<div dir="ltr">goes back to 'can we have a configurable script to run when DHCP assigns the address?'<div>Surely it can't be that hard to read a config line, save it, and later execute a script</div><div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Sep 6, 2016 at 1:54 PM, Ernst Bammer <<a href="mailto:herr.ernst@gmail.com" target="_blank">herr.ernst@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, sorry to bring this up again, but maybe somebody is back from vacation who can answer this? ;-) Best regards, Ernst On Sun, Jul 24, 2016 at 12:31 PM, Ernst Bammer <<a href="mailto:herr.ernst@gmail.com">herr.ernst@gmail.com</a>> wrote: > Hi, > > I have a service that depends on a non-loopback IPv4 address to be > available at start-up. My network configuration is done with networkd, > it's very simple and basically just: > > [Match] > Name=eth* > [Network] > DHCP=v4 > > I've added the following to my service: > > [Unit] > Requires=network-online.target > After=network-online.target > > Unfortunately, there is no IPv4 address when the service tries to > start (and then crashes). > For debugging purposes, I added this to [Service]: > > ExecStartPre=/bin/sh -c "/bin/cat /run/systemd/netif/links/*" > ExecStartPre=/bin/sh -c "/bin/cat /run/systemd/netif/leases/*" > > On reboot, I see this in the journal: > > Jul 24 11:41:59 myhost sh[492]: # This is private data. Do not parse. > Jul 24 11:41:59 myhost sh[492]: ADMIN_STATE=configured > Jul 24 11:41:59 myhost sh[492]: OPER_STATE=degraded > Jul 24 11:41:59 myhost sh[492]: FLAGS=69699 > Jul 24 11:42:00 myhost sh[529]: /bin/cat: /run/systemd/netif/leases/*: > No such file or directory > Jul 24 11:42:00 myhost systemd[1]: test.service: control process > exited, code=exited status=1 > Jul 24 11:42:00 myhost systemd[1]: Failed to start Test. > Jul 24 11:42:00 myhost systemd[1]: Unit test.service entered failed state. > > I suspect the problem might be that the network interface also gets a > link-local IPv6 address, and thus systemd-networkd-wait-online > immediately returns. If I disable IPv6 on my system (by blacklisting > the ipv6 module), it works as expected (s-n-w-o waiting for DHCPV4 > address). > > Is there a way to get s-n-w-o to wait for an address family (in my > case IPv4) to be available? Or is there any other workaround? > > FWIW, I'm using Debian 8 Jessie (systemd version 215). > > Thank you! > Ernst _______________________________________________ systemd-devel mailing list <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> </blockquote></div> </div>