NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LBR20 keeps disconnecting from LTE
I just got one of the new LBR20 Obri routers with LTE connection. I was looking forward to this product for quite a while as I live in a rural area without high speed access and all I have available...
Exact same issue here on Verizon... works great when it works. LTE Band 13 -60db. Typically I see something like below in logs about 5-6 times daily. Then just gives up. Reconnects in about 30 minutes.
Most likely returning to Amazon as this makes it unusable. Maybe Starlink in the not too distant future...
[Internet disconnected] Tuesday, November 24, 2020 03:01:08
[Internet connected] IP address: 100.104.59.71, Tuesday, November 24, 2020 03:01:05
[Internet disconnected] Tuesday, November 24, 2020 03:00:53
[Internet connected] IP address: 100.112.105.20, Tuesday, November 24, 2020 03:00:47
[Internet disconnected] Tuesday, November 24, 2020 03:00:38
[Internet connected] IP address: 100.97.131.71, Tuesday, November 24, 2020 03:00:36
[Internet disconnected] Tuesday, November 24, 2020 03:00:27
[Internet connected] IP address: 100.80.96.4, Tuesday, November 24, 2020 03:00:19
[Internet disconnected] Tuesday, November 24, 2020 03:00:10
[Internet connected] IP address: 100.79.43.222, Tuesday, November 24, 2020 03:00:07
[Internet disconnected] Tuesday, November 24, 2020 02:59:58
[Internet connected] IP address: 100.69.159.41, Tuesday, November 24, 2020 02:59:55
[Internet disconnected] Tuesday, November 24, 2020 02:59:46
[Internet connected] IP address: 100.78.98.238, Tuesday, November 24, 2020 02:59:36
[Internet disconnected] Tuesday, November 24, 2020 02:59:27
[Internet connected] IP address: 100.111.152.13, Tuesday, November 24, 2020 02:59:25
[Internet disconnected] Tuesday, November 24, 2020 02:59:16
[Internet connected] IP address: 100.103.28.226, Tuesday, November 24, 2020 02:59:10
[Internet disconnected] Tuesday, November 24, 2020 02:59:01
[Internet connected] IP address: 100.85.202.75, Tuesday, November 24, 2020 02:58:58
[Internet disconnected] Tuesday, November 24, 2020 02:58:49
[Internet connected] IP address: 100.74.164.121, Tuesday, November 24, 2020 02:58:47
[Internet disconnected] Tuesday, November 24, 2020 02:58:38
[Internet connected] IP address: 100.85.109.56, Tuesday, November 24, 2020 02:58:37
[Internet disconnected] Tuesday, November 24, 2020 02:58:28
[Internet connected] IP address: 100.73.130.1, Tuesday, November 24, 2020 02:58:27
[Internet disconnected] Tuesday, November 24, 2020 02:58:17
[Internet connected] IP address: 100.76.34.73, Tuesday, November 24, 2020 02:58:10
[Internet disconnected] Tuesday, November 24, 2020 02:58:00
[Internet connected] IP address: 100.107.158.55, Tuesday, November 24, 2020 02:57:56
[Internet disconnected] Tuesday, November 24, 2020 02:57:47
[Internet connected] IP address: 100.102.211.13, Tuesday, November 24, 2020 02:57:41
[Internet disconnected] Tuesday, November 24, 2020 02:57:31
[Internet connected] IP address: 100.76.46.246, Tuesday, November 24, 2020 02:57:25
[Internet disconnected] Tuesday, November 24, 2020 02:57:16
[Internet connected] IP address: 100.85.77.61, Tuesday, November 24, 2020 02:57:12
[Internet disconnected] Tuesday, November 24, 2020 02:57:03
[Internet connected] IP address: 100.77.146.14, Tuesday, November 24, 2020 02:57:00
[Internet disconnected] Tuesday, November 24, 2020 02:56:50
[Internet connected] IP address: 100.117.101.61, Tuesday, November 24, 2020 02:56:45
Yep blitzberlin. Pretty much what I was seeing in the logs as well. The thing I don't understand is how is it getting assigned new DHCP addresses every 15 or so SECONDS during that supposed downtime period? Seems to me that it has to be getting a data call connected each time - at least enough to get assigned a DHCP address. Could Verizon be dropping the call immediately after it connects and then allowing a reconnect - and then repeating that process several times?? Seems unlikely... Something odd about that behavior IMO.
After a bit of research, I found that they're using Quectel's EG18 module (which, BTW, is NOT among the Quectel modules that Verizon lists on its site as supported...). The connection manager (quectel-cm) is capable of providing more detailed logs, but I wasn't able to find a way to start it up that way on boot... If I can find some spare time I may see whether it's possible via the debug interface to kill/restart the CM with additional logging and see if that provides any additional insight into what's happening. Being an OpenWRT-based device does have its advantages. Thanks to NETGEAR for that! It's normally one of the reasons I buy NETGEAR routers.
But unless I can figure out a workaround soon (or NETGEAR speaks up about availability of a fix), the replacement unit may end up going back as well. I predict a bunch of LBR20 refurbs on the market if this isn't addressed soon. Negative feedback at Amazon starting to stack up.
Surprising for a new product with such great potential that firmware has not been updated since July?