summaryrefslogtreecommitdiff
path: root/python
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2026-09-24 15:28:39 +0000
committerChristian Breunig <christian@breunig.cc>2026-09-24 15:28:39 +0000
commit9c88884a67c01b4e5d74872abee41820a8f65331 (patch)
tree56bbedac930fb0300c9f6267807f5faa5af1315c /python
parent112fb62b8b15653c0a26e0de56f326cd2d67da9b (diff)
downloadvyos-1x-9c88884a67c01b4e5d74872abee41820a8f65331.tar.gz
vyos-1x-9c88884a67c01b4e5d74872abee41820a8f65331.zip
wwan: T9350: query ModemManager instead of the QMI control port
show_wwan.py drove qmicli against /dev/cdc-wdmN, which assumes the modem exposes a QMI control port. An MBIM modem does not, so every subcommand of "show interfaces wwan wwanN" failed on one - after waiting out a five second transaction timeout, twice over for "signal": $ show interfaces wwan wwan0 signal Command not supported by Modem (10.6s) $ qmicli --device=/dev/cdc-wdm0 --device-open-proxy --nas-get-signal-info error: couldn't create client for the 'nas' service: CID allocation failed in the CTL client: Transaction timed out ports: cdc-wdm0 (mbim), ttyUSB0 (at), wwan0 (net) ModemManager has already probed the modem and speaks whichever protocol it exposes - QMI, MBIM or plain AT. It is a hard dependency of "interfaces wwan" anyway, as conf_mode cannot dial without it, and it answers from its own cache over D-Bus without touching the device: $ show interfaces wwan wwan0 signal Access technology: lte (0.2s) Signal quality: 58% Operator: Telekom.de Registration: home Packet service: attached State: connected
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions