Files
packages/net/modemmanager
Michael Pfeifroth 7885dff933 modemmanager: skip virtual net devices in hotplug script
Every net uevent - eth ports, USB hubs, bridges, taps, SQM IFB,
GRE tunnels, veth, tun/tap - is handed to mmcli via
25-modemmanager-net's mm_report_event call, so ModemManager logs a
'not supported by any plugin' notice per device on every boot and
hotplug replay:

  ModemManager[15132]: <msg> [base-manager] couldn't check support
    for device '.../fsl-ehci.0/usb1/1-1/1-1.1':
    not supported by any plugin

mm_report_event() already discards virtual devices internally, but
only after mm_log "info" has written a "hotplug: add network
interface XXX: event processed" line to daemon.info for every one
of them.

Mirror the same guard in the hotplug script by exiting early when
DEVPATH points under /devices/virtual/*, which covers SQM IFB, GRE,
bridges, veth, tun/tap.  This never rejects a physical modem port
(kernel wwan, MHI, USB CDC/RNDIS/QMI/MBIM are all under real bus
subtrees).

Signed-off-by: Michael Pfeifroth <micpf@westermo.com>
2026-08-03 13:03:31 +02:00
..
…
…

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>'

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 '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.