packages/net/modemmanager/files/usr, branch master

modemmanager: suppress hotplug noise without breaking QMAP/QMI/MBIM mux

2026-09-22T06:37:11Z

Commit 7885dff933e7 ("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: 7885dff933e7 ("modemmanager: skip virtual net devices in hotplug script") Signed-off-by: Michael Pfeifroth

modemmanager: skip live report when the service isn't up yet

2026-08-03T11:03:31Z

At boot procd replays every previously-seen uevent before /etc/init.d/modemmanager starts. Each replay walks the hotplug.d/ tree, which calls mm_report_event() in modemmanager.common. That helper does two independent things: 1) appends the event to ${MODEMMANAGER_EVENTS_CACHE}, and 2) runs 'mmcli --report-kernel-event=...' to notify a live MM. Step 1 is what matters for boot; step 2 exists so events fired after MM is running get reported without waiting for the next cache replay. The cache path is intentional: ModemManager-wrapper starts MM, then mm_report_events_from_cache() polls 'mmcli -L' until the bus is available and replays every cached event. At boot the modemmanager service instance hasn't been spawned by procd yet, so step 2 always fails with: daemon.err ModemManager[NNN]: hotplug: Couldn't report kernel event: error: couldn't get bus: Could not connect: No such file or directory That's one daemon.err line per hotplug script per port, per boot. On a dual-modem board that's a dozen spurious errors before the service even starts. Nothing is lost -- the wrapper's cache replay picks them all up seconds later -- but the log noise makes real ModemManager errors harder to spot. Guard the live call with a cheap pidfile-based liveness check. The pidfile is procd's, so it proves the service instance has been spawned, not that MM is already reachable on the bus; the brief wrapper-startup window (procd spawns the wrapper -> wrapper execs MM -> MM reaches the bus) is not covered. In practice no fresh uevents fire in that window on the boards this was tested on, and events that do arrive there are still cached. If the service hasn't been spawned yet, the event is silently cached and the wrapper handles it. If it has, behavior is unchanged. Signed-off-by: Michael Pfeifroth

modemmanager: change to configuration option disable_modem

2025-07-08T05:55:17Z

This commit sets default of `disable_modem` to 1 and disconnects modem. If set otherwise it keeps the modem connected. Signed-off-by: Christian Korber

modemmanager: fix pending mmcli calls for ModemManager-monitor script

2025-04-01T08:08:27Z

If the ModemManager is stopped via '/etc/init.d/modemmanager', mmcli calls always remain in the process list. This is because the ModemManager-monitor call is not terminated properly, as the kill signals are not handled correctly in the startup script for mmcli. To fix this, the signal handling is refactored. Signed-off-by: Florian Eckert

modemmanager: add missing mmcli timeout option during ubus call

2025-04-01T08:08:27Z

The default 'timeout' value is 30 seconds when calling an mmcli action. That is too long. For this reason, the mmcli 'timeout' option is specified for calls and the value is set to 10 seconds. Signed-off-by: Florian Eckert

modemmanager: add config optional netifd integration

2025-02-26T09:03:30Z

This change introduces an optional configuration of the netifd integration in the ModemManager package. When disabled, it removes the NETIFD dependency and other unwanted components from the root filesystem during the build phase. Additionally, in the modemmanager.common the netifd-proto.sh inclusion line can be savely removed as there is no usage of it in its functions. Signed-off-by: Gilles Lenaerts

modemmanager: do not disable modem on reconnect

2025-02-12T15:52:16Z

If the modem loses the connection, an attempt is made to re-establish the connection via the report-down script. Until now, the modem was disabled when the modem processed the teardown of the modemmanager protohandler. The immediate up events of netifd renables the modem right away. This takes time, which is not necessary. This commit changes the behavior so that the modem is not disabled when the modemmanager is disconnected via the report-down script. Signed-off-by: Florian Eckert

modemmanager: extend log message with count on boot

2024-10-17T16:29:16Z

This makes debugging at system startup easier and shows how long we are waiting for the ModemManager to start. Signed-off-by: Florian Eckert

modemmanager: add missing ubus status backend via mmcli

2024-07-10T10:26:51Z

The 'modemmanager' uses the 'dbus'. Status information can be retrieved with the 'mmcli' command, this can also be output in json format. This commit adds a new 'ubus' backend with which this information can be easily accessed via ubus. * ubus call modemmanager info * ubus call modemmanager dump Signed-off-by: Florian Eckert

Merge pull request #23590 from TDT-AG/pr/20240305-modemmanager

2024-03-12T10:59:11Z

modemmanager: reconnect interface if the modemmanager detects a disconnect