Wireless Joint

Posted: **Wed Oct 30, 2024 9:38 pm**

I have a NEXQ6GO w/ EP06A. Generally, for the past 3 years it has worked wonderfully. Sometimes it goes down unable to connect for 30min-couple of hours, and in today's case almost 12 hours. I've tried reflashing the router. I've tried different builds (9-10-21 and 10-2022). I've tried to connect bone-stock with no saved configuration. It just gets to a point where it should connect and it just hangs. I've put the sim into a tablet and it connects fine. No known outages in the area. Usually it stays up connected for 3-4 weeks at a time. More so since upgradng the firmware awhile back. I've never made any perm. config changes and maybe this will clear itself on it's own no idea.
Usually there is a flurry of stuff that happens after the timeout error and OK lines @ the end, but not currently. Under the modem/network status page it says Provider:Connecting, SIM,IMEI,phone details are all populated like nomal. Yet I get no iP4/IP6 ip address. Here is a copy of the debug log:

Thanks for any assistance.

Code: Select all

Wed Oct 30 11:25:29 2024 : /dev/ttyUSB2 AT+CNMI?
+CNMI: 1,1,0,2,0

OK
  
Wed Oct 30 11:25:31 2024 : /dev/ttyUSB2 AT+QINDCFG="smsincoming"
+QINDCFG: "smsincoming",0

OK
  
Wed Oct 30 11:25:32 2024 : /dev/ttyUSB2 AT+QINDCFG="all"
+QINDCFG: "all",1

OK
  
Wed Oct 30 11:25:34 2024 : /dev/ttyUSB2 AT+QINDCFG="all",0,1
OK
  
Wed Oct 30 11:25:36 2024 : /dev/ttyUSB2 AT+CGMM
EP06

OK
  
Wed Oct 30 11:25:37 2024 : /dev/ttyUSB2 AT+QCFG="band"
+QCFG: "band",0x0,0x20000000000001018,0x0

OK
  
Wed Oct 30 11:25:39 2024 : /dev/ttyUSB2 AT+CGMM
EP06

OK
  
Wed Oct 30 11:25:40 2024 : /dev/ttyUSB2 AT+GMR
EP06ALAR02A08M4G

OK
  
Wed Oct 30 11:25:42 2024 : /dev/ttyUSB2 AT+CGMM
EP06

OK
  
Wed Oct 30 11:25:44 2024 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0

OK
  
Wed Oct 30 11:26:03 2024 : /dev/ttyUSB2 AT+QINDCFG="all",1
OK
  
Wed Oct 30 11:26:05 2024 : /dev/ttyUSB2 AT+COPS=3,2;+COPS?
+COPS: 0,2,"311480",7

OK
  
Wed Oct 30 11:26:07 2024 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)

OK
  
Wed Oct 30 11:26:08 2024 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CGDCONT: 6,"IPV4V6","VZWCLASS6","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

+CFUN: 1

OK
  
Wed Oct 30 11:26:13 2024 : /dev/ttyUSB2 AT+CMGS=?;+CMGL=?;+CMGR=?
+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")

OK
  
Wed Oct 30 11:26:14 2024 : /dev/ttyUSB2 AT+CMGF=0
OK
  
Wed Oct 30 11:26:18 2024 : /dev/ttyUSB2 AT+CPMS="SM","SM","SM"
+CPMS: 0,0,0,0,0,0

OK
  
Wed Oct 30 11:26:20 2024 : /dev/ttyUSB2 AT+CPMS="ME"
+CPMS: 0,99,0,0,0,0

OK
  
Wed Oct 30 11:26:23 2024 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0

OK
  
Wed Oct 30 11:26:51 2024 : /dev/ttyUSB2 AT+CMGL=4
+CMS ERROR: 303

TIMEOUT ERROR
  
Wed Oct 30 11:26:57 2024 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0

OK

Posted: **Thu Oct 31, 2024 10:14 am**

Still down. Never been down this long. Will be about 24 hours.

* I tried reflashing the modem firmware via QFirehose. No dice.

Posted: **Thu Oct 31, 2024 2:01 pm**

