Mifi: LTE connected but no Internet

alzhao · 2018-04-26T08:51:24.333Z

can you ssh to the router and check if the router can use the Internet.

ssh root@192.168.8.1

$ ping 8.8.8.8

mifiuser1 · 2018-04-26T08:54:11.150Z

No that is not possible. That is what I also posted in my first post:

I am able to ping the default gateway (in that case 10.29.28.2), but not something like 8.8.8.8.

alzhao · 2018-04-26T09:27:34.451Z

that is a problem. I have no idea.

Did you have any other cables connecting to the WAN port?

mifiuser1 · 2018-04-26T09:30:16.170Z

No. The only thing that is currently connected is a UART to USB adapter in order to log in via serial and of course the micro usb cable for power.

alzhao · 2018-04-26T09:31:20.309Z

can you try again adding wwan0 as interface

ping -I wwan0 8.8.8.8

mifiuser1 · 2018-04-26T10:31:49.645Z

Does also not work

root@GL-MIFI:/# ping -I wwan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes

alzhao · 2018-04-26T10:38:05.797Z

@rene, any chance you can have a check? Seems everything is fine.

mifiuser1 · 2018-04-27T10:18:01.957Z

Just want to mention that I ordered a second one which should arrive on Monday. Maybe the first one has some hardware failure if you say that all settings are correct.

mifiuser1 · 2018-05-02T08:10:40.939Z

So the new one I received two days ago and it was working out of the box, BUT with the 3g module instead of using the qmi mode and therefore using /dev/ttyUSB2 instead of /dev/cdc-wdm0. So I reconfigured the other one to the 3g mode and also using /dev/ttyUSB2 and it was working as well.

Then I switched the new one in the webinterface to 4g, then using qmi and /dev/cdc-wdm0 and it was still working. So I did the same to the other one and this is now working as well with that setup. I didn’t change anything else so could there be the possibility that something on the EC25 chip changed or is set/removed while switching from the 3g-module to qmi? Or is there a reset command for the chip that can be issued in qmi mode that could have caused this issue?

I only want to get to the root cause of this so that no one else is stuck at the same point

Config set (out-of-box)

config interface ‘modem’
option proto ‘3g’
option ifname ‘3g-modem’
option device ‘/dev/ttyUSB2’
option country ‘country21’
option sp ‘isp2’
option dialnum ‘*99#’
option apn ‘internet.telekom’
option username ‘telekom’
option password ‘tm’
option metric ‘40’

Config now set in qmi mode

config interface ‘modem’
option ifname ‘wwan0’
option service ‘fdd-lte’
option proto ‘qmi’
option device ‘/dev/cdc-wdm0’

alzhao · 2018-05-02T11:57:59.272Z

Seems this is a bug in qmi script and didn’t get fixed. The script affect the modem. Seems what have done get the modem fixed.

mifiuser1 · 2018-05-04T07:08:48.415Z

Okay thanks. That makes it clearer. And does that mean it has to be fixed on your end?

alzhao · 2018-05-05T08:32:21.117Z

Yes. We need to fix.

RVIT · 2018-07-10T00:01:41.413Z

Hi! Was this issue fixed? I’m asking because I’m trying to follow the poster’s instructions on moving back to the 3g module, as it appears I’ve screwed something up using uqmi commands. I’m unable to restore a connection to my lte provider now on /dev/ttyUSB2. Here’s what’s showing in my log file (looks like lots of duplicate ‘modem’ iface entries, but only one when I check /etc/config/network).

Mon Jul 9 23:34:09 2018 daemon.info gl-health>>: AP Ok=1
Mon Jul 9 23:34:09 2018 daemon.info gl-health>>: network(caIfnames) = wan wan6 tethering modem modem modem modem modem modem modem modem modem modem modem
Mon Jul 9 23:34:09 2018 daemon.info gl-health>>: STA Ok=1
Mon Jul 9 23:34:09 2018 daemon.info gl-health>>: Everthing is OK!!!
Mon Jul 9 23:34:09 2018 daemon.info gl-health>>: check wpa runing =
Mon Jul 9 23:34:09 2018 daemon.info pppd[19220]: Exit.
Mon Jul 9 23:34:09 2018 daemon.notice netifd: Interface ‘modem’ is now down
Mon Jul 9 23:34:09 2018 daemon.notice netifd: Interface ‘modem’ is setting up now
Mon Jul 9 23:34:11 2018 daemon.notice pppd[19343]: pppd 2.4.7 started by root, uid 0
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: abort on (BUSY)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: abort on (NO CARRIER)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: abort on (ERROR)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: report (CONNECT)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: timeout set to 10 seconds
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: send (AT&F^M)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: expect (OK)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: AT&F^M^M
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: OK
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: – got it
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: send (ATE1^M)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: expect (OK)
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: ^M
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: ATE1^M^M
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: OK
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: – got it
Mon Jul 9 23:34:12 2018 local2.info chat[19419]: send (AT+CGDCONT=1,“IP”,“fast.t-mobile.com”^M)
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: timeout set to 30 seconds
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: expect (OK)
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: ^M
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: AT+CGDCONT=1,“IP”,“fast.t-mobile.com”^M^M
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: ERROR
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: – failed
Mon Jul 9 23:34:13 2018 local2.info chat[19419]: Failed (ERROR)
Mon Jul 9 23:34:13 2018 daemon.err pppd[19343]: Connect script failed

Any ideas?

Sidac · 2018-08-30T08:05:11.949Z

Same problem as above, any idea on how to resolve?

alzhao · 2018-09-03T10:24:10.531Z

I am not sure if the modem has problems.

Anyway you can try v3 firmware for MiFi which is totally new. Not sure if the QMI problem was fixed. We fixed several bugs in QMI scripts already.

kefir · 2019-08-18T08:27:01.782Z

Thanks for this, I have a MiFi device that was working fine, then it suddently stopped with this exact same issue. 4G connected, I couldn’t ping anything, but curiously nslookup worked using 127.0.0.1 or using one of the dns servers shown in the output from:

uqmi -d /dev/cdc-wdm0 --get-current-settings

so clearly something was getting through. No other DNS servers worked, however.

Anyway, the fix was simply to open the web interface, manual config of the 4G device, change the device from /dev/cdc-wm0 to /dev/ttyUSB2, and then it immediately worked. After that I changed back to /dev/cdc-wm0, and it’s still working.

Thanks for sharing!

alzhao · 2019-08-19T06:59:47.371Z

Seems the modem has some problems and it fixed itself when you set up manually.

kefir · 2019-08-19T09:33:31.011Z

I had switched sim, rebooted the device, configured manually several times, and also tried automatic config, none of these things changed anything. So simply doing a manual config didn’t work for me. Only when I changed to ttyUSB2 did it immediately start working, and then still worked when I changed the device back. It’s been disfunctional for a few weeks, so I’ve tried a lot of stuff.

robotluo · 2019-08-23T15:41:16.571Z

This may be a bug, so I’ll try to reproduce it first

expert · 2019-10-06T08:50:06.149Z

@robotluo @alzhao
Have you guys solved this problem? I have same issue with new unit: MiFi: No internet connection via LTE modem