NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
> I just joined. [...]
You "just joined" _what_?
> [...] This should be straight forward. [...]
Perhaps you could reveal what "this" is?
> [...] I've tried both DMZ and Port Forwarding. This is all on my LAN.
> [...]
DMZ and port forwarding deal with incoming connections from the
outside world; they have nothing to do with activity which is "all on
[your] LAN".
> [...] Just need to ping or ssh from the DESKTOP to the Raspberry Pi.
> [...]
Do these devices have IP addresses? Care to share? What, exactly,
is connected to what, exactly, how, exactly? What, exactly, are you
doing? What, exactly, happens when you do it?
> [...] Both ping and ssh work fine from the 192 net. [...]
None of that is a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
> [...] What am I doing wrong? [...]
What are you doing?
> [...] If it matters this is an Orbi RBR50 mesh with one satellite.
> [...]
And the RBR50 is connected to what?
> [...] The laptop is actually connected to the Orbi wirelessly, the
> DESKTOP is hardwired to the modem [...]
"the modem"? Are you offering any hints as to what that might be?
> [...] if this matters, from the Raspberry Pi, I can ping the modem
> (10.0.0.1).
It might matter, if I knew to what the Raspberry Pi is connected, and
how?
If you're seeing IP addresses like "192.168.a.b" and "10.0.0.c", then
I'd guess that you have cascaded two routers, and have two different LAN
address subnets. Communication between different subnets, although
possible, requires extra effort.
Most likely, one of your routers should be configured as a wireless
access point, rather than as a full-function router.
Start with a complete inventory of your modem(s), router(s),
modem+router(s), et c. Then reveal what, exactly, is connected to what,
exactly, how, exactly. (Hint: If a device has different types of
Ethernet ports, then "connected to device" is not enough detail.)
Why do you have more than one router? Broader wireless-network
coverage? (One router wasn't confusing enough?)
I can't (yet) see your picture. In-line images must be approved by
a moderator before others can see them. The time required varies.
Attachments have no such limitation. Of course, attachments have their
own one-per-message limitation.
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!
> 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: