I wasn't clear what I meant about processing of the .network file. With Ethernet or Wi-Fi (using iwd), when the link comes up, systemd-networkd does the Right Thing and starts network services on the interface, running a DHCP client or setting up static address(es), routes, etc., as specified in the .network file. When ModemManager establishes the connection with the 3G carrier, systemd-networkd seems to be unaware of the event, and I have to poke it with "systemd restart systemd-networkd" or "networkctl reload" before it tries to use the information in the .network file for the interface. It seems to me like that ought to happen automatically. I suspect that ModemManager needs to be changed to inform systemd-networkd.
So far, it's not looking like there's an effort to integrate
ModemManager (or something similar) with systemd-networkd, which
is kind of a shame. If I come up with anything useful toward
making that happen, I'll offer a pull request, but at the moment
I'm looking at cobbling something together with Python.
Bruce A. Johnson | Firmware Engineer Blue Ridge Networks, Inc. 14120 Parke Long Court Suite 103 | Chantilly, VA 20151 Main: 1.800.722.1168 | Direct: 703-633-7332 http://www.blueridgenetworks.com OpenPGP key ID: 296D1CD6F2B84CAB https://keys.openpgp.org/
I took a closer look at what's going on with systemd-networkd, and I found whether I use ModemManager or mbim-cli to connect to the mobile network, the .network file will be processed, but _only after I restart systemd-networkd_.I'm not 100% sure this applies to all the applications in the systemd ecosystem (like systemd-networkd), but systemd is reloading .unit, .service, .mount and all the other files there are only after a `systemctl daemon-reload`. That's the intended behaviour. Just wanted to mention this. Can't comment on anything else, though, as I have no clue either. But I'm interested in this topic and am silently monitoring this thread.
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
