On Wed, 20 Apr 2016, Stefan Lippers-Hollmann wrote: > - systemd-networkd upstream hasn't committed to a policy regarding > wireless devices, its handling might change in the future
Yes, but the fact that systemd might get some native support is not guaranteed to break the setup we want to use here. > - systemd-networkd doesn't provide any tools like ifup/ ifdown so > far, making dynamic configuration changes (e.g. switch from wired- > to wireless networks) difficult. > - hotpluggable wireless cards (USB) are problematic in the sense > that systemd will wait (until timeout, 90s by default) if the > a configured device is unplugged. > - basically unsuitable for notebook scenarios, where one might > occasionally want to switch to wired ethernet (so far routing > metrics seem to be the only, quite hacky workaround). I think that people opting for systemd-networkd are fine with those limitations. Consider that people want to use it on devices like the raspberry pi which is not really like a smartphone or a laptop... Myself I was interested to document this setup for Kali Linux users (Debian derivative) where we use lots of ARM devices with built-in wifi. I also don't know what's hacky with the routing metric usage. What else would be its purpose if not to prioritize between different routes? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
