[lxc-users] Containers have network issues when their host uses a bonded interface

[Guido Jäkel]

Dear Peter,

may you paint a small ASCII art of your desired network setup and the network configuration? I see no reason that "LXC", i.e. the veth connecting two differently namespaced IP stacks is responsible for any problems.

BTW: I'm using a complex network setup with no problems, too. A real NIC is connected to a selected trunk of VLANs; they are decoded and connected to a couple of bridges and the containers are attached to one or more of it as needed for the business case.

greetings

Guido


On 07.09.2015 20:49, Peter Steele wrote:
> We're having issues with networking connections in our containers when the host is configured with bonded interfaces. When we configure these same servers to run with VMs, everything works fine, but when we swap out the VMs for equivalently configured containers, we get all kinds of network connection failures between containers. The network issues go away when we reduce the bond to have a single member. More specifically, we configure our server with a host bridge (br0), where the host bridge links to the host's bonded interface (bond0). We've been using this model for years with VMs. Something isn't working quite right with containers though.
> 
> Is there something we need to set in our containers' config files when the host is setup with bonding?
> 
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users