netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Johannes Wienke <jwienke@techfak.uni-bielefeld.de>
Cc: netdev@vger.kernel.org
Subject: Re: Bridge connectivity interruptions while devices join or leave the bridge
Date: Wed, 19 Sep 2018 13:07:55 +0300	[thread overview]
Message-ID: <20180919100755.GA26424@splinter> (raw)
In-Reply-To: <7e7e9b1d-b6b5-b72f-efe6-52d700ad1ffc@techfak.uni-bielefeld.de>

On Wed, Sep 19, 2018 at 11:10:22AM +0200, Johannes Wienke wrote:
> Can someone explain what is happening here and why adding and removing
> devices to a bridge results in the connectivity issues? How to avoid
> this behavior? I'd be glad for any hint on that.

The MAC address of the bridge ('brtest' in your example) is inherited
from the bridge port with the "smallest" MAC address. Thus, when you
generate veth devices with random MACs and enslave them to the bridge,
you sometimes change the bridge's MAC address as well. And since the
bridge is the default gateway sometimes packets are sent to the wrong
MAC address.

You can avoid randomly changing the bridge's MAC by setting it
explicitly:
# ip link set dev brtest address <some_mac>

  reply	other threads:[~2018-09-19 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  9:10 Bridge connectivity interruptions while devices join or leave the bridge Johannes Wienke
2018-09-19 10:07 ` Ido Schimmel [this message]
2018-09-19 11:00   ` Johannes Wienke
2018-09-19 16:45     ` Ido Schimmel
2018-09-19 17:03       ` Stephen Hemminger
2018-09-19 20:57         ` Johannes Wienke

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=20180919100755.GA26424@splinter \
    --to=idosch@idosch.org \
    --cc=jwienke@techfak.uni-bielefeld.de \
    --cc=netdev@vger.kernel.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).