| === SystemV is now known as SysV | ||
| === Guest2882 is now known as g4mbit | ||
| foo | Reverse tunneling with ssh, trying to expose a lapto behind NAT to public. I do this: ssh -fN -R 1.1.1.1:10022:localhost:22 relayserver_user@1.1.1.1 ... I can see it's running, but when I try to connect to it with ssh -p 10022 homeserver_user@1.1.1.1 it says "Connection refused" ... granted, from 1.1.1.1, I can see it running on port 10022 | 07:26 |
|---|---|---|
| foo | I wonder if I'm missing something | 07:32 |
| === SysV is now known as Linux | ||
| foo | Alright, going to try this again - had to sleep on it. :) I have computer A behind NAT (residential). I don't know the IP, it changes. I want to ssh in and access this computer remotely from computer B. I have a linux droplet at digital ocean I can use. I *thought* I can set up a reverse ssh tunnel to connect to computer A behind NAT... but I can't seem to get it. I don't want to fuss with port | 14:06 |
| foo | forwarding. I used to have this all set up and working with something like this: .... OHHHH. I was using serveo, which I took offline. Ok, that's why this broke. | 14:06 |
| foo | In that case, what are my options here if I wanted to use something else? *researches | 14:06 |
| === y0sh- is now known as y0sh_ | ||
| znf | foo, tailscale/zerotier | 20:35 |
| === Linux is now known as QNX | ||
| === scoobydoo_ is now known as scoobydoo | ||
| === scoobydoo_ is now known as scoobydoo | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!