NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
evollmca
Jan 20, 2021Aspirant
Help with routing issue
I have been searching, but honestly am not sure what to search for. I have an interesting scenario. I have a web service on my network that requires a valid SSL cert that I get from letsencrypt. In...
evollmca
Mar 18, 2021Aspirant
From the server ping works as the name resolves to the public IP and pings the router. So I guess it is pinging the router not the server. Same with tracert. It shows one successful hop directly to the public IP. Traffic gets forwarded from the router to the server through port forwarding. It seems like nothing connected via wifi we go through the port forwarding, but anything connected directly to the router will. So, for example, when I want to connect to the server with my phone I have to switch the wifi connection from the Orbi to an old access point I connected to the Orbi router.
It has never worked with the Orbi Router, but it was working before with my Asus router that the Orbi replaced
antinode
Mar 23, 2021Guru
> Model: RBR50|Orbi AC3000 Tri-band WiFi Router
RBR50[v1] or RBR50v2? Look for "Model" on the product label.
Firmware version? Connected to what?
> In order for client machines to successfully connect they must use the
> fully qualified name, which I think requires the traffic to be routed
> outside the router because it resolves to a public IP, but I am not
> sure.
The router should have a feature called "NAT loopback", which should
let you use the public IP (WAN/Internet) address from your LAN. Such
traffic is handled by the router, and does not get to the outside world.
> [...] I guess it is pinging the router not the server. [...]
The WAN/Internet interface on your router is the entity which has
your public IP address. I'd expect ADVANCED > ADVANCED Home : Internet
Port : Internet IP Address to show that. Your (unspecified) "server"
doesn't have that address, does it?
> [...] Traffic gets forwarded from the router to the server through
> port forwarding. [...]
Ok.
> [...] It seems like nothing connected via wifi we go through the port
> forwarding, but anything connected directly to the router will.
Sounds to me like a firmware defect. Unless a "guest" wireless
network is involved, any device on your LAN, wired or wireless, should
get the same access.
> Is there anything I can do, configuration wise, to get this to work,
> or I am just out of luck?
I doubt that there's any config option which would fix this. It
should just work.
> [...] it was working before with my Asus router [...]
That's also a clue.