NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DaveBrillhart
Jan 08, 2021Aspirant
RBR50 Port Forwarding / DMZ
I just joined. This should be straight forward. I've tried both DMZ and Port Forwarding. This is all on my LAN. Just need to ping or ssh from the DESKTOP to the Raspberry Pi. Both ping and ssh work f...
DaveBrillhart
Jan 09, 2021Aspirant
Thanks bud! Agree that the two router and double NAT is problematic.
Just quickly.... the cable modem/router is on-perm (in my home) ISP equip, they are hard coded to the 10 net, and have limited access to features (it seemed). I have my own Wi-Fi Router - a mesh network, that distributes 192 addresses to dozens of clients. So, yeah, tunneling thru TWO routers was/is the issue I think.
I now think there is a way to turn off the cable modem's router personality and make it simply a modem. Then my Orbi mesh router will be presented with the Internet IP and I'll have a single device to punch a hole thru for ssh access to my Pi. With more features to setup a DMZ or Port Triggering or Port Forwarding... whatever make sense.
Thanks again!
antinode
Jan 09, 2021Guru
> the cable modem/router [...]
Not a huge improvement over "the modem".
> [...] is on-perm (in my home) [...]
"On-permises"? (Bad spelling of whole words is easier to decipher
than bad spelling of abbreviations.)
> Most likely, one of your routers should be configured as a wireless
> access point, rather than as a full-function router.
> I now think there is a way to turn off the cable modem's router
> personality and make it simply a modem.
That would work, too, if it's possible. Sadly, with my weak psychic
powers, and a description like "the cable modem", it's tough to be sure
of much. Note that if you do that, then all your client devices must be
connected to the Orbi gizmo(s), not to your (unspecified) "the cable
modem". (Only the main Orbi router would connect to your "the cable
modem".)
> [...] Then my Orbi mesh router will be presented with the Internet IP
> and I'll have a single device to punch a hole thru for ssh access to my
> Pi. [...]
You don't need to "punch a hole thru" anything to access the R-Pi
"all on [your] LAN". If you want to access the R-Pi using SSH from the
outside world, then I'd advise using port forwarding. In which case,
look for "If you ever do get this stuff working" in: