nexq6go - can't connect

[gaddman]

Hi. Just bought the nexq6go-u, Quectel EM12-G, the adapter, antenna pigtail adapters, and the good power supply. Using stock antennas for now. I use Verizon, and have a postpaid data plan on an iPad. I get 2 bars LTE on the iPad and usable internet. I want to use that sim in the router.

I have everything hooked up and configured per the tutorials.

I can't seem to get the modem connected to the tower. I'm not sure if the modem is even starting up correctly. I never get past the status of "connecting"...never see any signal strength. I can put the sim back in the ipad and it works.

It looks like the sim is being recognized. I can see the modem information...my Line number, etc. I've tried no ttl, ttl 64, 65, and 117. Even adding IP6 to the tables. Tried different AT commands from various posts that I thought might have an effect. Nothing seems to help.

I've just reset the router and re-entered the APN, Timezone, etc. just to be at a fresh start.

I'm starting to wonder if I don't have something connected correctly. I used the the A and D antenna ports. I think thats what they are labelled. I did not use G....thats for GPS, right? Everything snapped in easy enough. Taped up the exposed connections of the adapter pigtails to antennas. Opened it back up for a double check and it all looks good.

Anyway, not sure what to post here that would be most helpful. Here's some of the log data starting near where I think the problem is. Let me know if any other data or screenshots would be helpful. Appreciate any help!


Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *****************************************************************
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: * Switched to : 2c7c:0512
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *****************************************************************
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 1
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 2 option
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 3 option
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 4 option
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 5 option
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 6 cdc_mbim
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 7 cdc_mbim
Mon Oct 5 13:21:29 2020 user.notice Log Print : Driver Name : 8 cdc_mbim
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *****************************************************************
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: * ProtoFind returns : 3
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: *****************************************************************
Mon Oct 5 13:21:29 2020 user.notice usb-modeswitch: Found Modem1
Mon Oct 5 13:21:30 2020 user.notice usb-modeswitch: Connecting a MBIM Modem
Mon Oct 5 13:21:30 2020 user.notice Create Connection: Start MBIM Connection
Mon Oct 5 13:21:31 2020 kern.notice kernel: [ 76.709745] random: crng init done
Mon Oct 5 13:21:35 2020 user.notice Create Connection: MBIM Comm Port : /dev/ttyUSB2
Mon Oct 5 13:21:39 2020 user.notice Create Connection: Quectel Unsolicited Responses Disabled
Mon Oct 5 13:21:51 2020 user.notice Get Profile: Default Profile Used
Mon Oct 5 13:21:51 2020 user.notice Create Connection: Profile for Modem1 sets interface to WAN1
Mon Oct 5 13:21:51 2020 user.notice Create Connection: Modem1 is using WAN1
Mon Oct 5 13:21:54 2020 user.notice sms process: SMS Supported
Mon Oct 5 13:21:57 2020 user.notice Create Connection: Pincode in script
Mon Oct 5 13:21:57 2020 user.notice Create Connection: Attempting to Connect
Mon Oct 5 13:21:59 2020 user.notice Create Connection: Using Netifd Method
Mon Oct 5 13:22:00 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Mon Oct 5 13:22:00 2020 user.notice MBIM Connect: Stopping network
Mon Oct 5 13:22:00 2020 daemon.notice netifd: wan1 (3832): Command failed: Permission denied
Mon Oct 5 13:22:00 2020 daemon.notice netifd: Interface 'wan1' is now down
Mon Oct 5 13:22:00 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Mon Oct 5 13:22:01 2020 user.notice MBIM Connect: Query radio state
Mon Oct 5 13:22:01 2020 user.notice MBIM Connect: Reading capabilities
Mon Oct 5 13:22:01 2020 user.notice MBIM Connect: Check PIN state
Mon Oct 5 13:22:01 2020 daemon.notice netifd: wan1 (3846): required pin: 3 - pin2
Mon Oct 5 13:22:01 2020 daemon.notice netifd: wan1 (3846): remaining attempts: 3
Mon Oct 5 13:22:01 2020 user.notice MBIM Connect: PIN unlocked
Mon Oct 5 13:22:01 2020 user.notice MBIM Connect: Checking subscriber
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 user.notice Get Profile: Default Profile Used
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 daemon.notice netifd: wan1 (3846): uci: Entry not found
Mon Oct 5 13:22:02 2020 user.notice MBIM Connect: Register with network
Mon Oct 5 13:22:02 2020 user.notice MBIM Connect: Attach to network
Mon Oct 5 13:22:06 2020 user.notice sms process: Reread SMS Messages on Modem 1
Mon Oct 5 13:22:17 2020 daemon.notice netifd: wan1 (3846): ERROR: mbim message timeout
Mon Oct 5 13:22:17 2020 user.notice MBIM Connect: Failed to attach to network
Mon Oct 5 13:22:17 2020 user.notice root: mbim bringup failed, retry in 15s
Mon Oct 5 13:22:32 2020 user.notice MBIM Connect: Stopping network
Mon Oct 5 13:22:33 2020 daemon.notice netifd: wan1 (4447): message not long enough
Mon Oct 5 13:22:33 2020 daemon.notice netifd: wan1 (4447): Command failed: Permission denied
Mon Oct 5 13:22:33 2020 daemon.notice netifd: Interface 'wan1' is now down
Mon Oct 5 13:22:33 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Mon Oct 5 13:22:33 2020 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='wan1'
Mon Oct 5 13:22:34 2020 user.notice MBIM Connect: Query radio state
Mon Oct 5 13:22:34 2020 user.notice MBIM Connect: Reading capabilities
Mon Oct 5 13:22:35 2020 user.notice MBIM Connect: Failed to read modem caps
Mon Oct 5 13:22:35 2020 user.notice root: mbim bringup failed, retry in 15s
Mon Oct 5 13:22:50 2020 user.notice MBIM Connect: Stopping network
Mon Oct 5 13:22:50 2020 daemon.notice netifd: wan1 (4830): Command failed: Permission denied
Mon Oct 5 13:22:50 2020 daemon.notice netifd: Interface 'wan1' is now down
Mon Oct 5 13:22:50 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Mon Oct 5 13:22:50 2020 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='wan1'
Mon Oct 5 13:22:51 2020 user.notice MBIM Connect: Query radio state
Mon Oct 5 13:22:51 2020 user.notice MBIM Connect: Reading capabilities
Mon Oct 5 13:22:51 2020 user.notice MBIM Connect: Check PIN state
Mon Oct 5 13:22:51 2020 daemon.notice netifd: wan1 (4841): required pin: 3 - pin2
Mon Oct 5 13:22:51 2020 daemon.notice netifd: wan1 (4841): remaining attempts: 3
Mon Oct 5 13:22:51 2020 user.notice MBIM Connect: PIN unlocked
Mon Oct 5 13:22:51 2020 user.notice MBIM Connect: Checking subscriber
Mon Oct 5 13:22:52 2020 daemon.notice netifd: wan1 (4841): uci: Entry not found

