NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear Nighthawk M5 MR5200 WAN issue
Hi, I have a Netgear Nighthawk M5 MR5200 (ip address 192.168.1.1) that is working with the IP passthrough and it is connected to the WAN port of an Asus AX11000 (ip address 192.168.2.1). I can acces...
Thanks
I am having the same problem, ethernet port unavailable after the night.
Firmware is up-to-date as of today.
This means the device is completely useless for me, unless this will be addressed immediately.
May need to send the device back to Amazon and purchase a better quality alternative.
I am having the same problem, ethernet port unavailable after the night.
Firmware is up-to-date as of today.
This means the device is completely useless for me, unless this will be addressed immediately.
May need to send the device back to Amazon and purchase a better quality alternative.
Actually, in my case it stop working as a wan modem (connected to my router) with IP-Passtrough after 1-3days. When netgear will fix this??? it's unusable!!!
Hi All,
For M5 Ethernet port connection stability issue, I have raised the case to the internal team and hope we can have a solution soon. The root cause of the issue may be related to WWAN side data connection reset by the carrier after certain period of time without data transferring, but the device fails to refresh the IP to the Ethernet client after the connection is resumed.
Thanks for your patience.
I seem to be encountering the issue identified in this thread as well.
I am on AT&T here in in the US with my MR5200 connected to a Netgear R7000P router.
MR5200 becomes inacessible with no connection to the main router every few days (but only in the morning after a night with presumably no data activity). Nevertheless, the device itself reports on its screen that it is successfully connected to the AT&T cellular network.
The MR5200 replaced a Netgear 2120 modem that had no problems maintaining a solid and stable connection to the R7000P at all times.
Really no other problems with the MR5200 other than its occassional failure to maintain a connection the R7000P.
I've both a MR1100 and the MR5200.
I can confirm that wan connection (with IP passtrough) to my router is 100% reliable on the MR1100 and connection is lost after 2-3 days on the MR5200 (external IP isn't updated to the lan port). What a joke.
after much troubleshooting I believe that this is the correct issue diagnosis.
One thing to note is that my device is attached to pfSense.
The first problem I experienced is that the WebUI configuration dialog defaults the subnet mask to a /32 address space, so by default it is set to 255.255.255.255, rather than a /24 space: i.e. 255.255.255.0. This causes a configuration issue for IP PassThru on PF Sense because the gateway would appear to be outside the subnet of the interface IP due to the host only mask. Changing it to /24 subnet mask resolves the issue.
The other issue is related to TTL. The default pfSense interface configurations have a TTL of 100 MS to 200MS, and after 200MS the link is considered down. I believe that without any data being transferred the Cell Tower may downgrade the connection to the device causing increased latency, which could cause the device to be marked down by PFSense. I increased my latency to 2000MS to prevent the link being marked down. When data is transferred I believe (but cannot confirm) that likely the LTE tower will increase power to the link and thereby decrease latency again. Just a couple of hints here, but I could be wrong.
For now with increased TTL on pfSense the device is not being marked down.
The problem if the interface gets marked down is of course that this causes the DHCP lease to be released, and then the interface cannot get a new DHCP lease again from the MR 5200 due to the bug you have referenced JohnPeng
One Final Thought, after running ifTop and monitoring the traffic on this interface, it appears that the NetGear device is sending DNS queries, after doing some research at least one other person has confirmed this.
I for one certainly do not appreciate any kind of 3rd party tracking code in the firmware if that's what this is.
Looking at this in more depth today. I turned on logging for that floating rule and then filtered the logs with the source IP of the Netgear modem. So what it looks like is happening is the Netgear modem is sending UDP packets to seemingly random IP's on port 53 (DNS) out our main WAN! I have no idea why that would even happen. Anyway I looked at the IP's and used whois to find out where they are going. Most of them are going to IP's owned by Microsoft. Some to Amazon. Others to other large US companies and others to foreign companies. I also disabled the floating rule and did a packet capture on the higher traffic that happens. I can see it still doing DNS queries at large companies.
Hi John
Is there any progress with this?
Thanks,
Toby
One thing I did as a workaround instead of using it as a "WAN passthrough" – I use it as a regular network connection but give the connected router DMZ access. Doing this kind of gives me the functionality I need, without dropping the connection every other day.