The interface _is_ required for online access, therefore, setting RequiredForOnline=no is not an option.
Am 27. Juni 2026 08:22:26 MESZ schrieb Sietse van Zanen <[email protected]>: >Checking with networkctl which (sub)interface is causing the issue and set >RequiredForOnline=no should be the quick fix for this. > >-Sietse > >-----Original Message----- >From: systemd-devel <[email protected]> On Behalf Of >Thomas Köller >Sent: Friday, 26 June 2026 23:10 >To: [email protected] >Subject: [systemd-devel] Mobile phone USB tethering > >I have a problem using a network interface created by using my mobile phone's >USB tethering function. I am normally using my laptop's built-in wifi adapter, >and this works flawlessly. If I connect my mobile phone via USB and enable its >'USB tethering' function, the network interface is created and even >successfully configured (via the phones DHCP server), however, >systemd-networkd-wait-online seems to not recognize it and times out. This is >what it says: > >root@yoga:/etc/systemd/system# journalctl -l -b -u >systemd-networkd-wait-online.service >Jun 26 13:47:19 yoga systemd[1]: Starting systemd-networkd-wait-online.service >- Wait for Network to be Online... >Jun 26 13:49:20 yoga systemd-networkd-wait-online[1273]: Timeout occurred >while waiting for network connectivity. >Jun 26 13:49:20 yoga systemd[1]: systemd-networkd-wait-online.service: >Main process exited, code=exited, status=1/FAILURE Jun 26 13:49:20 yoga >systemd[1]: systemd-networkd-wait-online.service: >Failed with result 'exit-code'. >Jun 26 13:49:20 yoga systemd[1]: Failed to start >systemd-networkd-wait-online.service - Wait for Network to be Online. > >As already mentioned, the interface does not seem to have any issues and is >fully functional after systemd-networkd-wait-online.service timed out. > >I am using systemd 259 (259.6-1.fc44). The built-in wifi adapter has been >disabled by setting 'ActivationPolicy = down' in its .network file. > > >
