Hi On 2016-04-20, Raphael Hertzog wrote: > Hi Stefan, > > On Thu, 17 Mar 2016 03:01:21 +0100 Stefan Lippers-Hollmann <s....@gmx.de> > wrote: > > Given that it's opt-in, explicitly documenting this as volatile > > and potentially unsupported (in the future) might be a way out, > > but I'd still hate to eventually break previously working network > > configurations in the future. > > Please do this if it's the only way to reassure you about this feature. > But this setup is largely documented and already in use in ArchLinux for > example and I was surprised to see that Debian did not support it yet. > > It seems to work rather well for most persons including Debian persons: > https://www.joachim-breitner.de/blog/664-Switching_to_systemd-networkd > > That article is dated Oct 2014 so we're really late in the game... please > fix this soon. Thank you.
What is your opinion regarding the system inherent problems I've raised? [ pasting from <20160317030121.68b23ccf@mir>, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766746#22 ] - systemd-networkd upstream hasn't committed to a policy regarding wireless devices, its handling might change in the future - 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 was really hoping to get some feedback, especially the later three issues, from those looking to get it supported. Regards Stefan Lippers-Hollmann
pgpNCZD6az3ki.pgp
Description: Digitale Signatur von OpenPGP