NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JinTu
Aug 26, 2021Star
LM1200 repeatedly dropping link
I recently purchased an LM1200-100NAS to serve as an LTE failover connection for my homelab and noticed a strange issue while setting up my pfSense-based router to use the LM1200 as a secondary WAN connection. When I initially activated the SIM card on Verizon with the LM1200, I had it directly connected to the Ethernet interface on a PC, and did not see any issues with the link dropping after the LM1200 had fully powered up. However, for some reason, shortly after powering up the LM1200 when connected to the router, it connects to the LTE network (the right-most LED goes from orange to green), then the LAN LED illumminates green, but shortly afterwards, the LAN LED extinguishes, and I see the port link is down on the router. The link stays down for a few seconds, then the process repeats unless I force release then renew the IP address on the router's interface via DHCP. Once I do this, the LM1200 stops dropping the link and the router get's an IP address and is able to route out the LM1200 via IPv4, and I am able to reach the management interface of the LM1200 on 192.168.5.1. This seems to happen every time I power-cycle the LM1200, and requires manual intervention to be able to get a valid IP and pass (IPv4) traffic through the device. I was also able to admin disable the router interface (leaving the link up) and then enabling the router's interface and this also seemed to helped as the link some of the time, but it wasn't consistant. This suggests the issue may be timing related.
The LM1200 and my router are also being issued an IPv6 IP address from my wireless carrier (Verizon) as well, but I have thus far been unsuccessful in routing out via IPv6. However, the IPv6 issue is an issue for another thread.
Note that I currently have the LM1200 in bridge mode.
Firmware version: EC25AFFDR07A09M4G.
App version: NTG9X07C_20.04.07.06.
Web App version: LM1200-HDATA_03.03.103.189.
Has anyone seen anything like this?
I see that there is a new firmware release due at the end of the month for the LM1200. Is there a possibility that this will address the issue?
232 Replies
- mal7887Aspirant
So just thought I would pass this along. I ended up returning the LM1200 due to the connection issues. I bought another vendors equipent but also expierenced some similar, albiet not as extreme connection issues, but ocasionally I would go through cycles where I was disconnected and reconnected. I noticed that I was getting a IPv4 Address and a IPv6 address. After trying some different things, I finally set the protocol type to IPv4 ONLY. Ever since I have done this, the connection has been 100% stable, I change it back to IPv4+IPv6 and i have sporadic connection issues again. There seems to be something weird happeneing with Verizon when getting a IPv4 and IPv6 address.
Since I have already returned my LM1200, I don't recall if disabling IPv6 was an option.
- kpbongTutor
I was intrigued by this report so I tried eding the APN to change the PDP from IPV4IPV6 to IPV4 only. This did not change the behavior I'm seeing in bridge mode, where the device resets itself when my router attempts to get a DHCP address. Router mode seems more stable with IPv4-only PDP.
- bbatty66TutorCan you give a bit more by way of specifics please? Per the thread, I'm assuming this is using an LM1200 on Verizon. If running in router mode, what did you use for gateway and DNS addresses?
- JohnPengNETGEAR Expert
mal7887 wrote:
So just thought I would pass this along. I ended up returning the LM1200 due to the connection issues. I bought another vendors equipent but also expierenced some similar, albiet not as extreme connection issues, but ocasionally I would go through cycles where I was disconnected and reconnected. I noticed that I was getting a IPv4 Address and a IPv6 address. After trying some different things, I finally set the protocol type to IPv4 ONLY. Ever since I have done this, the connection has been 100% stable, I change it back to IPv4+IPv6 and i have sporadic connection issues again. There seems to be something weird happeneing with Verizon when getting a IPv4 and IPv6 address.
Since I have already returned my LM1200, I don't recall if disabling IPv6 was an option.
This is an important information. Thanks for your feedback.
As our investigation shows, even though the device settings can cause the issue, eventually, the issue happens on the Verizon network side since the network intitiates the disconnection and the issue happens intermittently.
Thanks
- FiddlinTutor
I just got my LM1200 earlier this week and would like to join the growing list of people having this same problem. I want to connect the LM1200 in bridge mode to my pfSense firewall (core2duo with Intel quad gigabit card). I have Verizon service with the card the local store recommended when I showed them my LM1200.
First day: I hooked everything up accessed the LM1200 via web interface at 192.168.5.1 using a PC through my pfSense, got a connection after a couple failed attempts and used it for about 4 hours until I was done, and manually disconnected. Ever after: when I connect the LM1200, it quickly says it is connected, then cycles the link (link light down then up after several seconds), then says disconnected and cycles the link again. Every now and then, it will be up long enough to get maybe 3 or 4 pings to 8.8.8.8, but that is rare.
I can hook directly to a single computer just fine. When I connected to a single computer and let it work for a few minutes, then swung the ethernet cable over to the pfSense, I got good pings for about 20 or 30 seconds, then the cell connection dropped again.
I have already disabled IPv6 on all of my PCs, pfSense and LM1200 - I avoid using IPv6 anyway - just call me old-school. I will certainly try router mode tonight in hopes of getting my whole network online.
Let me know if I can provide anything to contribute to a solution - I really want this to work in bridge mode in hopes that at I could get at least some access into my network from outside. (I used to host several web sites and frequently remote into my home network from outside util I moved - I'm sure web-hosting is out of the picture over consumer-level cell, but bridge mode is what makes the most sense to use for a router/firewall anyway)
Also, thank you to everyone who has been contributing. This being my first venture into cell data (since comcast backed out after telling me they could hook me up), I was starting to think I missed some fine print in some verizon usage clause or just didn't understand how the LM1200 was supposed to work.
- AaronWTCIAspirant
This thread has been going since August of 2021. We still have no solution and its obviously not some one off thing. I have opened a ticket with Verizon support as well just to get another angle on it. A tier 2 tech told me he would monitor my connection and escalate the info to engineering. I am still waiting to hear back from them. I have sent 2 follow up emails but no response yet.
- AaronWTCIAspirant
I also shared the link to this with them as well. Maybe Netgear and Verizon could get it figured out together..
- JohnPengNETGEAR Expert
Fiddlin wrote:
I just got my LM1200 earlier this week and would like to join the growing list of people having this same problem. I want to connect the LM1200 in bridge mode to my pfSense firewall (core2duo with Intel quad gigabit card). I have Verizon service with the card the local store recommended when I showed them my LM1200.
First day: I hooked everything up accessed the LM1200 via web interface at 192.168.5.1 using a PC through my pfSense, got a connection after a couple failed attempts and used it for about 4 hours until I was done, and manually disconnected. Ever after: when I connect the LM1200, it quickly says it is connected, then cycles the link (link light down then up after several seconds), then says disconnected and cycles the link again. Every now and then, it will be up long enough to get maybe 3 or 4 pings to 8.8.8.8, but that is rare.
I can hook directly to a single computer just fine. When I connected to a single computer and let it work for a few minutes, then swung the ethernet cable over to the pfSense, I got good pings for about 20 or 30 seconds, then the cell connection dropped again.
I have already disabled IPv6 on all of my PCs, pfSense and LM1200 - I avoid using IPv6 anyway - just call me old-school. I will certainly try router mode tonight in hopes of getting my whole network online.
Let me know if I can provide anything to contribute to a solution - I really want this to work in bridge mode in hopes that at I could get at least some access into my network from outside. (I used to host several web sites and frequently remote into my home network from outside util I moved - I'm sure web-hosting is out of the picture over consumer-level cell, but bridge mode is what makes the most sense to use for a router/firewall anyway)
Also, thank you to everyone who has been contributing. This being my first venture into cell data (since comcast backed out after telling me they could hook me up), I was starting to think I missed some fine print in some verizon usage clause or just didn't understand how the LM1200 was supposed to work.
Thanks for the detailed information. Based on the discussion here, we know that pfsense can trigger the disconnection issue easily, but the disconnection initiated on the Network side. Really need to get the network logs to find out why. We could reproduce the same issue with other Netgear fixed wireless products on Verizon network. Even with LM1200, we can see that the issue happens intermittently, but when it happens, the link will keep resetting for a while before it finally gets stable.
Thanks
- cghTutorUsing verizon here. I am experiencing the same issues in this thread. The disconnects between LM1200 LAN port and router port are a layer 2 issue correct? Link up/down/up/down. Why does the (MAC) layer 2 connection between the LM1200 change? What does that have to do with the Verizon wireless connection? I am using a edge router 4. For comparison, if I disconnect the coax from my cable modem, my modem and router are still connected layer 2.
- JohnPengNETGEAR Expert
cgh wrote:
Using verizon here. I am experiencing the same issues in this thread. The disconnects between LM1200 LAN port and router port are a layer 2 issue correct? Link up/down/up/down. Why does the (MAC) layer 2 connection between the LM1200 change? What does that have to do with the Verizon wireless connection? I am using a edge router 4. For comparison, if I disconnect the coax from my cable modem, my modem and router are still connected layer 2.Seems you are using Verizon cable box connecting to LM1200 WAN port and a router connecting to LM1200 Lan port. If this is true, the issue discussed in the thread doesn't apply to your setup. The Verizon disconnection issue happens when using Verizon wireless network.
Thanks
- cghTutorJohn, Apologies. I am not using a Verizon cable box, I am using a LM1200. I was attempting to draw comparison to another type of modem and the behavior when the service provider connection gets dropped. This might help eliminated confusion if the LM1200 LAN to router L2 connection remained persistent through provider connection dropouts. No other modem that I am aware of drops L2 link when the service provider connection drops.
- mrgeniusAspirant
Hi John, any update on the cycling disconnects with Verizon and bridge mode? I'm a NETGEAR partner and turning anywhere I can to see if there is a fix on the horizon. I really want to buy these in bulk, but my eval unit is exibiting the same behavior as described in this thread: erratic cycling disconnects in bridge mode, with Verizon coming back with a new IP address each time, where router mode seems to be stable. Thank you.
- JohnPengNETGEAR Expert
mrgenius wrote:
Hi John, any update on the cycling disconnects with Verizon and bridge mode? I'm a NETGEAR partner and turning anywhere I can to see if there is a fix on the horizon. I really want to buy these in bulk, but my eval unit is exibiting the same behavior as described in this thread: erratic cycling disconnects in bridge mode, with Verizon coming back with a new IP address each time, where router mode seems to be stable. Thank you.
Right now, the issue in Verizon's hand. We have provided the device information for them to check the network logs. Seems this is not a device issue since we noticed the same issue also happens on other devices. Will push Verizon to provide the update asap.
Thanks for your patience.
JohnPeng wrote:Right now, the issue in Verizon's hand. We have provided the device information for them to check the network logs. Seems this is not a device issue since we noticed the same issue also happens on other devices. Will push Verizon to provide the update asap.
Thanks for your patience.
JohnPeng for anyone experiencing this issue who wants to reach out to Verizon to put additional pressure on them to investigate/resolve the issue, is there as specific case or ticket number that we can reference to direct their attention to the case Netgear already has open about this?
JohnPeng & Et al.
What a troubling issue indeed. Please read below for what I've discovered, if you've been reading this topic for months you'll find it quite interesting.
AT&T hotspot SIM works fine using Bridge Mode in my LM1200, no link dropping no lost IP addresses, this we know already.
All of my testing was done using a MikroTik hAP ac2 running 7.1.3 software for reference.
The Verizon hotspot SIM on our business account in the LM1200 in Bridge Mode receives an IP then drops the ethernet link approximately 26 seconds later and of course loses the IP address, then approximately 23 seconds later the ethernet link is recovered and the cycle repeats. This is the first time I've seen the behavior documented to this level of detail.
I decided to leave the hAP ac2 running all night long, utilizing the LM1200 with the Verizon SIM and left no devices connected to the router. Curiously the Verizon LTE connection never dropped while no other devices were connected to the router. Further, the ZeroTier VPN connection stayed stable and I was able to remotely access the hAP ac2 without issue. This behavior was most curious and so began my attempt at a theory of why. I had something to do with devices connected behind the NAT of the hAP ac2. Sure enough when I connected a device to the router the next morning the LM1200's connection began the drop and reconnect behavior described above.
What is different when the router connects via the Verizon IP vs though the NAT of the router? Should be nothing, right? A proper NAT translates the device IPs behind it and Verizon shouldn't know any better. How could Verizon know? After digging back into years of IP header theory back in my college days, I had mine (it took a few days) - and it was the TTL value was wrong.
I added a rule in the hAP ac2 that adds 1 to the TTL of all IP packets passing though the NAT. After doing that, the Bridge Mode connection became solid. No cycling of the ethernet link, nor IP addresses releasing and renewing. Of course, upon removing the rule adding 1 to the TTL the connection is dysfunctional as described above. After dozens of tests, the behavior is controllable and predicable based upon the TTL change.
Ok, so your thinking then the Netgear programmers just need to fix this by adding 1 to the TTL when the LM1200 is in Bridge Mode. Wrong!
Just for giggles (does anyone really giggle in these moments?) I decided to really go for it and see what the heck was going on and see if I could determine who's issue it was, now that I'd confirmed what it was. No need to blame Netgear if indeed they were not at fault. It's easy and that's wrong.
Since the hAP ac2 has a USB port and supports the Verizon USB730L functioning as a pass though bridge device I decided to do an experiment with the same Verizon SIM used in the testing with the LM1200. Surprisingly both the USB730L and the LM1200 exhibit the same behavior where the connection is unstable with an unmanipulated TTL and adding 1 to the TTL stabilizes the connection.
Verizon's network used to work properly without TTL manipulation with the USB730L and the hAP ac2. At some point it stopped working. I thought it was a bug in the hAP ac2s software and said well hopefully they'll fix it someday. It wasn't the hAP ac2s software, something has changed Verizon's network, I'm not sure when it changed it's been a while. This is Verizon's issue, not Netgear's.
Unfortunately, I don't know how to get this to the right folks at Verizon. Most people who hear this are going to think it's network gibberish when attempting a support call. I tried to get help from Netgear regarding the device and was promised a call back the next day, the call never came and my Case #: 45696214 was closed in 7 days because I was unresponsive. This is where Netgear is at fault. I'm utterly disappointed in Netgear support, closing the case with no call back is absolutely unacceptable.
Hopefully this helps someone.
--Mike
labellama this is an interesting discovery. I just did a quick check and by default my pfSense-based router is setting the TTL (and hop limit for IPv6) to 64 for the gateway health checks (but this varies for other traffic on failover) What is the minimum TTL/hop limit that you are seeing on egress from the hAP ac2 after making this change?
JinTu I’m seeing a TTL of 54 to 8.8.8.8, 113 to 8.8.4.4 and 50 to 1.1.1.1, these are the TTL values after the manipulation rule that adds 1 for all egress to the LM1200.
From my testing, forcing the TTL to 64 or 65 on egress did not change the dysfunctional behavior.
- JohnPengNETGEAR Expert
solah wrote:
JohnPeng Can you clarify that you work for / represent Netgear? What is taking so long to sort this out? Is there a solution on the horizon or should we just return our products?
I am the PM of the project. Based the logs we collected so far and other customers' feedback, the issue points to Verizon network issue. We have a case open with them to check the network logs, but the progress is slow.
If you have to use Verizon network and the current issue really prevents you from using the device, I am OK you return it for now. We will let you know when the issue is resolved.
Thanks
In regards to what the hAP ac2 is setting the TTL to, I don't know what I was thinking in my previous reply.
Before adding 1 to the TTL the TTL is 63, after of course it is 64.
Setting the TTL to 64 on egress to the LM1200 also mitigates the issue when using Verizon LTE.
I did a quick test on this yesterday by setting net.inet.ip.stealth=1 and net.inet6.ip6.stealth=1 which forces pfSense to not decrement the TTL/Hop limit by one for traffic that transits the firewall, and observed that during the test the TTL/hop limit for all outbound traffic was never less than 64.However, this doesn't seem to have improved the connection reliability or prevented the link from dropping on failover. At least in my case, I observed the same behavior as before in that as soon as pfSense failed over to using the LM1200 for anything other than ICMP, the link dropped after a few seconds.
- STI_MECEInitiate
I had to reply to this only because you can throw me in mix for having repeated dropped connections every 30 seconds. I can only get a consistent connection whenever I plug the LM1200 straight into my laptop, or at night ill carry it over to my smart tv and plug it in there so i watch Netflix.
How is this going on for over 6 months and still not resolved? I blame Netgear just as much as Verizon on this.
I can not setup any of my unifi devices or anything. I am literally just tied to the freaking modem with a flipping ethernet cord with nothing connected to it.
For some reason, whenever I try and have multiple devices everything just fails. I can see the flipping cell tower from my window, i got great signal.
Every time i loseconnection it picks up a new IP address. I just don't get it. Its even worse seeing how long this thread goes on for. No urgency.
- kristuferAspirant
Also on the verizon network here. Can anyone confirm any previous version of firmware this rebooting issue was not present on with verizon? I would be happy to try a downgrade at this point until a fix is finally distributed.
Chris
- FiddlinTutor
I don't remember this coming up in this thread before since I believe we've all been trying to get the LM1200 to work in bridge mode between our routers and verizon. While testing some other things, I discovered that the exact same behavior happens when I run the LM1200 in router mode and remove my router.
Testing went as follows:
The LM1200 is in router mode on a 5-port switch
4 computers are also on the switch
All computers can ping the LM1200 successfully
When LM1200 connects to verizon, one computer can access internet web pages, but the very moment a second computer tries to access an internet page, the cell connection drops.
This surely has to be something verizon is doing to prevent multiple devices from using their service - maybe something like trying to prevent people from using their phone as a hotspot without paying for hotspot service. It looks like we're only getting by in router mode behind a router because the router is the only device verizon can detect using the connection.
- sfenwick76Aspirant
I just purchased the LM1200 as a backup WAN link for my TL-R600VPN router. I have Verizon and have experience the same issues as everyone else -- the link is only up for about 5 seconds, then the link drops and this cycle repeats itself. I should have went to this support page instead of wasting several hours of my time trying to figure this out! Very frustrating. My LM1200 works fine if I connect it to a PC ethernet jack, but it exhibits this behavior if I connect it to one of the WAN ports on my router. I have tried both Bridge and Router mode, with the same results. Has anybody found a solution to this? Does anyone know if I ditch this LM1200 for another verizon hotspot like the Verizon 5G M1000 (it has an ethernet jack) will I just have the same problems?
Thanks!
- bbatty66Tutor
I finally had to give up on this one. I have to stay with Verizon (their cell tower to the east of my location is the only reliable signal source) so after trying several other options I wound up shifting to a verizon business account with a static IP provisioned and a demo unit of an Inseego Skyus 160. Once it arrived it took me under an hour to get everything configured and running, and most of my various problems (stability, UDP packets reaching my IoT devices via my local WAP fed by the LTE gateway) went away.
I understand that with no resolution between Verizon and Netgear there is very little that might be possible to fix this. Ultimately it doesn't matter who is in the wrong here though if the LM1200 can't be made to work with a Verizon consumer LTE signal and a working solution is needed.
bbatty66 wrote:
I understand that with no resolution between Verizon and Netgear there is very little that might be possible to fix this. Ultimately it doesn't matter who is in the wrong here though if the LM1200 can't be made to work with a Verizon consumer LTE signal and a working solution is needed.Given that this issue was originally reported in August of 2021 and Netgear has yet to take any meaningful steps to resolve it, all references to Verizon support should be removed from the product. As-is Netgear could be subject to litigation for false advertising under Section 43 of the Lanham Act...
- NathanR2D2AspirantJohnPeng Any updates? My Orbi RBR50 keeps dropping internet connection after a few hours with the WAN port connected to my cable modem and Verizon for LTE. Any ETA on a new firmware release address? Failover also does not work properly.
- JohnPengNETGEAR Expert
NathanR2D2 wrote:
JohnPeng Any updates? My Orbi RBR50 keeps dropping internet connection after a few hours with the WAN port connected to my cable modem and Verizon for LTE. Any ETA on a new firmware release address? Failover also does not work properly.As I just replied to another customer, this is not device issue. It is related to Verizon network. If you connect a computer to the ethernet port using the same Verizon SIM card, you will not see the issue. The issue only happens when your connect a router to ethernet port and the connection is released by the network, not by the device.
Thanks
- NathanR2D2Aspirant@Jonhpeng
I placed the LM1200 in router mode and will monitor to see if it still drops the WAN IP after a few hours. The primary connection is my cable modem with LTE as failover.