On Mon, Feb 29, 2016 at 7:12 PM, J Decker <d3c...@gmail.com> wrote: > systemd 229-3 > > I recently updated my Arch Linux. > > https://wiki.archlinux.org/index.php/IPv6_tunnel_broker_setup > > using a hurricane electric tunnel... > > and now the tunnel device wants to start and add all the static > addresses that are specified on other physical net devices.... in fact > the HE is attached to a bridge that has to wait itself for other > things to start. > > I would have thought that naming 00-eth0.network; 01-eth1.network or > something would start devices in that order? > > How do I specify a dependance order between network configurations?
Sorry I sent to wrong place. I did recently add a ipv6 to a bridge to stop another issue. but after moving the ipv6 to the end of the bridge it still doesn't wait for eth0 to come up before it starts the tunnel [code] [root@tower2 network]# systemctl start systemd-networkd [root@tower2 network]# Feb 29 20:15:23 tower2 polkitd[913]: Registered Authentication Agent for unix-process:3325:15819222 (system bus name :1.44 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf-8) Feb 29 20:15:23 tower2 systemd[1]: Starting Network Service... Feb 29 20:15:23 tower2 systemd-networkd[3331]: [/etc/systemd/network/he-tunnel.netdev:9] Tunnel addresses incompatible, ignoring assignment: <MyIP> Feb 29 20:15:23 tower2 systemd-networkd[3331]: [/etc/systemd/network/he-tunnel.netdev:10] Tunnel addresses incompatible, ignoring assignment: <TunnelIP> Feb 29 20:15:23 tower2 systemd-networkd[3331]: Tunnel with invalid address family configured in /etc/systemd/network/he-tunnel.netdev. Ignoring Feb 29 20:15:23 tower2 systemd-networkd[3331]: [/etc/systemd/network/he-tunnel.network:7] Route is invalid, ignoring assignment: <MyRouter IPv6 IP> Feb 29 20:15:23 tower2 systemd-networkd[3331]: [/etc/systemd/network/01-eth0.network:8] Tunnel is invalid, ignoring assignment: he-ipv6 [/code] there's then another started... oh starting started. eth0 needs to be up already and I can't confirm why it wouldn't be? it's DHCP so it needs to know when it gets its address before I can assign the he-tunnel. [/code] Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: netdev ready Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: Gained IPv6LL Feb 29 20:15:23 tower2 systemd-networkd[3331]: eno1: Gained IPv6LL Feb 29 20:15:23 tower2 systemd-networkd[3331]: eth0: Gained IPv6LL Feb 29 20:15:23 tower2 systemd-networkd[3331]: Enumeration completed Feb 29 20:15:23 tower2 systemd[1]: Started Network Service. Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: netdev exists, using ex [/code] _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
