From: Stephen Hemminger <stephen@networkplumber.org>
To: Mathieu Rohon <mathieu.rohon@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: bridge-utils : bridge fdb replace undocumented
Date: Thu, 8 Jan 2015 10:22:02 -0800 [thread overview]
Message-ID: <20150108102202.4fb6dd99@urahara> (raw)
In-Reply-To: <CAAfiWQqCv9=nFRNuxHPb+hRVbNywiEN_bQJHaxXc29hka0iUaw@mail.gmail.com>
On Thu, 8 Jan 2015 13:52:01 +0100
Mathieu Rohon <mathieu.rohon@gmail.com> wrote:
> Hi,
>
> the command :
> #bridge fdb replace
>
> can be useful to replace a learned Mac address by a static one. We'd
> like to use this command to solve an openstack bug :
> https://bugs.launchpad.net/neutron/+bug/1367999
>
> However it is not documented in the manpage of bridge-utilis version 1.5.9.
>
> Also, I don't know what is the minimum version to have this features.
>
> regards,
> Mathieu
Bridge command is part of iproute2 not bridge-utils.
prev parent reply other threads:[~2015-01-08 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 12:52 bridge-utils : bridge fdb replace undocumented Mathieu Rohon
2015-01-08 18:22 ` Stephen Hemminger [this message]
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=20150108102202.4fb6dd99@urahara \
--to=stephen@networkplumber.org \
--cc=mathieu.rohon@gmail.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 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).