This configuration make no sense whatsoever.

1) You create a bridge with no ports. What purpose does it serve? 2) If you want to add enp7s0 as a port, why do you have a configuration for enp7s0? If an interface is a bridge port, it cannot be used for IP traffic, so assigning it an IP is pointless.

If I understand correctly, in fact I took the set up upside down. I tried br0 ---> enp7s0 when in fact the scheme is |-----> dev 1 enp7s0 ----> bridge br0 ----| |------> dev 2 Am I correct in this scheme?

Am 06.03.2014 16:19, schrieb Paul Gideon Dann:

...

If I understand correctly, in fact I took the set up upside down. I tried br0 ---> enp7s0 when in fact the scheme is

|-----> dev 1

enp7s0 ----> bridge br0 ----|

|------> dev 2

Am I correct in this scheme?

What do you mean by dev 1 and dev 2?

Independently of what dev1 and dev2 are, the answer is 'no'.

Op 6 mrt. 2014 14:15 schreef "Thomas Bächler" het volgende:

Am 06.03.2014 14:03, schrieb arnaud gaboury:

...

Dear list,

I am running a machine "hortensia" with a container "dahlia". As the container will be a server, I want to have one IP for hortensia and another one for dahlia.

On hortensia, with dhcpcd.service and systemd-networkd both disabled, I start at boot two netctl profiles.

[...]

1) You create a bridge with no ports. What purpose does it serve? 2) If you want to add enp7s0 as a port, why do you have a configuration for enp7s0? If an interface is a bridge port, it cannot be used for IP traffic, so assigning it an IP is pointless.

In fact: make enp7so a port of br0 and then you can use the bridge as the network interface for Hortensia. For either static or dhcp: use the bridge device. Ip forwarding: a bridge is a OSI layer 2 device, not a router, so ip forwording can be turned off (Ip is layer 3). As for Dahlia; i don't know exactly how containers work in Linux, but i guess you'll need to configure some virtual network device and then add that to the bridge. My best guess would be to look up how this is done with LXC. mvg, Guus

1) Two new virtual interfaces are create: one that is visible to the container, and one that is visible to the host. The host now has two interfaces, which may be bridged, or it may act as a NAT router on the interface that goes to the container. The container only sees the one interface, and uses perfectly normal means to obtain an IP address.

That's correct. When I boot the container, a new interface "vb-dahlia" appears on the host, and on the container side, i have a "host0" interface. So I guess I must have a netctl br0 profile with this line : BindsToInterface=(enp7s0 vb-dhalia) -- google.com/+arnaudgabourygabx

On Thursday 06 Mar 2014 23:01:30 arnaud gaboury wrote:

On Thu, Mar 6, 2014 at 8:00 PM, arnaud gaboury wrote:

...

...

1) Two new virtual interfaces are create: one that is visible to the container, and one that is visible to the host. The host now has two interfaces, which may be bridged, or it may act as a NAT router on the interface that goes to the container. The container only sees the one interface, and uses perfectly normal means to obtain an IP address.> That's correct. When I boot the container, a new interface "vb-dahlia" appears on the host, and on the container side, i have a "host0" interface.

So I guess I must have a netctl br0 profile with this line :

BindsToInterface=(enp7s0 vb-dhalia)

It took me a while, but I have now a working bridge on Host machine, with a static IP and a working ethernet connection on container, with a static IP.

Thank you for your help

You're welcome, Arnaud. Glad you got it working in the end. Paul

I can't help you with your specific problem, but one thing is that you need to do, is to enable the machine to forward ip packets from one interface to another. Create something like a /etc/sysctl.d/99-sysctl.conf and add this:

# Enable packet forwarding net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 1

It is. gabx@hortensia ➤➤ ~ % cat /etc/sysctl.d/30-ipforward.conf net.ipv4.ip_forward=1 net.ipv6.conf.default.forwarding=1 net.ipv6.conf.all.forwarding=1