[Didneywhorl]

A few things.

Clear out your APNs by running

Code: Select all

AT+CGDCONT?

Then for every one that it returns in the output, run the following commands to blank them out:

Code: Select all

AT+CGDCONT=1

Code: Select all

AT+CGDCONT=2

Code: Select all

AT+CGDCONT=16

etc

etc

Running the command like that says set info at position 1 (2,3,16,etc) as follows ... <blank>... and so it does, it fills in the info with nothing.

At least one of them will error out, don't worry, it's normal.

Run your modem in MBIM mode.

Code: Select all

AT+QCFG="usbnet",2

Set it to LTE only

Code: Select all

AT+QCFG="NWSCANMODE",3,1

Then run

Code: Select all

AT+QPRTPARA=1

This makes sure all of your changes are saved into memory. It doesn't need to be run again. It's a one time precaution.

Then last run...

Code: Select all

AT+CFUN=1,1

This last command hard reboots the modem, which is required to make some of the previous changes. Simply rebooting the router will not hard boot the modem. Truly power cycling the router will though.


NEXT!

Verizon is a pure punk at the moment. IPV4 and IPV6 TTL/HL settings are generally require to get around Hotspot limits, but wont stop Verizon from blocking your device. Unfortunately that may require an IMEI change. The ideal is to use an IMEI of a device you own, and have registered the SIM to already, and copy that IMEI to the modem of want. This is technically illegal according to the FCC in the US. The Android developers and hackers have it figured out though and gladly post the AT command for "Restoring IMEI Number for mtk device" publicly on their forums. We do not allow it here.