Looks like your modem is not connecting to the network, There could be a number of reasons for that, including a router failure, modem, and carrier/network issue. The first step is to test the SIM card in a phone to make sure you can call and access the web. If it's not working in a phone then it's a carrier/network issue.
If the SIM is working in a phone, it's probably a router or modem issue which needs to be narrowed down one at a time.
It's best to test it with a spare modem, if it's working, then it's just you old modem. If not, it's the router.
The Carrier/network may also block you IMEI due to recent changes, something to keep in mind.
.
.
Also, recently I have noticed a weird crash due to a bug in some routers/modem/firmware combinations, when accessing CDN sites (Content Delivery Network), it crashes the router's kernel. CDN is used by many sites, it's not something you can see unless you analyze the traffic with something like UBO or WireShark. While they can be blocked one by one, it's simply not practical, so it's just to just update the firmware and/or modem, or even the router. Another workaround is to set an auto-restart of the modem, but it's annoying having to wait 2-3 minutes every time it happens and will keep happening whenever accessing a CDN served website. Of course a power off/on also fixes it.

Whenever the router goes down you can take a look at the kernel log by going to Settings > Status > Kernel Log
If you see something like this, it's likely the CDN bug.

[1561548.253269] ipheth 1-1:4.2: ipheth_rcvbulk_callback: urb status: -79

Posted: **Thu Oct 31, 2024 2:16 pm**

I'm not sure if I understand. The router itself never went down, just the ability for the modem to connect. When it did lose the connection it had lost it's IPv4 and IPv6 addesses and the typical reboots didn't resolve the issue. Unless you mean a certain site cause the connection to go down (CDN)? The only thing I see in the kernal log is "14.900094] usbcore: registered new interface driver ipheth", but since reflashing etc I understand if it's too late now. Any ideas on what I can do? I hope the modem isn't fried. I did try going to a 10-2022 build I notice the scripts were a little different than 9-10-21 firmware, but it was the same thing, it just would just sit there and not connect.

I did test the sim in the tablet and it worked. and the right sim and imei numbers come up on network status page.

Posted: **Thu Oct 31, 2024 2:20 pm**

Mr.Taco wrote: ↑Thu Oct 31, 2024 2:16 pm I'm not sure if I understand. The router itself never went down, just the ability for the modem to connect. When it did lose the connection it had lost it's IPv4 and IPv6 addesses and the typical reboots didn't resolve the issue. Unless you mean a certain site cause the connection to go down (CDN)? The only thing I see in the kernal log is "14.900094] usbcore: registered new interface driver ipheth", but since reflashing etc I understand if it's too late now. Any ideas on what I can do? I hope the modem isn't fried.

The router doesn't go down, the connection does due to the kernel crash. Anyway I added some more info above, read it again.
If a reboot doesn't reconnect the router/modem even temporarily, then it's probably not the CDN bug.

Posted: **Thu Oct 31, 2024 2:23 pm**

yeah sounds like router or modem

could changing modes possibly work QMI to ECM?

Posted: **Thu Oct 31, 2024 3:39 pm**

I ordered another modem.

* I'm gonna try nuking it.

** Tried AT+QPRTPARA=3 (sim out) which required correcting IMEI, and rebooting. Same issue, nogo. Hopefully new modem will be here soon.

Posted: **Thu Oct 31, 2024 6:22 pm**

got connected via AT+QCFG="usbnet",1

* I.e. showed carrier in network status via ethernet mode

Posted: **Thu Oct 31, 2024 7:43 pm**

Mr.Taco wrote: ↑Thu Oct 31, 2024 6:22 pm got connected via AT+QCFG="usbnet",1

* I.e. showed carrier in network status via ethernet mode

So you're back online via ethernet and WiFi?
It may have been just a modem software/setting corruption.

Posted: **Thu Oct 31, 2024 7:58 pm**

I FIXED IT

Posted: **Thu Oct 31, 2024 8:15 pm**

BillA wrote: ↑Thu Oct 31, 2024 7:43 pm
Mr.Taco wrote: ↑Thu Oct 31, 2024 6:22 pm got connected via AT+QCFG="usbnet",1

* I.e. showed carrier in network status via ethernet mode

So you're back online via ethernet and WiFi?
It may have been just a modem software/setting corruption.

It didn't work in ethernet mode, but it did connect. Also tried mbim:

