From: Jelle de Jong <jelledejong@powercraft.nl>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] bond-mode 4 bridge-utils 3.x kernel not fully working
Date: Mon, 17 Jun 2013 13:00:11 +0200 [thread overview]
Message-ID: <51BEEC3B.4080205@powercraft.nl> (raw)
In-Reply-To: <51A53977.1090106@powercraft.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29/05/13 01:10, Jelle de Jong wrote:
> I also sent this email to bonding-devel@lists.sourceforge.net
>
> I spent ours debugging and finding out what points to the problem.
>
> I run kvm quests with bridged networking on a bonding lacp set-up,
> with the 2.6 kernel this has been working fine for years. But with
> the 3.x kernel this doesn?t work any more.
>
> Traffic comes out the KVM quests but doesn?t come in. If I disable
> bonding everything just works again.
>
> # working with 2.6 not working with 3.x cat
> /etc/network/interfaces auto lo iface lo inet loopback
>
> auto bond0 iface bond0 inet manual slaves eth0 eth1 bond-mode 4
> bond-miimon 100 pre-up /sbin/ifconfig bond0 mtu 9000
>
> auto br0 iface br0 inet dhcp bridge_fd 0 bridge_stp on bridge_ports
> bond0
>
> # working with 3.x but no bonding!! cat /etc/network/interfaces
> auto lo iface lo inet loopback
>
> auto eth0 iface eth0 inet manual mtu 900
>
> auto br0 iface br0 inet dhcp bridge_fd 0 bridge_stp on bridge_ports
> eth0
>
> # uname -a Linux viktoriya 3.2.0-4-amd64 #1 SMP Debian
> 3.2.41-2+deb7u2 x86_64 GNU/Linux
>
> bridge-utils version 1.5-6
>
> I already checked iptabls, ebtables there are no running rules and
> the bellow on zero or one doesn't make a difference either also
> disabling bridge_stp off or bridge_maxwait 0 doesn't seem to help.
>
> /bin/echo "0" > /proc/sys/net/bridge/bridge-nf-call-arptables
> /bin/echo "0" > /proc/sys/net/bridge/bridge-nf-call-ip6tables
> /bin/echo "0" > /proc/sys/net/bridge/bridge-nf-call-iptables
Anybody? I?m still unable to use bonding lacp & bridge & vlans with
kvm guest in a 3.x kernel (2.6 is working fine)
Kind regards,
Jelle de Jong
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iJwEAQECAAYFAlG+7DcACgkQ1WclBW9j5HmXUwP9EXmWz7h2K+3LkWk0NbfAdxd6
nTb2nTWGX/659DqRIIIJbxz3haxxdDIUqjS6QBkAyaG8zJLwNSa2Ks4KdL5mrRJw
hSJOqRNhv7u92tNv1uZeN+bZ8huFvvPgMaMd4Mx/vCta1isSOtSzbS9devjg4SFP
0ZX6DhG32uELhpk1AtA=
=NrXT
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-06-17 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 23:10 [Bridge] bond-mode 4 bridge-utils 3.x kernel not fully working Jelle de Jong
2013-05-29 7:29 ` Wilco Baan Hofman
2013-05-29 7:54 ` Jelle de Jong
2013-06-17 11:00 ` Jelle de Jong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51BEEC3B.4080205@powercraft.nl \
--to=jelledejong@powercraft.nl \
--cc=bridge@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).