home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 19,372 of 21,939   
   Theo to kyonshi   
   Re: Port forwarding from RPi to Windows    
   05 Feb 24 18:06:50   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR theom+news@chiark.greenend.org.uk   
   REPLYTO 3:770/3.0 UUCP   
   MSGID: <+Nn*UJeCz@news.chiark.greenend.org.uk> 181b91a0   
   REPLY:  c9ac3f5e   
   PID: SoupGate-Win32 v1.05   
   kyonshi  wrote:   
   > I am behind a NAT, but I have a single RPi 3 running on a public IP. Now   
   > I found that to use a specific application properly on my Windows laptop   
   > I would need to have it on a public IP occasionally, so some clients   
   > could connect to it.   
   > Is there a way to make some sort of port forwarding from the Raspberry   
   > (which has both a publich eth0 IP and a private wlan0 IP) to my Windows   
   > machine via an app on the Raspberry? I tried with miniupnpc, but it   
   > demands a router that can be set to forward ports, and my ISP doesn't   
   > like that.   
      
   If you're running SSH on the Pi on a public port you can make a port   
   forward.  This tunnels port 1234 to port 4567 on the Windows machine:   
      
   ssh -L 1234:windows-pc.lan:4567 pi@raspberrypi.my.house   
      
   with windows-pc.lan and raspberrypi.my.house being the DNS names or IP   
   addresses of the machines concerned.  Then you tell whatever app you're   
   using to connect to localhost port 1234.  eg if the Windows box is running a   
   web app you're tell your browser to go to http://localhost:1234/   
      
   To do this you need to run SSH first, and the connection will go away once   
   the SSH session is closed.   
      
   You can also tunnel a SOCKS proxy:   
      
   ssh -D 3456 pi@raspberrypi.my.house   
      
   and then configure Windows / browser / etc to use the SOCKS proxy on   
   localhost port 3456.  This will allow connection to all machines on your   
   network as if you were there.   
      
      
   It is also possible to have the Pi permanently port forward, but for that   
   you expose the Windows machine to every attacker on the internet.  SSH is   
   designed for that and is probably more secure.   
      
   Another option is to run a VPN server on the Pi and connect to it via a VPN   
   client, which allows you into your home network.  Wireguard is a simple and   
   efficient VPN, or OpenVPN has some ways to get around ISP blocking of VPNs.   
      
   Theo   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca