packages/net/modemmanager/files, branch master

modemmanager: skip virtual net devices in hotplug script

2026-08-03T11:03:31Z

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]: [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

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

modemmanager: allow empty initial EPS bearer APN

2025-12-09T14:45:10Z

This commit removes the non-empty APN requirement for initial EPS bearer. An empty APN value is valid and means that the modem will use a network provided APN offered by the operator. Signed-off-by: Simonas Tamošaitis

modemmanager: always reset the init_eps if not configured

2025-09-04T06:35:09Z

The initial EPS is stored on the modem side. When establishing a connection, it must therefore be deleted if no EPS has been configured. This is because the system does not know whether one was configured previously. Signed-off-by: Florian Eckert

modemmanager: add missing ppp ifname option value

2025-09-04T06:35:09Z

The pppd supports the option to configure the name of the network interface at startup using the ifname option. The pppd can overwrite the name of the network interface at startup using the 'ifname' configuration option. If this option is not specified, the new network interface is created according to the following scheme: ppp, e.g. ppp0, ppp1 and so on. This can therefore change with every start if the number has been already assigned to another ppp connection. In order to always get the same interface name with the modemmanger proto via ppp, it is created according to the new scheme by setting the 'ifname': ppp-, e.g. ppp-wwan. Signed-off-by: Florian Eckert

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: add sourcefilter option support

2025-05-28T06:16:27Z

This make source based IPv6 routing option available for modemmanager when using modem SLAAC. Signed-off-by: Ryan Press

modemmanager: add missing any option to allowedmode

2025-04-10T07:33:58Z

The 'mmcli' also understands the option 'any'. Signed-off-by: Florian Eckert

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