So, afer some days (probably weeks) a new build of the 4.2 snapshot appeared for download.
I upgraded from 0212 to 0323 with “keep settings”.
Unfortunately, I am now unable to connect to the internet (SIM is recognised but won’t connect).
I tried fiddling with the settings but to no avail.
I have now downgraded back to 0212 and all is fine.
Hope this helps the devs.
Happi
Could you tell me what configurations you previously made?
I had a Wireguard client enabled and NextDNS over TLS.
But I disabled both of these and did a reboot and the modem still wouldnt connect.
I will do a clean install and see if that works.
Edit: Had another fiddle, including a clean install…but no luck.
Can you give some details of the modem, carrier and send the log?
It could be solved easily with these info.
Here’s some of the log.
All I did was:
load firmware, changed password (so I could login to GUI), synched time with browser, manually entered APN and password.
Modem: EP06 , Carrier: EE UK, APN “everywhere” (set manually as auto-setup doesn’t work on any 4.x firmware version.
Fri Mar 24 15:47:58 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CGDCONT=1,“IP”,“everywhere”
data_leangth=0 data=
OK
Fri Mar 24 15:47:58 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+QICSGP=1,1,“everywhere”,“eesecure”,“secure”,1
data_leangth=0 data=
OK
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2_4 (11906): udhcpc: received SIGTERM
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2_4 (11906): udhcpc: entering released state
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:488] call_end_reason is 1018
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:488] call_end_reason_type is 6
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:489] call_end_reason_verbose is 33
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:552] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:552] call_end_reason is 1018
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:552] call_end_reason_type is 6
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:553] call_end_reason_verbose is 33
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:46:20:553] try to requestSetupDataCall 60 second later
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:712] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:712] call_end_reason is 1018
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:712] call_end_reason_type is 6
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:713] call_end_reason_verbose is 33
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:776] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:776] call_end_reason is 1018
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:776] call_end_reason_type is 6
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:777] call_end_reason_verbose is 33
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:20:777] try to requestSetupDataCall 60 second later
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:59:562] QmiWwanThread exit
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (11833): [03-24_15:47:59:563] qmi_main exit
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Interface ‘modem_1_1_2’ is now down
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Interface ‘modem_1_1_2’ is setting up now
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2_4 (11906): Command failed: ubus call network.interface notify_proto { “action”: 0, “link-up”: false, “keep”: false, “interface”: “modem_1_1_2_4” } (Permission denied)
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ is now down
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ is disabled
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Network alias ‘’ link is down
Fri Mar 24 15:47:59 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ has link connectivity loss
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (22991): sh: 0: unknown operand
Fri Mar 24 15:47:59 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=‘AT+QNWPREFCFG=“roam_pref”,255’
data_leangth=0 data=
ERROR
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (22991):
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (22991):
Fri Mar 24 15:47:59 2023 daemon.notice netifd: modem_1_1_2 (22991): ERROR
Fri Mar 24 15:48:00 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=ATI
data_leangth=0 data=
Quectel
EP06
Revision: EP06ELAR03A08M4G
OK
Fri Mar 24 15:48:00 2023 daemon.notice netifd: modem_1_1_2 (22991): Failed to parse message data
Fri Mar 24 15:48:00 2023 daemon.notice netifd: modem_1_1_2 (22991): sh: 0: unknown operand
Fri Mar 24 15:48:00 2023 daemon.notice netifd: modem_1_1_2 (22991): sh: 1: unknown operand
Fri Mar 24 15:48:01 2023 user.notice mwan3[22926]: Execute ifdown event on interface modem_1_1_2 (unknown)
Fri Mar 24 15:48:01 2023 user.info mwan3track[12555]: Detect ifdown event on interface modem_1_1_2 (wwan0)
Fri Mar 24 15:48:01 2023 user.notice mwan3track[12555]: Interface modem_1_1_2 (wwan0) is offline
Fri Mar 24 15:48:01 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:781] QConnectManager_Linux_V1.6.3.1
Fri Mar 24 15:48:01 2023 daemon.notice netifd: Interface ‘modem_1_1_2’ is now up
Fri Mar 24 15:48:01 2023 daemon.notice netifd: Network device ‘wwan0’ link is up
Fri Mar 24 15:48:01 2023 daemon.notice netifd: Network alias ‘wwan0’ link is up
Fri Mar 24 15:48:02 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ is enabled
Fri Mar 24 15:48:02 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ has link connectivity
Fri Mar 24 15:48:02 2023 daemon.notice netifd: Interface ‘modem_1_1_2_4’ is setting up now
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2_4 (23186): udhcpc: started, v1.35.0
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:836] Find /sys/bus/usb/devices/1-1.2 idVendor=0x2c7c idProduct=0x306, bus=0x001, dev=0x004
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:862] Auto find qmichannel = /dev/cdc-wdm0
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:863] Auto find usbnet_adapter = wwan0
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:863] netcard driver = qmi_wwan, driver version = 5.10.146
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:01:865] Modem works in QMI mode
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:029] cdc_wdm_fd = 7
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:216] Get clientWDS = 20
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:280] Get clientDMS = 1
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:344] Get clientNAS = 3
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:408] Get clientUIM = 3
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:472] Get clientWDA = 1
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:536] requestBaseBandVersion EP06ELAR03A08M4G
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:792] requestGetSIMStatus SIMStatus: SIM_READY
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:856] requestGetProfile[1] everywhere/eesecure/secure/1/IPV4
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:856] requestSetProfile[1] everywhere/eesecure/secure/1/IPV4
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:857] no need to set skip the rest
Fri Mar 24 15:48:02 2023 daemon.notice netifd: modem_1_1_2 (23121): [03-24_15:48:02:924] requestRegistrationState2 MCC: 234, MNC: 30, PS: Attached, DataCap: LTE
Fri Mar 24 15:48:03 2023 daemon.notice netifd: modem_1_1_2_4 (23186): udhcpc: broadcasting discover
Fri Mar 24 15:48:06 2023 daemon.notice netifd: modem_1_1_2_4 (23186): udhcpc: broadcasting discover
Fri Mar 24 15:48:09 2023 daemon.notice netifd: modem_1_1_2_4 (23186): udhcpc: broadcasting discover
Fri Mar 24 15:48:09 2023 user.notice firewall: Reloading firewall due to ifdown of modem_1_1_2 ()
Fri Mar 24 15:48:14 2023 user.notice mwan3[23780]: Execute ifup event on interface modem_1_1_2 (wwan0)
Fri Mar 24 15:48:15 2023 user.notice mwan3[23780]: Starting tracker on interface modem_1_1_2 (wwan0)
Fri Mar 24 15:48:18 2023 user.info mwan3rtmon[12645]: Detect rtchange event.
Fri Mar 24 15:48:21 2023 user.notice firewall: Reloading firewall due to ifup of modem_1_1_2 (wwan0)
Fri Mar 24 15:48:56 2023 user.notice mwan3[24979]: Execute ifdown event on interface modem_1_1_2 (wwan0)
Fri Mar 24 15:48:58 2023 user.notice firewall: Reloading firewall due to ifdown of modem_1_1_2 (wwan0)
Fri Mar 24 15:49:02 2023 user.info mwan3track[24013]: Detect ifdown event on interface modem_1_1_2 (wwan0)
Fri Mar 24 15:49:07 2023 user.notice mwan3track[24013]: Interface modem_1_1_2 (wwan0) is offline
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CPMS=“ME”,“ME”,“ME”
data_leangth=0 data=
+CPMS: 0,23,0,23,0,23
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CGPADDR
data_leangth=0 data=
+CGPADDR: 1,“10.180.88.167”
+CGPADDR: 2,“”
+CGPADDR: 3,“”
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CPIN?
data_leangth=0 data=
+CPIN: READY
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+ICCID
data_leangth=0 data=
+ICCID: xxxxxxxxx
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+QCCID
data_leangth=0 data=
+QCCID: xxxxxxxxx
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CIMI
data_leangth=0 data=
xxxxxxxxx
OK
Fri Mar 24 15:50:44 2023 daemon.err modem_AT: (modem_AT.c:314) cmd=AT+CNUM
data_leangth=0 data=
+CNUM: “Own Number”,“xxxxxxxxxxxx”,129
:::::::::::::working
Fri Mar 24 16:33:18 2023 daemon.err usbmuxd[5044]: [16:33:18.424][3] usbmuxd v1.1.1 starting up
Fri Mar 24 16:33:18 2023 daemon.err usbmuxd[5044]: [16:33:18.450][3] Using libusb 1.0.24
Fri Mar 24 16:33:18 2023 daemon.err usbmuxd[5044]: [16:33:18.479][3] Initialization complete
Fri Mar 24 16:33:18 2023 daemon.err usbmuxd[5044]: [16:33:18.480][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with “–exit” to trigger.
Fri Mar 24 16:33:19 2023 user.notice firewall: Reloading firewall due to ifup of guest (br-guest)
Fri Mar 24 16:33:30 2023 user.notice mwan3[5591]: Execute ifup event on interface lan (br-lan)
Fri Mar 24 16:33:30 2023 user.notice mwan3[5591]: Starting tracker on interface lan (br-lan)
Fri Mar 24 16:33:33 2023 user.info mwan3rtmon[4902]: Detect rtchange event.
Fri Mar 24 16:33:35 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Fri Mar 24 16:33:39 2023 user.notice mwan3[6049]: Execute ifup event on interface loopback (lo)
Fri Mar 24 16:33:39 2023 user.notice mwan3[6049]: Starting tracker on interface loopback (lo)
Fri Mar 24 16:33:42 2023 user.info mwan3rtmon[4902]: Detect rtchange event.
More testing (build 4.2.1 0327) …I managed to connect by changing the protocol to “3G” (from QMI).
This auto changed the port from cdc-wdm0 > USB3 and added an extra option “service” > LTE/UMTS/GPRS.
Hope this helps to debug.
Happi
PS. probably should have mentioned, I am using the V2 version of the Spitz
Another update:
Loaded 4.2.2 beta1 (this appears to be an upgrade from the snapshot 4.2.1 even though the build number is lower (323 vs. 330) and build date earlier.
I can again connect using the QMI protocol but cannot get any internet. Troubleshooting this, I discoverd the problem appears to be something to do with the MAC address, as clicking the “random” option (ie, changing the MAC) gave instant internet. However, on rebooting the internet is once again blocked (until again resetting the MAC).
On MVNO Lebara (Vodafone Network) in the UK.
Managed to connect, after several changes in settings, using QCM. Reset to Factory and tried again, connected first time. I am on a 5G mast.
(X750V2)
V4.2.2 beta1 2023-03-23 20:03:03(UTC+08:00)
Can’t seem to get visibility of my 2.4G Wifi connection after I have changed the SSID and Password.
(Wireless not associated - can’t fix through Luci either)
Disappointed to see that you have restricted the IP address of the LAN to 192.168. I use IP addresses in the 10.0.0.0 and 172.0.0.0 ranges (for various reasons) which I will no longer be able to access. These are IANA private IP addresses.
EDIT: Changed through Luci.
It was on Auto, changed to Channel 2, now it shows up and I am connected OK. Thank you.
Any reason Auto is not working?
Missed that button completely!! Ooops!
Could you please check the Wi-Fi status page to see what channel it falls into when set to “auto”? You can find this information at the following URL: 192.168.8.1/cgi-bin/luci/admin/network/wireless.
When I change back to Auto, the 2.4Ghz Module is disabled.
EDIT: It is enabled in the GL.iNet setup page.
I just synchronized the information with my colleague, and it is a known bug, which has been fixed in the latest snapshot.
Thank you! Glad it was known!
Another month passes and finally a new snapshot.
Unofrtuantely, no improvement from the last build (0323) or from the beta release - it still fails to connect to my mobile network using the saved settings (QMI). The only thing that works is 3G (QCM aslo fails). So back to the last build that works for me - 4.2.0-0212.
V4.2.2 Snapshot 2023-04-18 06:45:10 (UTC+01:00)
Connected to Mobile Network ---- eventually. Made several attempts (>15) and it finally connected with the ‘default’ settings for the Manual setup (QCM/wdm0). I had to change APN and add Username and Password, but that was expected. Modem (Soft) and Router reset several times during this process.
@alzhao/@hansome - Do you have any idea when File sharing will be available in the Firmware?
Wi-Fi 2.4G available on Channel change without having to ‘tweak’.
Sorry, it has not been planned yet. As the storage is only 16MB for Spitz, the file sharing package is relatively large in size.
Up to build 0504 in the snapshot now and this connection issue still hasn’t been addressed.
Back to build 0212 for me…again!
