Here's an interesting data point: We noticed that our bond interface was
reporting a large number of dropped packets, particularly compared to
when we were using CentOS 6.5. As a test I decided to try out the new
"team" alternative to bonding that's offered by CentOS 7 and the dropped
packets v
On Tue, Sep 15, 2015 at 3:29 PM, Andrey Repin wrote:
> Greetings, Fajar A. Nugraha!
>
>>> We will have to do some thorough testing with the 4.2 (or possibly 4.1)
>>> kernel over the next few weeks to make sure this kernel doesn't introduce
>>> new issues.
>
>> That would seem like the best option
On 09/14/2015 11:02 PM, Fajar A. Nugraha wrote:
Assuming your problem is caused by bridging the veth interface,
there's an alternate networking setup with proxyarp + route that might
work. It doesn't use bridge, and only works for privileged containers.
I'll investigate how this could be setup
On 09/15/2015 01:29 AM, Andrey Repin wrote:
2b. If you absolutely want to communicate with containers from host via
network, you will need a similarly set up interface on the host.
This is a little complicated without a helper script, but still doable:
We do need to be able to communicate with
Greetings, Fajar A. Nugraha!
>> We will have to do some thorough testing with the 4.2 (or possibly 4.1)
>> kernel over the next few weeks to make sure this kernel doesn't introduce
>> new issues.
> That would seem like the best option for you.
>> new issues. Our only other option would be to fal
On Mon, Sep 14, 2015 at 8:56 PM, Peter Steele wrote:
> We will have to do some thorough testing with the 4.2 (or possibly 4.1)
> kernel over the next few weeks to make sure this kernel doesn't introduce
> new issues.
That would seem like the best option for you.
> new issues. Our only other opti
On 09/13/2015 06:19 AM, Fajar A. Nugraha wrote:
Had you use Ubuntu you could probably say something like "kernel 4.2
should be released as linux-generic-lts-wily for ubuntu 14.04 in about
two months, and we can switch to distro-supported package then"
Had you use Oracle Linux with support subscr
On Fri, Sep 11, 2015 at 7:31 PM, Peter Steele wrote:
> I tried the 4.2 kernel and the problem appears to be fixed in this kernel
> for my LXC tests--the arp tables update properly with this kernel. CentOS
> 7.1 is running kernel 3.10. Not sure what the QA folks here will think about
> using the 4.
On 09/11/2015 12:08 PM, Andrey Repin wrote:
So, have you tried getting rid of the bridge in first place?
The problem isn't the bridge per se, it's the bond mode. If I use
active-backup the veth->bridge->bond path from container to container
works as expected. Bond modes using load balancing o
Greetings, Peter Steele!
>> * Is even LXC not needed to reproduce the issue but just a bridge on a bound
>> and some other devices?
> I have not been able to reproduce the problem except between containers
> running on different hosts. Behavior is the same for lxc and libvirt-lxc.
>> * Did this
On 09/10/2015 11:14 PM, Guido Jäkel wrote:
* Is even LXC not needed to reproduce the issue but just a bridge on a bound
and some other devices?
I have not been able to reproduce the problem except between containers
running on different hosts. Behavior is the same for lxc and libvirt-lxc.
* Di
On 09/10/2015 07:57 PM, Fajar A. Nugraha wrote:
If I read the bug report correctly, it's not moved to lxc. Rather, KVM
is not required to reproduce it, using lxc is enough to trigger the
bug. Using KVM will of course still trigger the bug as well.
Sorry, I didn't mean the bug was moved to lxc,
Dear Peter, Hi Fajar,
* Is even LXC not needed to reproduce the issue but just a bridge on a bound
and some other devices?
* Did this issue appear if you use a higher MAC prefix than 64:... for the
veths?
May you dump the arp traffic (maybe together with icmp) on the host? I'm
interested in wh
On Fri, Sep 11, 2015 at 7:38 AM, Peter Steele wrote:
> I believe this link describes the exact problem I've been experiencing:
>
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/785668
>
> and although the original post targets KVM, later in the thread it moves to
> LXC.
If I read the bu
I believe this link describes the exact problem I've been experiencing:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/785668
and although the original post targets KVM, later in the thread it moves
to LXC. This is an old bug report and I'm surprised that this has not
been addressed i
I've configured a standard CentOS bridge/bond, the exact same setup that
I use for creating VMs. VMs on different hosts communicate through the
bridge without issues. Containers that use the identical bridge however
cannot reliably connect to containers on different hosts. We've
determined that
Hi Peter,
since you mentioned you are using bridged interfaces, is my assumption
correct that your containers's network connection is joined directly
to this bridge and containers talk to the world direcly (L2) and not
via routed (L3) network over host OS?
Did you try using routed setup (using bo
I don't think I'm up to the challenge of an ASCII art representation of
our cluster. How's this instead?
We run on a cluster of 1U and 2U servers. Each server is connected to
the same network by either multiple 1GigE or 10GigE links and is
configured with a bonded/bridged interface. Every serv
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 rea
Greetings, Peter Steele!
> 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
On 09/07/2015 11:49 AM, 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
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 con
22 matches
Mail list logo
