On Tuesday, 3 April 2018 11:21:37 AM AEST Geoff D'Arcy via luv-main wrote: > On 2018-04-03 08:32, Manoj C Menon via luv-main wrote: > > Have you tried "systemctl restart systemd-networkd" ? > > Thanks Manoj
https://www.freedesktop.org/software/systemd/man/systemd.network.html https://wiki.archlinux.org/index.php/systemd-networkd https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html The above 3 URLs document the systemd-netorkd service, the last one notes "when configuration is updated and systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up manually". So it seems that restarting systemd-networkd might not do what is desired. But I have never wanted to use it so I don't know a lot about it. While I generally think systemd is a good thing the networking side of it is something I haven't felt a need to use. > Yes did try that and not using netplan, however Russell's suggestion > does exactly what I need so all good. I believe that the traditional Debian network configuration (ifup/ifdown etc) developed in the mid 90's is for most systems the best way of doing things. The only exception I've found so far is wireless networks on laptops for which NetworkManager is usually quite good (apart from when it breaks and refuses to do anything). If you use ifup/ifdown then systemd won't know that much about what you are doing. It might be a good topic for a Saturday LUV meeting to explore these networking configuration issues. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