AT+QCFG="usbnet",0 - QMI/PPP/Default
AT+QCFG="usbnet",1 - ECM
AT+QCFG="usbnet",2 - MBIM

only ethernet would connect but i couldnt really do anything and only ipv4. So I put it back to QMI mode. Then i started messing with AT+CGDCONT commands

Code: Select all

AT+CGDCONT=1;+CGDCONT=2;+CGDCONT=3;+CGDCONT=4;+CGDCONT=5;+CGDCONT=6;+CGDCONT=7;+CGDCONT=8;+CGDCONT=9;+CGDCONT=10;+CFUN=0;+CFUN=1

and

Code: Select all

AT+QMBNCFG=“AutoSel”,0
AT+QMBNCFG=“Deactivate”
AT+CFUN=1,1

This nuked the predefined APNs so only VZWINTERNET existed. When I tried to connect it still would not connect, BUT it seemed to progress further in the debud log.

So then I reflashed the modem again and it connected!

I was hoping it would restore all the default APNs but VZWINTERNET is still only one there. Do you know how I can restore it back to how it was?

I wonder if I do

Code: Select all

AT+QPRTPARA=3

again if that will bring back all the built in APNs? Aka from this:

Code: Select all

AT+CGDCONT?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

Back to this:

Code: Select all

AT+CGDCONT?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CGDCONT: 6,"IPV4V6","VZWCLASS6","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

Posted: **Thu Oct 31, 2024 10:17 pm**

Very interestng. So AT+QPRTPARA=3 and a hard boot brought back the default APNs and with it the same connectivity issue of not connecting. Hahah, I just broke it back to normal! It kept the same IMEI/didn't restore it, but i didn't trust it so I issued it again to make sure it won't secretly revert. That would suck.

So I can nuke APNs again, or I can try flashing the modem again--Basically do the same steps I did before to restore connection. I'll report back. I'll try reflashing modem.

Posted: **Fri Nov 01, 2024 12:01 am**

So flashing the modem didn't work outright.

Recreating the steps I did this:

Code: Select all

AT+CGDCONT=1;+CGDCONT=2;+CGDCONT=3;+CGDCONT=4;+CGDCONT=5;+CGDCONT=6;+CGDCONT=7;+CGDCONT=8;+CGDCONT=9;+CGDCONT=10;+CFUN=0;+CFUN=1

Then I flashed the modem firmware via QFirehose. Then reboot. And bam, connected QMI mode like before it went down. For some reason now, it doesn't like those other APNs and needs a fresh flash. Whatever. Glad it's resolved. I now have an extra modem coming my way, haha.

Edit: If anyone needs the newest firmware as of today for the EP06-A, one can download it from: https://fw.gl-inet.com/download/EP06A-m ... 01.009.zip

(from https://docs.gl-inet.com/router/en/4/tu ... _software/ )

Posted: **Fri Nov 01, 2024 1:14 am**

Mr.Taco wrote: ↑Fri Nov 01, 2024 12:01 am So flashing the modem didn't work outright.

Recreating the steps I did this:
Code: Select all
AT+CGDCONT=1;+CGDCONT=2;+CGDCONT=3;+CGDCONT=4;+CGDCONT=5;+CGDCONT=6;+CGDCONT=7;+CGDCONT=8;+CGDCONT=9;+CGDCONT=10;+CFUN=0;+CFUN=1
Then I flashed the modem firmware via QFirehose. Then reboot. And bam, connected QMI mode like before it went down. For some reason now, it doesn't like those other APNs and needs a fresh flash. Whatever. Glad it's resolved. I now have an extra modem coming my way, haha.

Glad it worked, having an extra modem is not a bad thing, just in case. heh
All those commands look familiar, wrote them many noons ago.

Wireless Joint

NEXQ6GO - EP06A - Stuck On Connecting (RESOLVED)

NEXQ6GO - EP06A - Stuck On Connecting (RESOLVED)

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting

Re: NEXQ6GO - EP06A - Stuck On Connecting (RESOLVED)

Re: NEXQ6GO - EP06A - Stuck On Connecting (RESOLVED)

Re: NEXQ6GO - EP06A - Stuck On Connecting (RESOLVED)