Hi there,
I am testing a device Management Framework named balenaOS on a couple of Edge
devices. Networking is managed by ModemManager/NetworkManager. After a couple
of hours my device (Raspberry CM3 based) goes offline, having no Internet
Connection via LTE any more. When I connect to the device via LAN, I can see
that the modem has disappeared:
root@9d52738:~# mmcli -L
No modems were found
root@9d52738:~# nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
supervisor0 bridge connected supervisor0
balena0 bridge unmanaged --
br-4a4858757201 bridge unmanaged --
resin-dns bridge unmanaged --
veth607d783 ethernet unmanaged --
veth91c10ab ethernet unmanaged --
vethd462048 ethernet unmanaged --
vethe6faf8c ethernet unmanaged --
vethf0bd237 ethernet unmanaged --
lo loopback unmanaged --
resin-vpn tun unmanaged --
root@9d52738:~# nmcli c
NAME UUID TYPE DEVICE
Wired connection 1 b7cd7ae6-6bbe-3c64-b4a7-d687b5550671 ethernet eth0
supervisor0 a0dd8e69-49ab-4946-ba7a-b2036e96f530 bridge supervisor0
gsm d8f002d1-dfc3-3cad-ac58-c7d3cc563b75 gsm --
This is my NetworkManager config:
root@9d52738:~# cat /etc/NetworkManager/system-connections/gsm.nmconnection
[connection]
id=gsm
type=gsm
autoconnect=true
autoconnect-retries=0
[gsm]
apn=web.vodafone.de
[ppp]
no-vj-comp=true
nobsdcomp=true
nodeflate=true
[ipv4]
method=auto
[ipv6]
method=ignore
Interestingly, the modem’s devices are visible:
root@9d52738:~# ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Dec 3 11:30 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Dec 6 10:39 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Dec 6 10:39 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 3 Dec 6 21:42 /dev/ttyUSB3
crw-rw---- 1 root dialout 188, 4 Dec 6 10:39 /dev/ttyUSB4
crw-rw---- 1 root dialout 188, 5 Dec 6 10:39 /dev/ttyUSB5
These are the nm/mm versions I use:
mmcli 1.10.6
nmcli tool, version 1.20.2
The Journal does only Show Events About 1h ago, the modem went offline earlier:
root@9d52738:~# date
Fri Dec 6 23:16:39 UTC 2019
root@9d52738:~# journalctl -u ModemManager
-- Logs begin at Fri 2019-12-06 22:15:49 UTC, end at Fri 2019-12-06 23:16:40
UTC. --
-- No entries --
root@9d52738:~# journalctl -u NetworkManager
-- Logs begin at Fri 2019-12-06 22:15:49 UTC, end at Fri 2019-12-06 23:17:14
UTC. --
Dec 06 22:35:09 9d52738 NetworkManager[805]: <info> [1575671709.1903] dhcp4
(eth0): state changed bound -> expire
Dec 06 22:35:09 9d52738 NetworkManager[805]: <info> [1575671709.1906] device
(eth0): DHCPv4: 480 seconds grace period started
Dec 06 22:35:12 9d52738 NetworkManager[805]: <info> [1575671712.2717] dhcp4
(eth0): state changed expire -> bound
Dec 06 22:36:26 9d52738 NetworkManager[805]: <info> [1575671786.1989] manager:
(resin-vpn): new Tun device (/org/freedesktop/NetworkManager/Devices/655)
I cannot see anything unusual in the Service Status:
root@9d52738:~# systemctl status ModemManager.service
● ModemManager.service - Modem Manager
Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor
preset: enabled)
Active: active (running) since Fri 2019-12-06 10:38:55 UTC; 12h ago
Main PID: 3180 (ModemManager)
Tasks: 3 (limit: 2305)
Memory: 1.8M
CGroup: /system.slice/ModemManager.service
└─3180 /usr/sbin/ModemManager --log-journal
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
I am able to recover the modem manually by restarting the Service and waiting a
Minute:
root@9d52738:~# systemctl restart ModemManager.service
root@9d52738:~# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Huawei Technologies Co., Ltd.]
ME909s-120
root@9d52738:~# nmcli c
NAME UUID TYPE DEVICE
Wired connection 1 b7cd7ae6-6bbe-3c64-b4a7-d687b5550671 ethernet eth0
gsm d8f002d1-dfc3-3cad-ac58-c7d3cc563b75 gsm ttyUSB1
supervisor0 a0dd8e69-49ab-4946-ba7a-b2036e96f530 bridge supervisor0
root@9d52738:~# nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
supervisor0 bridge connected supervisor0
ttyUSB1 gsm connected gsm
ppp0 ppp disconnected --
balena0 bridge unmanaged --
br-4a4858757201 bridge unmanaged --
resin-dns bridge unmanaged --
veth607d783 ethernet unmanaged --
veth91c10ab ethernet unmanaged --
vethd462048 ethernet unmanaged --
vethe6faf8c ethernet unmanaged --
vethf0bd237 ethernet unmanaged --
lo loopback unmanaged --
resin-vpn tun unmanaged --
It is important that the modem Connection stays online without manual
Intervention. Any help with the issue much appreciated.
Kind regards
Bruno
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
