From: Stephen Hemminger <stephen@networkplumber.org>
To: Seweryn Niemiec <ser@man.szczecin.pl>
Cc: bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] [PROBLEM] mac address learned on wrong port
Date: Wed, 27 Apr 2016 12:37:26 -0700 [thread overview]
Message-ID: <20160427123726.65ce2ecb@samsung9> (raw)
In-Reply-To: <5720BBCD.2070009@man.szczecin.pl>
On Wed, 27 Apr 2016 15:17:01 +0200
Seweryn Niemiec <ser@man.szczecin.pl> wrote:
> On 26.04.2016 18:49, Stephen Hemminger wrote:
> > This usualy happens when you either have a loop or packet leaks in from other port.
>
> Yeah, it looks like a loop, but p2p1 is connected to a production network with
> running MSTP, so I was sure there is no loop, but I have double checked it today
> and I'm still sure there is no loop in the net outside of the server. To make it
> super sure I have connected p2p1 to a dead end port (vlan with this one port
> only) on a switch and the effect was the same - container's mac is learned on p2p1.
>
But you are not running Spanning Tree on your bridge.
next prev parent reply other threads:[~2016-04-27 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 13:38 [Bridge] [PROBLEM] mac address learned on wrong port Seweryn Niemiec
2016-04-26 16:49 ` Stephen Hemminger
2016-04-27 13:17 ` Seweryn Niemiec
2016-04-27 19:37 ` Stephen Hemminger [this message]
2016-04-29 12:03 ` Seweryn Niemiec
2016-05-09 11:12 ` Seweryn Niemiec
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=20160427123726.65ce2ecb@samsung9 \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=ser@man.szczecin.pl \
/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