Yes; I thnk instead it's a DHCP issue; since the device has no address to start, adding the tunnel endpoing to that socket without an address seems to be failing. It has to wait until the DHCP signal, and then it really needs the DHCP address to update the tunnel endpoint configuration.
On Mon, Feb 29, 2016 at 10:36 PM, Kai Krakow <[email protected]> wrote: > Am Mon, 29 Feb 2016 19:12:11 -0800 > schrieb J Decker <[email protected]>: > >> I would have thought that naming 00-eth0.network; 01-eth1.network or >> something would start devices in that order? > > No... It does say nothing about order in your sense. It's just ordering > which configuration overwrites another when options are specified in > multiple files. > > So it's not start order, it just order of precedence for configuration > options. > > -- > Regards, > Kai > > Replies to list-only preferred. > > _______________________________________________ > systemd-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
