packages/net/modemmanager/Makefile, branch master

modemmanager: rework initial EPS bearer modes

2026-10-05T09:12:07Z

Commit 246506690f2d ("modemmanager: always reset the init_eps if not configured") changed the behaviour for an unset 'init_epsbearer' from leaving the modem untouched to clearing the initial EPS bearer on every setup. This is a regression for users upgrading from 24.10: - Modems without support for setting the LTE attach configuration (e.g. Sierra Wireless EM7430) fail the setup with MM_INIT_EPS_BEARER_SET_FAILED and never come up. - Attach settings preloaded by the carrier firmware are wiped. The same commit also removed the explicit 'none' case, so 'none' now silently skips the initial EPS bearer setup, while it cleared it in 24.10. Neither matches the documentation. Make all modes explicit, each naming where the initial EPS bearer settings come from: - modem: leave the settings stored on the modem unchanged (default) - network: set an empty initial EPS bearer, the network assigns the APN; replaces the implicit clear, e.g. after a SIM swap - connection: use the connection options (apn, iptype, ...) - custom: use the init_* options 'none' and 'default' are kept as deprecated aliases for 'modem' and 'connection'. 'none' maps to 'modem' as documented in the README and as it behaves since 246506690f2d, although an explicit 'none' cleared the initial EPS bearer in 24.10; use 'network' for that. Unknown values fall back to 'modem'. The README now documents the modes and how to clear stale settings manually. Fixes: https://github.com/openwrt/packages/issues/30299 Signed-off-by: Michael Pfeifroth

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: fix custom initial EPS bearer username

2026-09-17T14:54:35Z

The custom initial EPS bearer code uses init_username, which agrees with the documented UCI option. However, the option was registered and read as init_user, so init_username was discarded before the custom EPS bearer settings were passed to mmcli. Register and read the option consistently as init_username. Signed-off-by: Michael Pfeifroth

modemmanager: bump PKG_RELEASE

2026-09-07T10:46:19Z

Update PKG_RELEASE by one. Signed-off-by: Florian Eckert

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: bump PKG_RELEASE

2026-07-15T08:16:54Z

Bump PKG_RELEASE number. This is due because of earlier changes. Signed-off-by: Christian Korber

modemmanager: add configurable plugins

2026-07-15T08:16:54Z

This adds the feature to choose which plugins to include or not. Additionally, the needed shared plugins are added automatically. Signed-off-by: Christian Korber

modemmanager: make building builtin options optional

2026-07-15T08:16:54Z

This commit enables to choose whether to compile the plugins into the binary or not. If not included, it moves the plugins to `/usr/lib/ModemManager/`. Signed-off-by: Christian Korber

modemmanager: fix dependency and ci

2026-07-05T10:24:51Z

lua-cjson depends on liblua, so add missing lua dependency. modemmanager-rpcd has no version, so add a simple test, and skip version check. Signed-off-by: Etienne Champetier

modemmanager: fix netifd proto sim path

2026-02-10T12:59:28Z

Use specific SIM path instead of 'any' when unlocking with PIN code. This fixes PIN unlock issues on devices with multiple modems where 'any' could select the wrong modem. Bump modemmanager PKG_RELEASE Signed-off-by: micpf