After clearing out the APNs and making sure it is set in Modem-->Connection Profile-->APN, make sure you do a full power cycle.


Also check your SMS messages and your account and make sure Verizon didnt shut the SIM down.

[gaddman]

Thanks for the response. Still no connection
I did everything in your post. When clearing out the APNs, there were 5 or 6. 1 and 3 returned errors. In the debug log, they both come up with "vzwinternet", and that is what is in the connection profile. I did notice in the connection profile, it also has "root" as connection user name. I assume that is correct? I've seen it blank in some instructions. It won't let me blank it out...always comes back as "root". I have no sms messages. And my account looks ok. I can put the sim back in the ipad and it works fine. And I had already found that "other" thing you mentioned. Whether it's using hotspot data or not, shouldn't I get some sort of connection?

I've tried different variations of TTL settings. The latter being the current settings.

iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
or
iptables -t mangle -I POSTROUTING -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -j TTL --ttl-set 117
ip6tables -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
or
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117

Thanks again! Looking forward to more advice.

[Didneywhorl]

Yeah, the TTL is moot point until you get on the network. Your System Log shows your being denied someway.

[MattB29]

I also had the user name being root that was persistent. It did not go away until I did a hard reset boot (on a Wg3526 build with the Chinese factory firmware) and reload of Golden Orb firmware. Once I did that the username would remain blank though I do not know if that is your problem with getting a connection. What router firmware are you running and have you tried to reload it?

[gaddman]

Firmware Version GoldenOrb_2020-04-04. It was preloaded. I generated an archive (backup) as soon as I got the thing.
After a couple of days of messing with settings I did a "perform reset", and I've restored my backup. But I have not flashed a new firmware image.

[Adm1jtg]

Hmmm current wifix versions have a date of 5-16 and current rooter versions are dated 3-1

i would try flashing one of the above versions

[gaddman]

I can't seem to find the firmware (any version) for the NEXQ6GO. It's not listed on either of the firmware locations mentioned here: https://thewirelesshaven.com/wifix-router-firmware/

I guess I have to ask someone from The Wireless Haven to provide it to me?

[Adm1jtg]

ask if there is a version of rooter here:
https://forums.whirlpool.net.au/thread/3vx1k1r3?p=715

and I would also message The Wireless Haven

[Didneywhorl]

Hmmm current wifix versions have a date of 5-16 and current rooter versions are dated 3-1

i would try flashing one of the above versions

NEXQ6GO firmware is loaded with its own firmware. There is no updated version yet

[gaddman]

Great! One less thing to worry about. So is it definitely a software problem? Can I rule out user error on the initial build...like connectors or wrong antennas screwed into the wrong place? Maybe I have to get further down the road to rule out a physical issue? Wifi is working, so I know that side is working.

Should the modem connection profile have a user name? Mine is hard-coded as "root".

[gaddman]

I assume this is the part of the system log that is failing...the bold Permission denied lines? Looks like line 3 ...login with "root" ...was successful.

Anymore ideas?

