NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M7 Pro (MR7400)... Bridge Mode/IP-Passthrough Only Works After Reboot?
As the topic says... If I reboot the router to which the M7 is attached via eth, then I have to reboot the M7 as well before bridge mode works. Has anyone else experienced this, or the contrary;...
you should be able to reboot your router downstream from the M7 and it will pickup an IP after reboot. i have an M6 Pro and this is how it behaves. I imagine it's not going to be that different in the M7
Hey... thanks for responding. You are correct, it works when you reboot the M7. It's always nice to get confirmation from someone else of "works that way for me too". My point is that it only works when you reboot the M7.
When the connection drops out or the IP address becomes invalid for any reason means someone has to physically walk to the M7 and reboot it. Given the M7's ability to connect external antennae means it has many use cases where the device is not simply right in front of you. Since everything usually works as soon as it's rebooted my point is that any device should be re-issuing a DHCP request whenever a re-connection is possible... and there's no technical reason why it can't, or shouldn't.
...or at least provide the ability to manually provoke the process to run and anyone with my use-cases can implement the rest themselves.
this is a mobile device and is not meant for remote installation. it seems like you are talking about the instance when the device loses connection from the cell site and you're saying the only way to get connectivity is to reboot your device? I re-read your post, you did not describe it that way. i also have instances of that happening and I have made myself a DIY reboot device where it pings a stable IP like 8.8.8.8, and if for some reason it does not get a response, it re-cycles the power to my M6 Pro. There are commercial devices sold for this exact purpose, just google it. you can get something that would cycle the AC supply of the power brick connected to your M7.
I'm talking about IP connectivity failure where one can't even ping the internal IP address of the M7 (devices can still keep a local/private IP address even when IP passthrough is activated) which can't be related cellular connectivity because they're totally different eth interfaces internally within the M7. Even if it were cellular connectivity it's still not required to reboot a device to re-establish connectivity to the cell network.
I looked at packet captures just now to see if there's anything deeper I can see. In the specific instance of this packet capture, the M7 IPv4 stack has stopped responding to ARP requests even though it is still sending them. My local ARP cache is showing an expired ARP lease for the IPv4 gateway address and thus no packets can be sent to the IPv4 gateway. For completeness, IPv6 ND is still working and so I can ping the IPv6 (link-local) gateway. I would definitely class this as a bug.
oooooo.... adding to that... the M7 is responding to ARP requests for the 192.168.1.1 address it maintains. I'm just not getting anything back for my ARP "who owns <IPv4 gateway address>?" or hearing any ARP requests from <IPv4 gateway address>.