Reply
Highlighted
Tutor

RBR850 NAT loopback

Hello,

 

I'm hosting a webserver at home. The site is perfectly accessible from outside the network.

 

When I try to access it from inside the network, it works via wifi but won't work on an ethernet connection. I tried this on multiple devices.

 

Somehow NAT loopback is broken on ethernet only. Is there some setting somewhere for fixing this ?

Thanks !

Message 1 of 12
Highlighted
Luminary

Re: RBR850 NAT loopback

Currently Orbi AX is not yet included in the list of NETGEAR products that support NAT loopback:

https://kb.netgear.com/000049578/NETGEAR-Router-support-for-NAT-Loopback

Message 2 of 12
Highlighted
Tutor

Re: RBR850 NAT loopback

Thank you for the link. It's interesting that it works via Wifi though.

 

Does anyone know if/when this feature will be completely implemented ?

 

Thanks

Message 3 of 12
Highlighted
Apprentice

Re: RBR850 NAT loopback

I can confirm the lack of proper support for NAT loopback with a newly bought RBR750 (AX4200).

 

Very disappointing.

 

Netgear maintains a website with the subset of products that work correctly:

https://kb.netgear.com/000049578/NETGEAR-Router-support-for-NAT-Loopback

Message 4 of 12
Highlighted
Guru

Re: RBR850 NAT loopback

Something to post about here:

https://community.netgear.com/t5/Idea-Exchange-For-Home/idb-p/idea-exchange-for-home


My Setup (Cable 900Mbps/50Mbps)>CAX80(Modem Mode)>RBK853 v3.2.16.6(Router Mode)

Additional NG HW: C7800/CM1100/CM1200/CM2000, Orbi CBK40, RBK853, R7800, R7960P, EX7500/EX7700, XR450 and WNHDE111
Message 5 of 12
Highlighted
Apprentice

Re: RBR850 NAT loopback

This link is to an idea forum where new things are being proposed.

 

Being unable to establish a connection to a port on the public Internet is a bug.

 

Please read RFC 5382

 

7.2. Hairpinning Behavior

NATs that forward packets originating from an internal address,
destined for an external address that matches the active mapping for
an internal address, back to that internal address are defined in
[BEHAVE-UDP] as supporting "hairpinning". If the NAT presents the
hairpinned packet with an external source IP address and port (i.e.,
the mapped source address and port of the originating internal
endpoint), then it is defined to have "External source IP address and
port" for hairpinning. Hairpinning is necessary to allow two
internal endpoints (known to each other only by their external mapped
addresses) to communicate with each other. "External source IP
address and port" behavior for hairpinning avoids confusing
implementations that expect the external source IP address and port.

 

REQ-8: A NAT MUST support "hairpinning" for TCP.


a) A NAT's hairpinning behavior MUST be of type "External source
IP address and port".

Justification: This requirement allows two applications behind the
same NAT that are trying to communicate with each other using
their external addresses.


a) Using the external source address and port for the hairpinned
packet is necessary for applications that do not expect to
receive a packet from a different address than the external
address they are trying to communicate with.

 

Message 6 of 12
Highlighted
Guru

Re: RBR850 NAT loopback

And you can contact NG support as well to let them know of your concerns. Theres nothing we can effect here in the forums. 

 

Good Luck. 


My Setup (Cable 900Mbps/50Mbps)>CAX80(Modem Mode)>RBK853 v3.2.16.6(Router Mode)

Additional NG HW: C7800/CM1100/CM1200/CM2000, Orbi CBK40, RBK853, R7800, R7960P, EX7500/EX7700, XR450 and WNHDE111
Message 7 of 12
Highlighted
Aspirant

Re: RBR850 NAT loopback


@kildare wrote:

Currently Orbi AX is not yet included in the list of NETGEAR products that support NAT loopback:

https://kb.netgear.com/000049578/NETGEAR-Router-support-for-NAT-Loopback


I just checked the KB and it seems that RBR850 was added to the list.
That doesn't mean that it works, I'm able to access a resource using an external connection but not using the public IP from within the LAN. 

Message 8 of 12
Highlighted
Guide

Re: RBR850 NAT loopback

Same, NAT loopback isn't working for me on the RBR850.  Basically devices connected via Ethernet cannot talk to devices connected to Wifi (same Router).

Message 9 of 12
Highlighted
Prodigy

Re: RBR850 NAT loopback


@whoDean wrote:

Same, NAT loopback isn't working for me on the RBR850.  Basically devices connected via Ethernet cannot talk to devices connected to Wifi (same Router).


That is not the same problem as NAT loopback.  NAT loopback is when the public IP address or domain name of the server does not work within the local network (and presumably the local IP address or name still works).

 

If your wired and wireless devices cannot communicate with each other then that is probably a different problem.  They can't ping each other's local IP addresses?  Do you have any network switches between your Orbi and the wired devices?  Some network switches, particularly "managed" or "green" ones, cause connectivity problems within the Orbi local network.

 

Message 10 of 12
Highlighted
Guide

Re: RBR850 NAT loopback

I should have worded that better.

Wired Ethernet server is perfectly accessible by local wired clients, but inaccessible by local Wi-Fi clients, all devices connected through the Orbi.
Message 11 of 12
Highlighted
Guru

Re: RBR850 NAT loopback

What is this Ethernet Server? A PC with Server installed on it?

 

I can access my wired NAS while my Mac Book Pro is wirelessly connected to RBR. 

 

 


My Setup (Cable 900Mbps/50Mbps)>CAX80(Modem Mode)>RBK853 v3.2.16.6(Router Mode)

Additional NG HW: C7800/CM1100/CM1200/CM2000, Orbi CBK40, RBK853, R7800, R7960P, EX7500/EX7700, XR450 and WNHDE111
Message 12 of 12
Top Contributors
Discussion stats
  • 11 replies
  • 697 views
  • 3 kudos
  • 7 in conversation
Announcements