Flint 2, USB modem not recognized

Technical Support for Routers
1

I've had my Flint 2 for a couple of weeks, works great, fast, ...
I just purchased a Beryl MT-3000 so far it seems fast and everything works.
I have a ZTE MF833V that I used years ago. Tried it in the Flint first. It doesn't recognize the cellular modem. Any idea if this should work? I'll try it in the Beryl tomorrow to see if it's any different. The log file indicates that it detects it, then gives a repeated warning message.

Log file shows this:

Fri Jun 21 16:49:57 2024 kern.info kernel: [ 788.584056] usb 1-2: new high-speed USB device number 8 using xhci-mtk
Fri Jun 21 16:49:57 2024 kern.info kernel: [ 788.750250] usb-storage 1-2:1.0: USB Mass Storage device detected
Fri Jun 21 16:49:57 2024 kern.info kernel: [ 788.756559] usb-storage 1-2:1.0: Quirks match for vid 19d2 pid 1225: 1
Fri Jun 21 16:49:57 2024 kern.info kernel: [ 788.763315] scsi host0: usb-storage 1-2:1.0
Fri Jun 21 16:50:00 2024 cron.err crond[8317]: USER root pid 25538 cmd . /lib/functions/modem.sh;check_ip
Fri Jun 21 16:50:00 2024 cron.err crond[8317]: USER root pid 25539 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Fri Jun 21 16:50:00 2024 cron.err crond[8317]: USER root pid 25540 cmd . /lib/functions/modem.sh;modem_net_monitor
Fri Jun 21 16:50:02 2024 kern.info kernel: [ 793.838197] usb 1-2: USB disconnect, device number 8
Fri Jun 21 16:50:03 2024 kern.info kernel: [ 794.232023] usb 1-2: new high-speed USB device number 9 using xhci-mtk
Fri Jun 21 16:50:03 2024 kern.info kernel: [ 794.401643] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-11200000.xhci-2, ZTE CDC Ethernet Device, 3a:24:d0:ba:1c:ad
Fri Jun 21 16:50:03 2024 kern.info kernel: [ 794.416235] usb-storage 1-2:1.2: USB Mass Storage device detected
Fri Jun 21 16:50:03 2024 kern.info kernel: [ 794.422529] scsi host0: usb-storage 1-2:1.2
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:03 2024 user.warn : skip line without '=' Default
Fri Jun 21 16:50:03 2024 user.warn : skip line without '='
Fri Jun 21 16:50:04 2024 kern.notice kernel: [ 795.454174] scsi 0:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
Fri Jun 21 16:50:04 2024 kern.notice kernel: [ 795.463126] scsi 0:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Fri Jun 21 16:50:04 2024 kern.warn kernel: [ 795.472760] sd 0:0:0:1: Power-on or device reset occurred
Fri Jun 21 16:50:04 2024 kern.notice kernel: [ 795.482447] sd 0:0:0:1: [sda] Attached SCSI removable disk
Fri Jun 21 16:51:00 2024 cron.err crond[8317]: USER root pid 27238 cmd . /lib/functions/modem.sh;check_ip
Fri Jun 21 16:51:00 2024 cron.err crond[8317]: USER root pid 27239 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Fri Jun 21 16:51:28 2024 authpriv.info dropbear[14123]: Exit (root) from <192.168.1.189:53586>: Exited normally
Fri Jun 21 16:51:49 2024 kern.info kernel: [ 900.055344] usb 1-2: USB disconnect, device number 9
Fri Jun 21 16:51:49 2024 kern.info kernel: [ 900.060397] cdc_ether 1-2:1.0 usb0: unregister 'cdc_ether' usb-11200000.xhci-2, ZTE CDC Ethernet Device
Fri Jun 21 16:51:49 2024 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Jun 21 16:51:50 2024 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Jun 21 16:52:00 2024 cron.err crond[8317]: USER root pid 28764 cmd . /lib/functions/modem.sh;check_ip
Fri Jun 21 16:52:00 2024 cron.err crond[8317]: USER root pid 28765 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Fri Jun 21 16:52:00 2024 cron.err crond[8317]: USER root pid 28766 cmd . /lib/functions/modem.sh;modem_net_monitor
Fri Jun 21 16:52:13 2024 kern.err kernel: [ 924.123420] WiFi@C15L1,RTMPDeletePMKIDCache() 1311: IF(2), del PMKID CacheIdx=5
Fri Jun 21 16:52:58 2024 kern.debug kernel: [ 969.509575] entrytb_aid_aquire(): found non-occupied aid:17, allocated from:4
Fri Jun 21 16:52:58 2024 kern.warn kernel: [ 969.516723] 7986@C13L2,MacTableInsertEntry() 1577: New Sta:c0:b8:83:f0:20:71
Fri Jun 21 16:52:58 2024 kern.notice kernel: [ 969.525153] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714: Recv Assoc from STA - c0:b8:83:f0:20:71
Fri Jun 21 16:52:58 2024 kern.err kernel: [ 969.534337] 7986@C08L1,APBuildAssociation() 745: invalid status code(53) !!!
Fri Jun 21 16:52:58 2024 kern.notice kernel: [ 969.541395] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ReASSOC Send ReASSOC response (Status=53)...
F

2

hello
I tested a ZTE MF833U1
It is recognized as tethering, not modem

image
image1262×388 15 KB

1 Like
3

I didn't see it show up as tethering on my Flint 2, but it does on my Beryl MT-3000. But in either case that doesn't seem right. There's no ability to configure or get status.

4

Never mind, I found I need to connect to the web interface.

5

Doesn't it work on the MT3000?
Do you have Internet access?
Let me test Flint2

6

It’s working on the MT3000. I was just surprised to see it as tethering.

I just loaded 4.6.0 and verified that my USB modem works and the TTL setting does what it is supposed to do.

I might have seen minor issues with mwan switching between repeater and modem, but that would be a different issue. It’s also hard to know if it’s real because I’m trying to run the MT3000 in repeater mode in a marina. Wi-Fi in a marina is always challenging.

So I’m convinced there is no problem now.