Wed Oct 7 09:50:49 2020 user.notice usb-modeswitch: Found Modem1
Wed Oct 7 09:50:49 2020 user.notice usb-modeswitch: Connecting a MBIM Modem
Wed Oct 7 09:50:50 2020 user.notice Create Connection: Start MBIM Connection
Wed Oct 7 09:50:52 2020 daemon.err uhttpd[1565]: luci: accepted login on /admin/status/syslog for root from 192.168.1.131
Wed Oct 7 09:50:53 2020 kern.notice kernel: [ 76.479807] random: crng init done
Wed Oct 7 09:50:55 2020 user.notice Create Connection: MBIM Comm Port : /dev/ttyUSB2
Wed Oct 7 09:50:58 2020 user.notice Create Connection: Quectel Unsolicited Responses Disabled
Wed Oct 7 09:51:09 2020 user.notice Get Profile: Default Profile Used
Wed Oct 7 09:51:09 2020 user.notice Create Connection: Profile for Modem1 sets interface to WAN1
Wed Oct 7 09:51:10 2020 user.notice Create Connection: Modem1 is using WAN1
Wed Oct 7 09:51:12 2020 user.notice Create Connection: Pincode in script
Wed Oct 7 09:51:12 2020 user.notice Create Connection: Attempting to Connect
Wed Oct 7 09:51:15 2020 user.notice Create Connection: Using Netifd Method
Wed Oct 7 09:51:15 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Wed Oct 7 09:51:15 2020 user.notice MBIM Connect: Stopping network
Wed Oct 7 09:51:16 2020 daemon.notice netifd: wan1 (3367): Command failed: Permission denied
Wed Oct 7 09:51:16 2020 daemon.notice netifd: Interface 'wan1' is now down
Wed Oct 7 09:51:16 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Wed Oct 7 09:51:16 2020 user.notice MBIM Connect: Query radio state
Wed Oct 7 09:51:16 2020 user.notice MBIM Connect: Reading capabilities
Wed Oct 7 09:51:16 2020 user.notice MBIM Connect: Check PIN state
Wed Oct 7 09:51:16 2020 daemon.notice netifd: wan1 (3383): required pin: 3 - pin2
Wed Oct 7 09:51:16 2020 daemon.notice netifd: wan1 (3383): remaining attempts: 3
Wed Oct 7 09:51:16 2020 user.notice MBIM Connect: PIN unlocked
Wed Oct 7 09:51:16 2020 user.notice MBIM Connect: Checking subscriber
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): Usage: uci [<options>] <command> [<arguments>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383):
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): Commands:
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): batch
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): export [<config>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): import [<config>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): changes [<config>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): commit [<config>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): add <config> <section-type>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): add_list <config>.<section>.<option>=<string>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): del_list <config>.<section>.<option>=<string>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): show [<config>[.<section>[.<option>]]]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): get <config>.<section>[.<option>]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): set <config>.<section>[.<option>]=<value>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): delete <config>[.<section>[[.<option>][=<id>]]]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): rename <config>.<section>[.<option>]=<name>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): revert <config>[.<section>[.<option>]]
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): reorder <config>.<section>=<position>
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383):
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): Options:
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -c <path> set the search path for config files (default: /etc/config)
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -d <str> set the delimiter for list values in uci show
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -f <file> use <file> as input instead of stdin
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -m when importing, merge data into an existing package
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -n name unnamed sections on export (default)
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -N don't name unnamed sections
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -p <path> add a search path for config change files
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -P <path> add a search path for config change files and use as default
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -q quiet mode (don't print error messages)
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -s force strict mode (stop on parser errors, default)
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -S disable strict mode
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): -X do not use extended syntax on 'show'
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383):
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 user.notice Get Profile: Default Profile Used
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 daemon.notice netifd: wan1 (3383): uci: Entry not found
Wed Oct 7 09:51:17 2020 user.notice MBIM Connect: Register with network
Wed Oct 7 09:51:17 2020 user.notice MBIM Connect: Attach to network
Wed Oct 7 09:51:19 2020 user.notice sms process: SMS Supported
Wed Oct 7 09:51:27 2020 user.notice sms process: Reread SMS Messages on Modem 1
Wed Oct 7 09:51:32 2020 daemon.notice netifd: wan1 (3383): ERROR: mbim message timeout
Wed Oct 7 09:51:32 2020 user.notice MBIM Connect: Failed to attach to network
Wed Oct 7 09:51:32 2020 user.notice root: mbim bringup failed, retry in 15s
Wed Oct 7 09:51:47 2020 user.notice MBIM Connect: Stopping network
Wed Oct 7 09:51:47 2020 daemon.notice netifd: wan1 (3704): message not long enough
Wed Oct 7 09:51:48 2020 daemon.notice netifd: wan1 (3704): Command failed: Permission denied
Wed Oct 7 09:51:48 2020 daemon.notice netifd: Interface 'wan1' is now down
Wed Oct 7 09:51:48 2020 daemon.notice netifd: Interface 'wan1' is setting up now
Wed Oct 7 09:51:48 2020 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='wan1'
Wed Oct 7 09:51:48 2020 user.notice MBIM Connect: Query radio state
Wed Oct 7 09:51:48 2020 user.notice MBIM Connect: Reading capabilities

