[HN Gopher] A Visual Guide to SSH Tunnels: Local and Remote Port...
       ___________________________________________________________________
        
       A Visual Guide to SSH Tunnels: Local and Remote Port Forwarding
        
       Author : signa11
       Score  : 39 points
       Date   : 2023-01-12 06:27 UTC (16 hours ago)
        
 (HTM) web link (iximiuz.com)
 (TXT) w3m dump (iximiuz.com)
        
       | kentrf wrote:
       | This.
       | 
       | Port forwarding goes both ways.
       | 
       | I may, or may not, have used ssh forwarding and reversing
       | forwarding to create a shadow IT tunnel(s) between my home and
       | work when VPN was acting up.
       | 
       | Also, SOCKS proxy is very useful if you can puncture a hole home
       | and your work requires a proxy to access the World Wide Web from
       | the office location.
        
       | RpFLCL wrote:
       | This is a handy resource, SSH tunnels are something that I always
       | find easier to grasp when displayed visually.
       | 
       | I use a reverse SSH tunnel to access my home network when
       | traveling.
       | 
       | Ex:
       | 
       | - [Machine-A (on my LAN, behind NAT, with a dynamic IP address)]
       | maintains a long lived SSH connection to [Machine-B (a VPS with a
       | public IP)] with a reverse tunnel configuration.
       | 
       | - I can then SSH into Machine-B and follow the tunnel back into
       | Machine-A, and from there access the rest of my home network.
       | 
       | It works pretty well. I can access files on my NAS and check on
       | my Raspberry Pi cameras without needing to put either on "the
       | cloud". Although I have to admit I always have to pull up a
       | resource like the one in OP whenever I want to setup something
       | like this, I've never learned it by heart and always need a
       | refresher.
        
       | jalino23 wrote:
       | I find this useful!
        
       | linux2647 wrote:
       | Your machine can also act as a bastion to a remote resource for
       | the rest of your network through local port forwarding, e.g. -L
       | 0.0.0.0:8080:localhost:8080
       | 
       | Then any local machine can e.g. curl yourip:8080 and the request
       | will go through your machine, over the SSH tunnel, to the remote
       | machine
        
         | McNutty wrote:
         | Sorry but how is that different to what the blog post says?
        
       ___________________________________________________________________
       (page generated 2023-01-12 23:00 UTC)