netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
	"vyasevic@redhat.com" <vyasevic@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Malek, Patryk" <patryk.malek@intel.com>
Subject: RE: removing bridge in vlan_filtering mode requests delete of attached ports main MAC address
Date: Thu, 26 Oct 2017 20:33:07 +0000	[thread overview]
Message-ID: <02874ECE860811409154E81DA85FBB5882AD0E46@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <02874ECE860811409154E81DA85FBB5882AD0E1A@ORSMSX115.amr.corp.intel.com>

> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of Keller, Jacob E
> Sent: Thursday, October 26, 2017 1:27 PM
> To: vyasevic@redhat.com; netdev@vger.kernel.org
> Cc: Malek, Patryk <patryk.malek@intel.com>
> Subject: RE: removing bridge in vlan_filtering mode requests delete of attached
> ports main MAC address
> 
> > -----Original Message-----
> > From: Vlad Yasevich [mailto:vyasevic@redhat.com]
> > Sent: Thursday, October 26, 2017 3:22 AM
> > To: Keller, Jacob E <jacob.e.keller@intel.com>; netdev@vger.kernel.org
> > Cc: Malek, Patryk <patryk.malek@intel.com>
> > Subject: Re: removing bridge in vlan_filtering mode requests delete of attached
> > ports main MAC address
> >
> > Hi Jake
> >
> > I think adding a !fdb->local should work.  local fdb contain the address of
> assigned
> > to
> > the ports of the bridge and those shouldn't be directly removed.
> >
> > If that works,  that looks like the right solution.
> >
> > -vlad
> >
> 
> So this does prevent us from removing the port's address. However, if I add two
> devices to the bridge, then after removing the bridge, each device now keeps
> both permanent addresses in their list, which isn't what we want is it?
> 
> Do we even want to assign the local fdb addresses to every port?
> 
> Obviously, I don't fully understand this code, so I think I'm missing something
> here.
> 
> Regards,
> Jake
> 

Ok, I tried this again, and it didn't end up crossing the local device addresses to each port. I'm not sure how that happened the first time yet, so maybe it is correct to skip removing local addresses... but if we skip removing them, wouldn't we want to skip adding them too?

Thanks,
Jake

  reply	other threads:[~2017-10-26 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 18:06 removing bridge in vlan_filtering mode requests delete of attached ports main MAC address Keller, Jacob E
2017-10-26 10:21 ` Vlad Yasevich
2017-10-26 19:56   ` Keller, Jacob E
2017-10-26 20:27   ` Keller, Jacob E
2017-10-26 20:33     ` Keller, Jacob E [this message]
2017-10-27  0:21       ` Keller, Jacob E
2017-11-01  0:10       ` Keller, Jacob E
2017-11-01  0:58         ` Toshiaki Makita
2017-11-01 22:25           ` Keller, Jacob E
2017-11-02  9:22             ` Toshiaki Makita
2017-11-02 22:10               ` Keller, Jacob E
  -- strict thread matches above, loose matches on Subject: below --
2017-10-20 17:23 Keller, Jacob E

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=02874ECE860811409154E81DA85FBB5882AD0E46@ORSMSX115.amr.corp.intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=patryk.malek@intel.com \
    --cc=vyasevic@redhat.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 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).