From: "richardvoigt@gmail.com" <richardvoigt@gmail.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: bridge@lists.linux-foundation.org, bonding-devel@lists.sourceforge.net
Subject: Re: [Bridge] [Bonding-devel] received packet with own address as source address
Date: Thu, 4 Dec 2008 04:18:54 +0000 [thread overview]
Message-ID: <2e59e6970812032018lcedac31o4de5cd71de718bd0@mail.gmail.com> (raw)
In-Reply-To: <25142.1228351616@death.nxdomain.ibm.com>
On Thu, Dec 4, 2008 at 12:46 AM, Jay Vosburgh <fubar@us.ibm.com> wrote:
> Matthew Kent <matt@bravenet.com> wrote:
>
>>Trying to determine if I have a misconfiguration, misunderstanding or
>>have stumbled on a bug.
I think there is a bug here although the description doesn't sound
like the buggy case.
Here is the specific configuration that produces the same message and
I think should not:
A bond in fail-over mode, either both or just one PHY connected.
VLANs configured on the bond device.
Two of the bond VLAN interfaces members of the same bridge, stp
enabled. An external bridge device (actually a fancy transparent
traffic shaper with a history of occasional seizure) connecting the
same two VLANs. A router on the higher-numbered (so less preferred by
STP) VLAN. So the nominal case is for STP to block forwarding, but if
the traffic shaper fails then the bridge will start sending traffic
direct to the router.
Now when the traffic shaper is forwarding traffic, the BPDUs sent out
the preferred port come back on the non-preferred port and force it
into blocking mode as desired. But the "received packet with own
address as source address" message is logged.
next prev parent reply other threads:[~2008-12-04 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 0:20 [Bridge] received packet with own address as source address Matthew Kent
2008-12-04 0:46 ` [Bridge] [Bonding-devel] " Jay Vosburgh
2008-12-04 4:18 ` richardvoigt [this message]
2008-12-04 18:46 ` Matthew Kent
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=2e59e6970812032018lcedac31o4de5cd71de718bd0@mail.gmail.com \
--to=richardvoigt@gmail.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=bridge@lists.linux-foundation.org \
--cc=fubar@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.