LM1200 repeatedly dropping link

Thank you for the update. I am really hoping for this solution as this device is going to be sales tool for our msp team. I really need the ability for mobile connectivity through our firewall for demo purposes. 

John:

Any developments?  Does the team think we're close to resolution with Verizon?  Or is this still way out in terms of finding the problem?

---

stuyboy wrote:

John:

Any developments?  Does the team think we're close to resolution with Verizon?  Or is this still way out in terms of finding the problem?

 

---

We are at the final stage on debugging the issue. Verizon has been contacted and waiting for their feedback on the network logs for the disconnection issue. Still working on it.

Thanks

Just wanted to add to this thread that I'm experiencing the same thing with a Verizon sim.

In bridge mode (which is the mode I would think it needs to be in), connected to our Orbi, it resets itself every 30 seconds or so.

Basicaly can't use it at all!

However, when I set it to Router mode (counter intuitive, since the Orbi is routing 100+ devices), it actually works.

Thankfully, theres no "Double NAT" issues. (also confusing!)

We're only using this when PGE fails, and Comcast disconnects after their battery backup runs out.

Hopefully, the way we're running it continues to work for us, but it definitiely doesn't seem correct.

Looking forward to a firmware that cleans/clears all of this up.

Thanks in advance Netgear. 

Cheers,

Joel

Newmediasoup, LLC

For all customers who are experiencing constant disconnection with Verizon SIM card, could you please help to check your SIM's ICCID and let me know what is the number on the 11th digit of the ICCID? Based on Verizon, the number should not be lower than 7. We would like to determine whether the disconenction issue is due to older Verizon SIM cards.

89148000006287332959

ICCID is the numer printed on your SIM card starting with 89.

Thanks

OP here, and my ICCID's 11th digit is 7. The SIM itself was purchased directly from Verizon in August 2021.

---

JinTu wrote:

OP here, and my ICCID's 11th digit is 7. The SIM itself was purchased directly from Verizon in August 2021.

---

---

Thanks for the quick feedback. You do see the constant disconnections with the Verizon SIM.

Regards

John

Hello, Checked and my ICCID is 5. 

---

VinceBlack wrote:

Hello, Checked and my ICCID is 5. 

---

Thanks for the confirmation. Our test SIM is 6. We are getting a replacement SIM card with higher number and will let you know whether the new SIM card can resolve the issue. If so, you can request to have your SIM card updated as well.

Hi JohnPeng,

Yes, but only until I am able to successfully able to manually release and renew the DHCP lease and then the link stabilizes as mentioned in the first post. You have logs from me from October 25 of last year.

JohnPeng The 11th digit of ICCID is a 6, SIM issued in late Sep 2021. My device is experiencing the frequent connectivity issue, as described in my previous comments in this thread. Issue is still occuring. 

my 11th digit is a 6, it was also issued in fall of 2021.

My 11th digit is 4.  I'm nearing the end of my return window, so I would like to get this figured out soon.  Otherwise I'm probably just boxing it up and sending it back.

---

scoodogg wrote:

My 11th digit is 4.  I'm nearing the end of my return window, so I would like to get this figured out soon.  Otherwise I'm probably just boxing it up and sending it back.

---

Do you have another Verizon device? If so, could you please try use the SIM card on the Verizon device first. Then move the SIM card back to LM1200 to see whether the issue goes away.  If the issue is there, I suggest you to return it first. You can buy it again after we fix the issue if you like.

Thanks

I cant return mine. At this point its im losing money and might as well punt and find a different device/service that works. Its all just a corporate hassle at this point to move on.

---

AaronWTCI wrote:

I cant return mine. At this point its im losing money and might as well punt and find a different device/service that works. Its all just a corporate hassle at this point to move on.

---

Please standby. We are actively working on this. 

Thanks

all For Verizon disconnection issue, the SIM card is not the culprit. We received the new SIM card and tested, but the disconnection issue still happens. Based on your feedback, we can conclude the same as well.

Provided the feedback to Verizon and waiting for new information. 

Regards

I am having the same issue.  I have two LM1200s, each one connected to a Juniper SRX being used for VPN connections.  If i connect the LM1200 to my laptop, no problems.  Once it is connected to the firewall:

-Bridge Mode: Interface on SRX side stays fine, but the outside address on the LM1200 begins to cycle, breaking VPN.

-Router mode: Interface continues to cycle and grab new addresses, also breaking VPN.

It usually happens once the VPN connects, but that is just observation and could be a coincidence.  It does only seem to start happening once the connecting is complete to the remote device.

---

kylemania wrote:

I am having the same issue.  I have two LM1200s, each one connected to a Juniper SRX being used for VPN connections.  If i connect the LM1200 to my laptop, no problems.  Once it is connected to the firewall:

 

-Bridge Mode: Interface on SRX side stays fine, but the outside address on the LM1200 begins to cycle, breaking VPN.

-Router mode: Interface continues to cycle and grab new addresses, also breaking VPN.

 

It usually happens once the VPN connects, but that is just observation and could be a coincidence.  It does only seem to start happening once the connecting is complete to the remote device.

---

Thanks for the information. In this thread, some customers mentioned the same thing that when VPN enabled router is connected to the LAN port, it triggered the disconnection. We will check more on this direction.

Regards

JohnPeng 

Because so many of us were able to make a PC/Desktop work on Verizon on the LM1200 vs a Router...

Would pursue differentiation between network protocol of Router as client vs PC as client.  Main difference likely being the Network Address Translation (NAT).  Routers serve internal clients by using random high ports on the outbound connection (how a router knows to route a packet back to your specific desktop/phone). 

Verizon must be detecting source traffic not coming out of port 80 or 443?  Or perhaps the random nature of the high port #s?  Seems very strange that Verizon is able to detect a router vs a singular PC attached to the LTE modem as the IP protocol should appear the same on the wire. (https://help.ui.com/hc/en-us/articles/115005779887-Intro-to-Networking-Network-Address-Translation-NAT-and-the-Internet).  The only difference is traffic coming out of the router is constantly on a random port (the router uses this port to then map back to your internal machine).

Verizon is obviously doing something funny there in detecting the behavior a Router is exhibiting on its network vs a PC.  I assume this "Bridge" code is also unique to the LM1200, as this Verizon bug doesn't seem to affect any of Netgear's other LTE/Hotspot products?

Just some ideas.

I moved the sim card into the Jetpack hotspot and back.  This did not help.

I guess I'll start boxing this thing back up.  Such a shame.  It was pretty nice when it worked.

Not only 1200, it happens with my LAX20 as well on Verizon. i do have both and both having a same issie 

Firmware Version:EC25AFFDR07A09M4G

App Version:NTG9X07C_20.06.09.00

Web App Version:LM1200-HDATA_03.03.103.201

Hardware Version:1.0

---

sokobanz wrote:

Not only 1200, it happens with my LAX20 as well on Verizon. i do have both and both having a same issie 

 

Firmware Version:EC25AFFDR07A09M4G

App Version:NTG9X07C_20.06.09.00

Web App Version:LM1200-HDATA_03.03.103.201

Hardware Version:1.0

 

---

Thanks for the new info. Will check internal with LAX20 engineer to find some details. You can retrun the device now if you can only use Verizon SIM with it. Will try to resolve it soon.