cr08
commented
1 month ago Here's the excerpts from the logs that I'm able to find useful info from:
com"
OK
AT+CGACT=1,1
+CGEV: ME PDN ACT 1
OK
AT+CGPADDR=1
+CGPADDR: 1,"21.188.8.83","0.0.0.0.0.0.0.0.172.57.56.247.79.57.199.27"
OK
AT+CGPADDR=1
+CGPADDR: 1,"21.188.8.83","0.0.0.0.0.0.0.0.172.57.56.247.79.57.199.27"
OK
AT+GTDNS=1
+GTDNS: 1,"10.177.0.34","10.177.0.210"
+GTDNS: 1,"253.0.151.106.0.0.0.0.0.0.0.0.0.0.0.9","253.0.151.106.0.0.0.0.0.0.0.0.0.0.0.16"
OK
AT+CGACT=0,1
+CGEV: ME PDN DEACT 1
OKThu May 30 23:20:43 2024 daemon.notice netifd: 5G (9112): Modem /dev/ttyUSB8 disconnected
Thu May 30 23:20:43 2024 daemon.notice netifd: Interface '5G' is now down
Thu May 30 23:20:43 2024 daemon.notice netifd: Interface '5G' is setting up now
Thu May 30 23:20:43 2024 daemon.notice netifd: 5G (9121): Setup fm350 interface 5G with port /dev/ttyUSB8
Thu May 30 23:20:43 2024 daemon.notice netifd: 5G (9121): Found path /sys/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.6/ttyUSB8
Thu May 30 23:20:43 2024 daemon.notice netifd: 5G (9121): Found interface eth1
Thu May 30 23:20:43 2024 daemon.notice netifd: 5G (9121): Setting up eth1
Thu May 30 23:20:56 2024 daemon.notice netifd: 5G (9288): Modem /dev/ttyUSB8 disconnected
Thu May 30 23:20:56 2024 daemon.notice netifd: Interface '5G' is now down
Thu May 30 23:20:56 2024 daemon.notice netifd: Interface '5G' is setting up now
Thu May 30 23:20:56 2024 daemon.notice netifd: 5G (9301): Setup fm350 interface 5G with port /dev/ttyUSB8
Thu May 30 23:20:56 2024 daemon.notice netifd: 5G (9301): Found path /sys/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.6/ttyUSB8
Thu May 30 23:20:56 2024 daemon.notice netifd: 5G (9301): Found interface eth1
Thu May 30 23:20:56 2024 daemon.notice netifd: 5G (9301): Setting up eth1
Thu May 30 23:21:09 2024 daemon.notice netifd: 5G (9464): Modem /dev/ttyUSB8 disconnected
Thu May 30 23:21:09 2024 daemon.notice netifd: Interface '5G' is now down
Thu May 30 23:21:09 2024 daemon.notice netifd: Interface '5G' is setting up now
Thu May 30 23:21:09 2024 daemon.notice netifd: 5G (9472): Setup fm350 interface 5G with port /dev/ttyUSB8
Thu May 30 23:21:09 2024 daemon.notice netifd: 5G (9472): Found path /sys/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.6/ttyUSB8
Thu May 30 23:21:09 2024 daemon.notice netifd: 5G (9472): Found interface eth1
Thu May 30 23:21:09 2024 daemon.notice netifd: 5G (9472): Setting up eth1
Preface: I don't have logs at the moment but I'll get and post those later this afternoon. This happened after an impromptu test late last night and didn't save anything I had seen.
This is on an x86-64 box running a largely stock OpenWRT 25.05.3. Just a few basic packages added on such as drivers for some USB ethernet dongles, Luci, and the necessary packages from this repo.
First test with just this 5G modem installed (I have a few Quectel EC25-AF cards I intend to use in addition which will come up later) on its own it seemed to be fine. It grabbed ttyUSB ports starting at 0. Pointed the interface at ttyUSB4 and after a bit of waiting it connects and works perfect.
I've stepped further in my setup and added one of my Quectel EC25-AF 4G LTE cards in using QMI tools/drivers. Both cards are connected via USB internally (separate host buses/power supplies. Power is not an issue.) and now both take up their own set of serial ports. The Quectel card is taking first dibs on boot so sits on 0-4 and the f350 on 5-x. Found the correct AT port I think it was on ttyUSB8. Confirmed with minicom and proper responses on key commands. I should note that the RNDIS port is on eth1 and eth0 is consistently taken up by a USB ethernet dongle. But the logs I do see seem to pick this up with no issue.
However now the card won't connect in this setup. Doing some digging and eventually figuring out I can have minicom connected while the connection is attempted and seeing the output, the summary of what I'm seeing is it seems like it connects fine but throws a CONFIGURE_FAILED error then it sends a disconnect command and restarts the process. Here's kinda the cliffnotes/paraphrasing of what I saw on the serial port:
The CONFIGURE_FAILED I only briefly see in the Luci interface page when I'm paying close attention. I haven't seen it anywhere else.
Apologies for putting this out without any solid logs or concrete info. It's been nagging my brain this morning while at work and wanted to get something put down. I'll post more detailed info this afternoon (EST time). But if there's any good tips on this, maybe someone else has run into this before or has pointers on how I can maybe get more verbose logging to get an idea what it is tripping up on?
Thanks!