Michael Pfeifroth
f094afbed0
Commit7885dff933("modemmanager: skip virtual net devices in hotplug script") exited 25-modemmanager-net for every device under /devices/virtual/* to stop the per-device "event processed" line from spamming daemon.info on every boot and hotplug replay. That blanket exit also dropped the QMAP/QMI/MBIM multiplexing netdevices (qmapmux*, qmimux*, mbimmux*). Those live under /devices/virtual too, but they are real modem data ports and mm_report_event() deliberately keeps them (ModemManager then resolves their lower_* link back to the physical modem). Skipping them in the hotplug script broke multiplexed data connections. Rather than duplicating that qmapmux/qmimux/mbimmux allow-list in the hotplug script -- where it would drift out of sync with the copy in mm_report_event() -- keep the filter in one place. mm_report_event() now returns non-zero when it drops a virtual device, and the hotplug scripts only emit their "event processed" info log when the event was actually reported. The noisy log lines are gone for the dropped devices, and the mux ports still reach ModemManager. Fixes:7885dff933("modemmanager: skip virtual net devices in hotplug script") Signed-off-by: Michael Pfeifroth <micpf@westermo.com>
OpenWrt ModemManager
Description
Cellular modem control and connectivity
Optional libraries libmbim and libqmi are available. Your modem may require additional kernel modules and/or the usb-modeswitch package.
Usage
Once installed, you can configure the 2G/3G/4G modem connections directly in /etc/config/network as in the following example:
config interface 'broadband'
option device '/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.2/1-1.2.1'
option proto 'modemmanager'
option apn 'ac.vodafone.es'
option allowedauth 'pap chap'
option username 'vodafone'
option password 'vodafone'
option pincode '7423'
option iptype 'ipv4'
option plmn '214001'
option lowpower '1'
option signalrate '30'
option allow_roaming '1'
option force_connection '1'
option init_epsbearer '<none|default|custom>'
option timeout '120'
Only 'device' and 'proto' are mandatory options, the remaining ones are all optional.
The 'allowedauth' option allows limiting the list of authentication protocols. It is given as a space-separated list of values, including any of the following: 'pap', 'chap', 'mschap', 'mschapv2' or 'eap'. It will default to allowing all protocols.
The 'iptype' option supports any of these values: 'ipv4', 'ipv6' or 'ipv4v6'. It will default to 'ipv4' if not given.
The 'plmn' option allows to set the network operator MCCMNC.
The 'signalrate' option set's the signal refresh rate (in seconds) for the device. You can call signal info with command: mmcli -m 0 --signal-get
The 'timeout' option set's the command timeout (in seconds) for the long running 'mmcli' calls ('enable', 'simple-connect', 3gpp-register-in-operator' and '3gpp-set-initial-eps-bearer-settings') in the modemmanager protohandler. The default value is 120 seconds, if no value is configured.
The 'force_connection' option is designed to ensure that the modem automatically attempts to reconnect regardless of any errors encountered during the connection process.
If there is no Circuit switch network available, then an initial EPS bearer must be set, so this could be used during the network registration process in 4G and 5G network. For this resaon a new configuration option 'init_epsbearer' was added, which could have the following values.
- none: Do not set an initial EPS bearer (default)
- default: Use the configuration option 'apn', 'iptype', 'allowedauth', 'username' and 'password' for setting the initial EPS bearer. These are the same options as when establishing a connection.
- custom: This could be used to use diffrent options when establishing a connection. The options are prefixed with an 'init'. So we have the following options 'init_apn', 'init_iptype', 'init_allowedauth', 'init_username' and 'init_password' for setting the initial EPS bearer.