[Didneywhorl]

Change the modem back to QMI mode. It may be an issue with MBIM mode on your network.

Code: Select all

AT+QCFG="usbnet",0

then

Code: Select all

AT+CFUN=1,1

[Didneywhorl]

You don't seem to have any issues with the software, and you don't need any user info in the connection profile.

Your definitely getting onto the network, and then its booting you off.

Wed Oct 7 09:51:17 2020 user.notice MBIM Connect: Register with network
Wed Oct 7 09:51:17 2020 user.notice MBIM Connect: Attach to network
Wed Oct 7 09:51:19 2020 user.notice sms process: SMS Supported

...


Wed Oct 7 09:51:32 2020 daemon.notice netifd: wan1 (3383): ERROR: mbim message timeout
Wed Oct 7 09:51:32 2020 user.notice MBIM Connect: Failed to attach to network
Wed Oct 7 09:51:32 2020 user.notice root: mbim bringup failed, retry in 15s
Wed Oct 7 09:51:47 2020 user.notice MBIM Connect: Stopping network

[gaddman]

Change the modem back to QMI mode. It may be an issue with MBIM mode on your network.

Code: Select all

AT+QCFG="usbnet",0

then

Code: Select all

AT+CFUN=1,1

Ok...did this. Looks like it's getting further. Now we may be at a provider issue?

Wed Oct 7 10:33:02 2020 user.notice usb-modeswitch: Found Modem1
Wed Oct 7 10:33:03 2020 user.notice usb-modeswitch: Connecting a QMI Modem
Wed Oct 7 10:33:03 2020 user.notice Create Connection: Start QMI Connection
Wed Oct 7 10:33:06 2020 kern.notice kernel: [ 75.324547] random: crng init done
Wed Oct 7 10:33:08 2020 user.notice Create Connection: QMI Comm Port : /dev/ttyUSB2
Wed Oct 7 10:33:08 2020 user.notice Create Connection: WDA-GET-DATA-FORMAT is "raw-ip"
Wed Oct 7 10:33:12 2020 user.notice Create Connection: Quectel Unsolicited Responses Disabled
Wed Oct 7 10:33:23 2020 user.notice Get Profile: Default Profile Used
Wed Oct 7 10:33:23 2020 user.notice Create Connection: Profile for Modem1 sets interface to WAN1
Wed Oct 7 10:33:23 2020 user.notice Create Connection: Modem1 is using WAN1
Wed Oct 7 10:33:25 2020 user.notice Create Connection: Pincode in script
Wed Oct 7 10:33:25 2020 user.notice Create Connection: Attempting to Connect
Wed Oct 7 10:33:31 2020 user.notice sms process: SMS Supported
Wed Oct 7 10:33:38 2020 user.notice QMI Connect: WDA-GET-DATA-FORMAT is "raw-ip"
Wed Oct 7 10:33:39 2020 user.notice QMI Connect: Waiting for network registration
Wed Oct 7 10:33:39 2020 user.notice sms process: Reread SMS Messages on Modem 1
Wed Oct 7 10:33:40 2020 user.notice QMI Connect: Starting network vzwinternet
Wed Oct 7 10:33:40 2020 user.notice QMI Connect: Connection returned : "Call failed"
Wed Oct 7 10:33:40 2020 user.notice QMI Connect: status is "disconnected"
Wed Oct 7 10:33:40 2020 user.notice QMI Connect: GET-CURRENT-SETTINGS is "Out of call"
Wed Oct 7 10:33:50 2020 user.notice Create Connection: Retry Connection
Wed Oct 7 10:34:08 2020 user.notice Create Connection: Pincode in script

[gaddman]

So I'm guessing we are getting to the same point with both methods (MBIM or QMI). The network is not accepting the connection either method. Should I pursue TTL settings or is it still premature for that?

[Didneywhorl]

Clear out your APNs again, delete your APN under ModemConnection Profile, and try AT+QCFG=”usbnet”,1 (ECM mode) for giggles. Then power cycle the router and then enter the APN into connection profile again then power cycle again.

[Didneywhorl]

Generally if the SIM phone number shows up, then the network is connecting with you. As the SIM card has no phone number saving capability on it. It is just your subscriber ID, the network then assigns the appropriate number to your device. That said, you ARE connecting to the network, then for some reason being booted.

Which APN does your device use again? And I’m assuming your entering that into the Modem profile APN spot on the router?

[gaddman]

Clear out your APNs again, delete your APN under ModemConnection Profile, and try AT+QCFG=”usbnet”,1 (ECM mode) for giggles. Then power cycle the router and then enter the APN into connection profile again then power cycle again.

Well, that did something!

The ECM mode command gave an error. Can you tell if the ECM mode took? The log still says QMI

From the log:
Wed Oct 7 14:54:28 2020 user.notice QMI Connect: status is "connected"

On the APN reset, the steps that we did not do before, was to delete it out of the connection profile, reboot, then re-enter it and reboot again. I'm wondering if that is what did the trick?

If so, should I go back to MBIM mode now if that is preferred?

Thanks so much. Great to finally see a connection!

[Didneywhorl]

Leave it! lol.

QMI vs MBIM is kind of a moot issue. Go with what works.

[gaddman]

Thanks for the help! Calling it a success for now.

[gaddman]

Just an update. I moved the router to a different location. Had to unplug it. When it came back up, it would not connect. I deleted the APN in the connection profile, power cycled it. Then re-entered the APN and power cycled again. Then it connected.

[ltefreedom]

If others land here with a WE826GO running a Quectel EP06-A modem trying to get this combination running for the first time, the first part of this thread did the trick for me. That would be the second post instructing how to clear the APNs then run in MBIM mode. After the modem hard reboot command I power cycled the router and it started working. Now to figure out how to turn on carrier aggregation as the speed is just as bad as the Verizon provided hotspot.

[Didneywhorl]

...
Now to figure out how to turn on carrier aggregation as the speed is just as bad as the Verizon provided hotspot.

Carrier aggregation is controlled by the carriers settings on your particular tower. The modem may be capable of 2CA on Bx +By bands, but your tower may not have it setup.

Sometimes your modem has to use one particular band as a base. For imaginary instance: Say your servingcell band (sometimes called an "anchor band" )is B2 and your modem can CA B2 with B5. It might only like to CA those two bands if your base servingcell band is B5 to CA with B2.

Make sense?