NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk M2 IP PassThrough stops working when idle
So I have a Nighthawk M2 in IP PassThrough with a VPN tunnel uplink over time it disconnects from 4G network for some reason and as soon as I login to the Nighthawk it springs to life.
firmware NTG24_10.19.03.00
So anyone else having this problem? the ISP is o2
24 Replies
do you have it in performance mode?
Their is no performance mode option
I would assume by spring to life, you mean it regains connectivity to the cell tower? Do you use it with a battery? Do you take it mobile or purely stationary connected to a wall charger?
There could be a few things going on here.-o2 could be disconnecting you after being connected to their network for a while. ATT in the US seems to be doing this.
-if you are using a battery with your M2 and not taking it mobile, i would suggest using it on pure AC power using the charging brick and no battery. your device seems to be going into some sort of sleep mode, which is really not described in the manual. how is your VPN set up?
Thanks for the replies so far
Yes its always plugged in I don't see how removing the battery would help I have a VPN from Zyxel VPN300 that the Nighthawk is connected to which connects back to my virgin media Zyxel FLEX200 with pings going down the tunnel and I can see the tunnel drop I have tied a Connection Keeper app but does not come back to life until I login with password to Nighthawk then it starts working.
So its like this o2 gives out a 10. IP all works fine then 4G goes down Zyxel VPN300 picks up a IP of the LAN by Nighthawk I have set 192.168.7.0/24 I go to 192.168.7.1 login then it springs to life get 10. IP.
You might be right it might be o2 I was just hoping it might be a firmware bug.
So I have put the Nighthawk out of IP PassThrough mode and see what happens can take about 3 days uptime.
What I need is a app that can auto login to Nighthawk so that it stays up any ideas?
Well its been a week and no disconnects when out of IP PassThrough so its not o2 and must be a netgear when in IP PassThrough mode.
sad😞
I have an M6 in IP Passthrough mode. I don't even remember the last time I rebooted it. obviously they are different devices. could be a firmware implementation difference.
Yup tried without the battery in IP PassThrough still disconnects from 4G after a number of days so Netgear has broken uptime for IP PassThrough.😔
so just to recap, the IP passthrough was working fine before the latest FW update happened? If that's the case, please submit a bug report for netgear may be able to address it in a future update
So its odd I had it in router mode for some weeks then just out of interest put it back in IP PassThrough and for many weeks its been fine?
got solved?
I'm seeing something similar with the M7 Pro. What I've found through looking through packet captures is that the M7 stops responding to ARP requests even though it's still sending them out. The ARP cache expires for the ARP lease on the M7's gateway IPv4 address and now packets can't be sent to previous IP address because the ARP table entry has expired.
Due to the IP PassThrough work you don't really connect to the CGNAT gateway directly to its MAC its more like NAT 1:1. I've not had any more problem since so something the ISP was doing. I would think the M7 is the same with a 2 minute lease? But what the M7 has WAN side of the NAT 1:1 is anyone’s guess.
you don't really connect to the CGNAT gateway directly to its MAC its more like NAT 1:1.I have many questions...
On what is this statement based? How is CGNAT relevant here?
People can often have different meanings when they refer to "NAT 1:1". Is there a specific RFC that refers to the specific type of NAT 1:1 to which you're referring?
Regardless of the type of NAT, if an IPv4 node is supposed to send packets to another IPv4 node, how can it do so if it does not know the layer 2 MAC address to which to send those packets? i.e. how is any IPv4 node in a segment supposed to send its packets to its IPv4 gateway if that node does not have the MAC address? Shouldn't the bridge still respond to ARP requests? If not, why? How can it act as a layer 3 gateway if there is no layer 2 address? Broadcast?
