Re: [systemd-devel] Satitic IP in container

2014-03-03 Thread arnaud gaboury
> > On host side : > /etc/systemd/network/70-dahlia.netdev *** > [Match] > Host=host0 > Virtualization=container > > [NetDev] > Name=br0 > Kind=bridge > > [Match] > Virtualization=container > > *** /etc/systemd/network/80-dahlia.network *** > [Network] > DHCP=no > DNS=192.168.1.254 > > > [Addr

Re: [systemd-devel] Satitic IP in container

2014-03-01 Thread arnaud gaboury
On Sat, Mar 1, 2014 at 3:26 PM, arnaud gaboury wrote: > > >> >> No, --network-bridge=br0 means that a pair of veth devices are created >> (host0 inside the container and vb-* outside), and the vb-* is added >> to your bridge br0. So you should really have host0 in the container >> with this option

Re: [systemd-devel] Satitic IP in container

2014-03-01 Thread arnaud gaboury
> > No, --network-bridge=br0 means that a pair of veth devices are created > (host0 inside the container and vb-* outside), and the vb-* is added > to your bridge br0. So you should really have host0 in the container > with this option. However, if you don't, which device did this mac > address you

Re: [systemd-devel] Satitic IP in container

2014-03-01 Thread Tom Gundersen
On Sat, Mar 1, 2014 at 2:28 PM, arnaud gaboury wrote: >> I suggest simply matching on the name >> instead: "Name=host0". > > I have a problem with this host0. On container, no host0 listed. If I > remember correcty, I shall start systemd-nspawn with some more options, like > --network-veth, right

Re: [systemd-devel] Satitic IP in container

2014-03-01 Thread arnaud gaboury
You mean the MAC address of the 'host0' device? This will not be > stable between reboots of the container, so I guess this won't work > (you can verify with "ip link"). You are right, this address changes across reboot. I get rid of this line. I suggest simply matching on the name > instead: "

Re: [systemd-devel] Satitic IP in container

2014-03-01 Thread Tom Gundersen
On Sat, Mar 1, 2014 at 9:18 AM, arnaud gaboury wrote: > I set up successful a Arch container managed by systemd-nspsawn. > > I have an issue setting an IP for the container. > > My host is Arch, running custom Kernel 3.13.5-1 (userspace is set) and > systemd-git (lats updated yesterday evening). >

[systemd-devel] Satitic IP in container

2014-03-01 Thread arnaud gaboury
I set up successful a Arch container managed by systemd-nspsawn. I have an issue setting an IP for the container. My host is Arch, running custom Kernel 3.13.5-1 (userspace is set) and systemd-git (lats updated yesterday evening). dhcpcd.service is disabled and network is started with these profi