Chris's Wiki :: blog/linux/SystemdNetworkdWhy Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/SystemdNetworkdWhy?atomcommentsDWiki2016-09-29T06:14:43ZRecent comments in Chris's Wiki :: blog/linux/SystemdNetworkdWhy.By Anon on /blog/linux/SystemdNetworkdWhytag:CSpace:blog/linux/SystemdNetworkdWhy:3a629abba9d12a63fd3b919558276385e1f61ba2Anon<div class="wikitext"><p>You can get systemd to run a program each time the networking is modified (but be aware this happens every time a DHCP lease is renewed) by using a path activated service as hinted at by <a href="https://www.joachim-breitner.de/blog/664-Switching_to_systemd-networkd#comment_1">https://www.joachim-breitner.de/blog/664-Switching_to_systemd-networkd#comment_1</a> .</p>
</div>2016-09-29T06:14:43ZBy Chris Siebenmann on /blog/linux/SystemdNetworkdWhytag:CSpace:blog/linux/SystemdNetworkdWhy:c2a784231414597a5139103b42f924a690adb9f7Chris Siebenmann<div class="wikitext"><p>Networkd doesn't seem to have any support for policy routing and the
things you need to support it. In <a href="https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdNetworkdSetup">my setup</a>
I deal with this by having my 'set everything up' systemd <code>.service</code>
(which runs some scripts to do all the work) specify that it is run after
systemd-networkd-wait-online.service. This is not perfect (although it
works for me) and it definitely wouldn't cope with a dynamic situation
where devices are coming and going and you need to reconfigure things
as they do.</p>
<p>It's unfortunate that as far as I know you can't get networkd to easily
notify you of networking changes in a way that you can react to. It
probably emits DBus notifications about things, but I don't think there's
anything beyond that.</p>
<p>(I imagine the systemd people will fix this someday but that they also
consider it out of scope for the early iterations of networkd. Possibly
they feel that that sort of sophistication actually belongs in
NetworkManager, at which point you have other problems.)</p>
</div>2015-06-25T20:51:52ZBy Garth on /blog/linux/SystemdNetworkdWhytag:CSpace:blog/linux/SystemdNetworkdWhy:96169e796fd9f994ca4124b08453498627ab38f2Garth<div class="wikitext"><p>A quick question on networkd - does it support policy routing and associated custom route tables?</p>
<p>Currently having all sorts of grief using ifcfg- files with Fedora 22 Server, and seeing your posts has prompted me to start thinking of the switch to networkd - IFF it supports policy routing and multiple custom routing tables.</p>
<p>Cheers.</p>
</div>2015-06-25T20:34:47ZBy Albert on /blog/linux/SystemdNetworkdWhytag:CSpace:blog/linux/SystemdNetworkdWhy:0cf44a80b249672cdef2b24db89f7b9ec2ef32b7Albert<div class="wikitext"><p>I'm pretty sure I saw an ifcfg man page some time in the past where all the variables used in the ifcfg-* files were documented (similarly there were ifcfg-bridge, ifcfg-vlan etc. man pages to document extra variables used for those types of interfaces). Google does confirm that they exist, however I can't find them in any of the redhat/fedora/centos systems I have access to.</p>
</div>2015-01-21T09:28:13Z