All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Warkentin <andreiw@motorola.com>
To: netdev@vger.kernel.org
Subject: Fix bridge MAC change notification.
Date: Thu,  4 Aug 2011 20:55:48 -0500	[thread overview]
Message-ID: <1312509349-23363-1-git-send-email-andreiw@motorola.com> (raw)

This is my first time on netdev. I am writing about the ensuring
that upper network layers are aware of bridge MAC changes due
to re-configuration or port addition/removal.

It seems this topic has cropped up before, with one patch by 
Stephen Hemminger already in 3.0, and a fix for it (sent 7/22)
(http://marc.info/?l=linux-netdev&m=131135705613958&w=2) pending.

The existing patches don't cover the br_del_if case, the case of 
a changing MAC address on a port associated with the bridge, and
the case of manually setting the MAC address, which the following
patch remedies.

Table of Contents:
[PATCH] Bridge: Always send NETDEV_CHANGEADDR up on br MAC change.

Thank you,
A


             reply	other threads:[~2011-08-05 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  1:55 Andrei Warkentin [this message]
2011-08-05  1:55 ` [PATCH] Bridge: Always send NETDEV_CHANGEADDR up on br MAC change Andrei Warkentin
2011-08-05  2:11 ` Always send NETDEV_CHANGEADDR up Andrei Warkentin
2011-08-05  2:11 ` [PATCHv2] Bridge: Always send NETDEV_CHANGEADDR up on br MAC change Andrei Warkentin
2011-08-05  2:17 ` Always send NETDEV_CHANGEADDR up Andrei Warkentin
2011-08-05  2:17 ` [PATCHv3] Bridge: Always send NETDEV_CHANGEADDR up on br MAC change Andrei Warkentin
2011-08-05  4:36   ` Stephen Hemminger
2011-08-05  6:13     ` Andrei Warkentin
2011-08-05 21:04       ` Always send NETDEV_CHANGEADDR up Andrei Warkentin
2011-08-05 21:04       ` [PATCHv4] Bridge: Always send NETDEV_CHANGEADDR up on br MAC change Andrei Warkentin
2011-08-08 20:12         ` Stephen Hemminger
2011-08-09  5:12           ` Andrei Warkentin
2011-08-10  4:45           ` David Miller

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=1312509349-23363-1-git-send-email-andreiw@motorola.com \
    --to=andreiw@motorola.com \
    --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 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.