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,378 of 21,939   
   68g.1499 to kyonshi   
   Re: Port forwarding from RPi to Windows    
   06 Feb 24 00:51:21   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR 68g.1499@etr6.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  f48f7d6b   
   REPLY:  c9ac3f5e   
   PID: SoupGate-Win32 v1.05   
   On 2/5/24 12:40 PM, 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 can get it, spend a few extra $$$ on a static IP.   
      Makes things a LOT easier.   
      
      To deal with dynamic IPs ... first off there are $$$   
      services. Basically they monitor your real IP, then   
      update DNS servers to match per change.   
      
      However I don't like paying extra $$$, or giving   
      commercial entities too much access/info.   
      
      So, I wrote a little Python sockets daemon that   
      polls for a coded packet from the dest - plus   
      one for the dest that detects an IP change and   
      sends it on via the tiny packet over a selected   
      port. The client polls this port, and uses the   
      packet to update the current IP address. A   
      'personal' version of DDNS utils. Not 'public'   
      however, no providers DNS nums are changed. COULD   
      be in theory though ...   
      
      If I can find it in The Mess I could post the   
      daemon/poller code. Not very flexible, but   
      it worked ok for years. Thing is, the desired   
      target for the IP daemon WAS a static IP. For   
      broader use you'd have to have the same or   
      post the info elsewhere (a provider acct   
      that offers ssh access to a file maybe.   
      
   --- 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