-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Description
Is your feature request related to a problem? Please describe.
Setting up WWAN connection with systemd-networkd is the major hurdle at the moment.
Describe the solution you'd like
Ability to specify a new .network or .netdev link type which would talk with ModemManager to establish and properly configure IP interface managed by systemd-networkd
Describe alternatives you've considered
Right now we have to resort to scripting and manual output parsing which is cumbersome and error-prone.
The typical WWAN connection bring-up looks as follows:
mmcli --list-modems
/org/freedesktop/ModemManager1/Modem/5 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module
# this gives the path and modem number e. g. 5:
mmcli --simple-connect="apn=test-internet.myapn" -m 5
successfully connected the modem
mmcli -m 5
...
Bearer paths: /org/freedesktop/ModemManager1/Bearer/3
# this (if succeed) gives the number of the established bearer e. g. 3:
mmcli -b 3
General path: /org/freedesktop/ModemManager1/Bearer/3
type: default
Status connected: yes
suspended: no
interface: wwan0
ip timeout: 20
Properties apn: test-internet.myapn
roaming: allowed
IPv4 configuration method: static
address: 10.10.42.234
prefix: 30
gateway: 10.10.42.24
dns: 8.8.8.8, 8.8.4.4
mtu: 1500
Statistics duration: 60
attempts: 1
total-duration: 60
Now we have to parse the output of the mmcli (or use dbus - whatever) and get the IP address, Gateway and other parameters to generate wwan.network so it can be controlled with systemd-networkd.
Would be way more convenient if systemd-networkd could take care of low-level details and extract that information directly from ModemManager as well as gracefully handle network interruptions etc.
The systemd version you checked that didn't have the feature you are asking for
247