[systemd-devel] unable to bring an interface UP with systemd-networkd

[Tom Gundersen]

On Tue, Mar 11, 2014 at 6:42 PM, arnaud gaboury
<arnaud.gaboury at gmail.com> wrote:
> I run a dahlia container on a hortensia machine. Both are Arch boxes,
> and container is managed with nspawn and networkd.
>
> When I boot the hortensia machine, part of the ip addr output is :
>
> gabx at hortensia ➤➤ ~ % ip addr
> ................
> 4: vb-dahlia: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master br0
> state DOWN group default qlen 1000
>     link/ether 6a:91:b5:72:db:c5 brd ff:ff:ff:ff:ff:ff
>
>
> gab at dahlia ➤➤ ~ % ip addr
> ..............................
> 2: host0: <NO-CARRIER,BROADCAST,MULTICAST,ALLMULTI,AUTOMEDIA,UP> mtu
> 1500 qdisc pfifo_fast state DOWN group default qlen 1000
>     link/ether 7e:3a:5a:93:ab:ee brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.94/24 brd 192.168.1.255 scope global host0
>        valid_lft forever preferred_lft forever
>
> I have to manually
> gabx at hortensia ➤➤ ~ # ip link set dev vb-dahlia up
> to get network up in container.
>
>
> Here are my network config files on hortensia:
>
> /etc/systemd/dahlia.netdev
> [Match]
> Virtualization=container

If hortensia is your host, then this will have no effect as
"Virtualization=container" means it should only take effect in a
container.

> [NetDev]
> Name=vb-dahlia
> Kind=bridge

You don't want to set up vb-dahlia as a bridge. This should be a veth
device created automatically by nspawn for you, and added to whatever
bridge (on the host machine) you specify. What you need to do, is to
create that bridge though. If you want to use networkd on the host to
do that use:

***
/etc/systemd/network/br0.netdev
[NetDev]
Name=br0
Kind=bridge
***

> /etc/systemd/80-container-host0.network
> [Match]
> Virtualization=container
> Name=host0
>
> [Network]
> DHCP=no

This is ok, but DHCP defaults to 'no', so you can skip it.

> DNS=192.168.1.254
> Bridge=br0

Hm, are you sure you want to have a bridge in your container, usually
that's on the host (and joined by nspawn itself)? You probably want to
drop this line.

> [Address]
> Address=192.168.1.94/24
>
> [Route]
> Gateway=192.168.1.254
>
>
> Ethernet and bridge are both started with netctl profiles. eth has no
> IP and bridge br0 binds (enp7s0 vb-dahlia).
> No network settings inside the container, and systemd-networkd disabled.
>
> I have tried many various configurations, but the vb-dahlia interface
> is always DOWN .
>
> What am I missing or misconfiguring ?
>
> Thank you for help
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel