I have found that you will need to bring the virtual interface up (the one handled by systemd-nspawn).
Right. I am left after I boot my machine (the host) with this : 4: vb-dahlia: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master br0 state DOWN group default qlen 1000 link/ether 62:a2:6b:f4:0f:87 brd ff:ff:ff:ff:ff:ff I have to manually # ip link set dev vb-dahlia up to get the network working on the container : 2: host0: <BROADCAST,MULTICAST,ALLMULTI,NOTRAILERS,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 5a:51:a2:a2:b5:fb 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 inet6 fe80::5851:a2ff:fea2:b5fb/64 scope link valid_lft forever preferred_lft forever If you are running systemd-networkd on
the host then you can do that easily with a network file. I've called mine vb-veth.network and it contains:
[Match] Name=vb-*
I will try your hack asap
Right now on the host side I have everything being handled only by systemd-{networkd,nspawn}, I don't add any physical interfaces to the bridge Ah? I have two netctl profiles, one for my physical eth (enp7s0) with no ip, one for bridge (br0) with enp7s0 binded to. So you mean you don't have any bridge profile managed by netctl ?
but I suppose that would also be possible to do with
systemd-networkd.