[systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
I already used for a while a container (Arch on Arch). I had two distinct IP and a working setup thanks to good help from Tom Gundersen I am trying to replicate my network settings on a new setup (Fedora on Arch). For now, I am just trying with DHCP. Here the setup on host:

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container Is this correct? Looks fine.

Re: [systemd-devel] network interface down in container

2015-04-30 Thread Lennart Poettering
On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container Is this correct? Looks fine. * Now on the container side: Nothing configured.

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : #

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 12:48 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury

Re: [systemd-devel] network interface down in container

2015-04-30 Thread Lennart Poettering
On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: E2978F 2: host0 Link File: n/a Network File: n/a Type: ether State: off (unmanaged) HW Address: 0e:7f:c3:fb:25:b1 MTU: 1500 So, as it appears networkd does consider itself

Re: [systemd-devel] network interface down in container

2015-04-30 Thread Lennart Poettering
On Thu, 30.04.15 12:18, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015, 2:22 PM Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: E2978F 2: host0 Link File: n/a Network File: n/a Type: ether State: off (unmanaged) HW Address:

Re: [systemd-devel] network interface down in container

2015-04-30 Thread Dan Williams
On Thu, 2015-04-30 at 11:44 +0200, Lennart Poettering wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container Is this correct? Looks fine.