Ethernet Bridge development
 help / color / mirror / Atom feed
From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: Sander Klein <roedie@roedie.nl>
Cc: Bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] Bridge - vlan - bond
Date: Sat, 05 Dec 2009 19:24:01 +0100	[thread overview]
Message-ID: <4B1AA541.2030500@free.fr> (raw)
In-Reply-To: <7a0b4b1b5dc484f5e0c2f619d4bfb804@localhost>

Sander Klein wrote :
> Hi list,
> 
> I have a problem with using bonding, with vlans and bridging. I'm trying
> to create the following situation:

Can you please also describe what you try to achieve, and not only your setup ?

What are the expected effects ?

Your bonding setup (active-backup) will lead to one port enabled and one disabled.

Why don't you simply use eth0.101 and eth1.101 as two ports of br101, and enable stp ?

Enabling stp would achieve the same result : one port in forwarding state and one in the blocked state.

	Nicolas.

> Network overview:
> 
>                +------+
> +--------+     |blade |
> |        |-----|switch| eth0 +------+
> |        |     |      |------|      |
> |        |     +------+      |      |
> | switch |                   | host |
> |        |     +------+      |      |
> |        |     |blade |------|      |
> |        |-----|switch| eth1 +------+
> +--------+     |      |
>                +------+
> 
> Situation on the host:
> 
> +----+
> |eth0|------+
> +----+      |
>          +-----+   +---------+   +-----+
>          |bond0|---|bond0.101|---|br101|
>          +-----+   +---------+   +-----+
> +----+      |
> |eth1|------+
> +----+
> 
> 
> Now, as soon as the bridge comes up I get the error 'bond0.101: received
> packet with  own address as source address'. This happens every time I
> start a new sessioen to a host. Sniffing with tcpdump and wireshark on
> br101 show all arp packets 2 times. I cannot figure out why this is
> happening. When I create this situation without the bridge I do not get
> duplicate traffic, so it's not coming from the network.
> 
> My config is:
> 
> auto bond0
> iface bond0 inet manual
>         slaves eth0 eth1
>         bond_primary eth0
>         bond_mode active-backup
>         bond_miimon 100
> 
> auto bond0.101
> iface bond0.101 inet manual
> 
> auto br0
> iface br0 inet static
>         bridge_ports bond0.101
>         bridge_stp off
>         address 192.168.1.25
>         netmask 255.255.255.0
>         gateway 192.168.1.1
> 
> I've tried this with the stock Debian Lenny kernel (2.6.26) and 2.6.32. Am
> I doing something wrong here?
> 
> Greets,
> 
> Sander Klein
> 
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
> 


  parent reply	other threads:[~2009-12-05 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05 16:30 [Bridge] Bridge - vlan - bond Sander Klein
2009-12-05 16:58 ` Sebastian Gottschall (DD-WRT)
2009-12-05 18:24 ` Nicolas de Pesloüan [this message]
2009-12-05 19:47   ` Sander Klein
2009-12-09 22:21     ` Nicolas de Pesloüan
2009-12-06 17:17 ` richardvoigt
2009-12-06 20:14   ` Sander Klein

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=4B1AA541.2030500@free.fr \
    --to=nicolas.2p.debian@free.fr \
    --cc=bridge@lists.linux-foundation.org \
    --cc=roedie@roedie.nl \
    /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