GL-MiFi support for EC25-AF?

Wondering if anyone has had success with the Quectel EC25-AF in either a MiFi or Spitz from GL? I figured these modules would be plug-and-play since part of the same series as the default Quectel EC25-A. So far I’ve not been able to establish a connection.

I’m testing in a GL-MiFi with a config and SIM I can confirm connects just fine when using the EC25-A. If I power down, replace the module with the EC25-AF, I get the following output in the system log when attempting to connect:

Sat Jan 12 02:23:52 2019 daemon.notice netifd: Interface 'modem' is now down
Sat Jan 12 02:23:52 2019 daemon.notice netifd: Interface 'modem' is setting up now
Sat Jan 12 02:23:58 2019 daemon.notice netifd: modem (25337): "Failed to connect to service"
Sat Jan 12 02:24:06 2019 daemon.err gl_monitor[4382]: sh: 0: unknown operand
Sat Jan 12 02:24:08 2019 daemon.notice netifd: modem (25337): "Failed to connect to service"
Sat Jan 12 02:24:13 2019 daemon.notice netifd: modem (25337): "Unknown error"
Sat Jan 12 02:24:13 2019 daemon.notice netifd: modem (25337): Waiting for network registration
Sat Jan 12 02:24:15 2019 daemon.err gl_monitor[4382]: sh: 0: unknown operand
Sat Jan 12 02:24:18 2019 daemon.notice netifd: modem (25337): Starting network modem
Sat Jan 12 02:24:24 2019 daemon.notice netifd: modem (25337): Failed to connect to service
Sat Jan 12 02:24:24 2019 daemon.notice netifd: modem (25337): Unable to obtain client ID
Sat Jan 12 02:24:24 2019 daemon.notice netifd: modem (26223): Stopping network modem
Sat Jan 12 02:24:24 2019 daemon.notice netifd: modem (26223): Command failed: Permission denied
Sat Jan 12 02:24:24 2019 daemon.notice netifd: Interface 'modem' is now down
Sat Jan 12 02:24:24 2019 daemon.notice netifd: Interface 'modem' is setting up now
Sat Jan 12 02:24:24 2019 daemon.err gl_monitor[4382]: sh: 0: unknown operand
Sat Jan 12 02:24:33 2019 daemon.err gl_monitor[4382]: sh: 0: unknown operand
Sat Jan 12 02:24:35 2019 daemon.notice netifd: modem (26231): "Failed to connect to service"
Sat Jan 12 02:24:40 2019 daemon.notice netifd: modem (26231): "Unknown error"
Sat Jan 12 02:24:40 2019 daemon.notice netifd: modem (26231): Waiting for network registration
Sat Jan 12 02:24:43 2019 daemon.err gl_monitor[4382]: sh: 0: unknown operand
Sat Jan 12 02:24:45 2019 daemon.notice netifd: modem (26231): Starting network modem
Sat Jan 12 02:24:50 2019 daemon.notice netifd: modem (26231): Failed to connect to service
Sat Jan 12 02:24:50 2019 daemon.notice netifd: modem (26231): Unable to obtain client ID
Sat Jan 12 02:24:51 2019 daemon.notice netifd: modem (27021): Stopping network modem
Sat Jan 12 02:24:51 2019 daemon.notice netifd: modem (27021): Command failed: Permission denied
Sat Jan 12 02:24:51 2019 daemon.notice netifd: Interface 'modem' is now down
Sat Jan 12 02:24:51 2019 daemon.notice netifd: Interface 'modem' is setting up now

what is the difference between EC25-A and EC25-AF?

The EC25-A has support for LTE bands 2/4/12. The EC25-AF supports LTE bands 2/4/5/12/13/14/66/71.

I like to know how to make EC25-AF work as well. then I can use one mifi with both t-mobile and verizon sim.

We use Verizon, and they do not support the EC25-A, only the EC25-AF. Is there any news on compatibility for Verizon?

Also, looking at the EC06-A, but it appears to still be in testing/development with Verizon in N.A. Would love to see utilize the Spitz as a Mesh/LTE gateway, with its dual band 2/5G radios.

Does anyone have any knowledge or experience getting this to work on the Verizon network?

I think EC25-AF is supported in recent firmware. If it still does not work, pls let me know.

I installed the testing firmware openwrt-mifi-3.022-0430.bin to see if the EC25-AF would work. Although it looks more promising that perhaps the firmware recognized the board, this firmware reports a SIM card error with both the EC25-A and the EC25-AF. I’ve used two different SIM cards and swapped out the modem cards twice. The previous testing firmware that I was running on worked fine, so I’m pretty sure there is a bug in the new firmware.

Thanks

@peng1can Any luck with the EC25-AF? I’m considering making my purchase, as I see the AF variant is listed now on the “Shop” page, rather than the A variant; but hoping to get a confirmation before I buy an expensive brick or two…

I can confirm the EC25-AF is operational in the MiFI in the US. Depending on your carrier, the EC25-AF’s onboard carrier profiles may or may not be certified, so check that on the Quectel website.

I had a Mifi with the EC-25A working fine on T-Mobile. Removing the A and replacing it with the AF results in the Mifi seeing the modem, recognizing that it’s on T-Mobile, but not pulling an IP address or doing anything else. Placing the A back in the unit restores connectivity. Is there anything more we should need to do to get the AF to work?

I see that the EC-25AF has a t-mobile certificate on the quectel site, so it seems like the card should work with Tmobile.

Thanks

A few firmware updates later, and I still have the same problem. GUI shows T-Mobile, several bars of 4G service, but no internet with the EC25-AF.

I am using EC25-AF and T-Mobile and it works fine.

In the UI there is carrier info. Can you post that?

I have the same issue as peng1can. The first time I fired it up I got a text message from T-Mobile welcoming me to the system. As expected I got a text blocked reply via text when trying to send a text. For some reason that makes me believe the thing is working at least on some level.

From a command line I can ping 8.8.8.8 and 8.8.4.4 but no other ip. If I ping by name, it correctly gives the ip address of the domain but again does not ping.

From the 192.168.8.1 menu using the AT Commands link everything appears to talk to the modem. A Request Network Information gives the following -
+QNWINFO: “FDD LTE”,“310260”,“LTE BAND 2”,725

It also shows it gets an IP starting with 6, which is Army Information Systems Center so I seriously doubt that …

Is there a way to determine if the problem is a device issue or an account type issue? I’ve purchased an account that is purposed for low bandwidth M2M devices that use a web interface. I expected those devices to be able to reach out and connect to their server, update, etc., and to be able to reach in to them for configuration and control. I read on another thread that they had an account type difference, but these people keep telling me it should work fine for this purpose.

Thanks

Hello,

For special account types, you usually need to set up APN manually. You can ask the operator, which APN should you use

The issue here was the account type that I assigned this sim was ‘non-routable.’ When we changed the account type the unit immediately worked as expected.

Which leaves me then with the question, can we ‘bridge’ the GL-MiFi? If I am reading correctly (and I usually miss something important) non-routed basically means the device attached to the modem is consuming or creating the data on the IP assigned to the card. Does bridging, or some other setting, provide that functionality?

The non-routable accounts are much less expensive.

Will the operator assign you static IP?