Modemmanager issue

Ppokharel · April 29, 2023, 1:56am

I have the following system and having some issue on installing modem manager

DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r22657-1e8b318ebe'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r22657-1e8b318ebe'
DISTRIB_TAINTS=''
Linux version 5.15.108 (builder@buildhost) (aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 12.2.0 r22657-1e8b318ebe) 12.2.0, GNU ld (GNU Binutils) 2.40.0) #0 SMP


I tried to install modemanager and getting the following error can someone help me on this.

> nstalling modemmanager (1.20.6-1) to root...
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages

/modemmanager_1.20.6-1_aarch64_cortex-a53.ipk
> Collected errors:
>  * opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/modemmanager_1.20.6-1_aarch64_cortex-a53.ipk, wget returned 8.
>  * opkg_install_pkg: Failed to download modemmanager. Perhaps you need to run 'opkg update'?
>  * opkg_install_cmd: Cannot install package modemmanager

efahl · April 29, 2023, 3:17am

You're updating to today's snapshot? I haven't looked at the buildbots for your specific arch, but this is sometimes symptomatic of when packages for the build have not finished building. Wait a few hours, or maybe until tomorrow, then try again...

reinerotto · April 29, 2023, 6:06am

+1. I stopped using snapshots, because of multiple times having issues, because of ongoing development. Only to use stable versions.
BTW: I have large fleet of LTE-routers, without modemmanager. Do you really need it ?

Lynx · April 29, 2023, 6:34am

How do you manage automatic reconnection upon disconnection?

reinerotto · April 29, 2023, 7:04am

Programmatically, myself. mwan3-events help here, because usually (but not always) there is another internet connection (wan, wifi) available, too.

Lynx · April 29, 2023, 7:26am

Newer versions of modemmanager report disconnections to a so-called dispatcher script facility that brings the interface down, which supports adding custom commands such that you can bring the interface back up. But the OpenWrt devs are very slow to upgrade modemmanager in 22.03 such that the present version doesn't include the new so-called dispatcher scripts.

github.com/openwrt/packages

ModemManager: broken in 22.03 and netifd reconnect issue

opened 08:15PM - 03 Nov 22 UTC

lynxthecat

**Firstly**, ModemManager is broken in 22.03 because modem disconnect does not r…each through to netifd absent this patch from @aleksander0m: https://github.com/openwrt/packages/commit/bc754f31cfdb004eefa43038f8f0827922107fc6 In short, ModemManager sees the disconnect, but netifd does not and the output of e.g. 'ifstatus' or 'ip addr show dev' is wrong (reflecting the old connected state and not updated to reflect disconnection). See e.g. here: https://github.com/openwrt/openwrt/issues/8368#issuecomment-1299719052. So ModemManager in 22.03 needs to be updated to fix this. **Secondly**, even with the above patch in the ModemManager version on OpenWrt master, upon disconnection we see: ``` Wed Nov 2 20:38:54 2022 daemon.info [2716]: <info> [modem0] state changed (connected -> disconnecting) Wed Nov 2 20:38:54 2022 daemon.info [2716]: <info> [modem0] state changed (disconnecting -> registered) Wed Nov 2 20:38:54 2022 daemon.info [2716]: <info> [modem0/bearer3] connection #1 finished: duration 121s, tx: 258333 bytes, rx: 371928 bytes Wed Nov 2 20:38:54 2022 user.notice modemmanager: interface wan (network device wwan0) disconnected Wed Nov 2 20:38:54 2022 daemon.notice netifd: Interface 'wan' has lost the connection Wed Nov 2 20:38:54 2022 daemon.notice netifd: Network device 'wwan0' link is down Wed Nov 2 20:38:54 2022 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry ``` And so although now with the patched version of ModemManager netifd sees the disconnect, netifd does not actually reconnect. This is using /etc/config/network: ``` config interface 'wan' option proto 'modemmanager' option device '/sys/devices/platform/1e1c0000.xhci/usb2/2-1' option auth 'pap' option iptype 'ipv4v6' option apn 'xx option username 'yy' option password 'zz' ```

github.com/openwrt/packages

modemmanager: report network initiated disconnections to netifd

committed 04:39AM - 15 May 22 UTC

aleksander0m

+38 -0

The new connection dispatcher scripts support integrated in ModemManager 1.18.8 …allows us to provide a openwrt-specific dispatcher script used to report netifd that the underlying network connection is down. See also https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/775 Fixes https://github.com/openwrt/openwrt/issues/8368 Fixes https://github.com/openwrt/packages/issues/14096 Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>

So 22.03 users that need this must manually upgrade modemmanager or use alternative ways to reconnect on disconnection.

reinerotto · April 29, 2023, 8:08am

Using mwan3 as a 'vehicle' to detect disconnection, and to trigger re-connection via short script (probably modem specific, though) is much simpler compared to Modemmanger plus netifd plus ...

Lynx · April 29, 2023, 1:18pm

Hmm. Using mwan3 for this purpose also seems a little Heath Robinson, especially for those like myself without multiple wan connections.

At least modemmanager is designed to, well, manage modems, and netifd is an integral part of OpenWrt. It's just the loop hasn't been properly closed yet.

It seems modem support in OpenWrt needs a little attention.

Ppokharel · May 1, 2023, 1:07pm

still having the same issue