From: Jamal Hadi Salim <jhs@mojatatu•com>
To: vyasevic@redhat•com, davem@davemloft•net, stephen@networkplumber•org
Cc: netdev@vger•kernel.org, sfeldma@cumulusnetworks•com,
john.r.fastabend@intel•com, roopa@cumulusnetworks•com
Subject: Re: [net-next PATCH 2/2] bridge netlink dump interface at par with brctl Actually better than brctl showmacs because we can filter by bridge port in the kernel
Date: Mon, 02 Jun 2014 18:17:50 -0400 [thread overview]
Message-ID: <538CF80E.5010009@mojatatu.com> (raw)
In-Reply-To: <538C9988.3040902@redhat.com>
On 06/02/14 11:34, Vlad Yasevich wrote:
>
> I think that after this code, if you set a bridge mac address thus
> causing an fdb like:
> <mac> dev br0 vlan 0 master permanent (old notation)
>
> you will not show it if you set the br_idx with
> # bridge fdb show br br0
>
>
> I looks like the only way to show such fdb is not set any filters at all
> since if you set a port filter, you will not see it either as it will be
> filtered out in bridge code.
>
I thought the comment which says "selfie" would take care of that; i.e
the default dump would do it.
If you give me an example of setting such an entry I will try it out
and see if it works.
cheers,
jamal
next prev parent reply other threads:[~2014-06-02 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 11:56 [net-next PATCH 1/2] bridge fdb dumping takes a filter device Dumping a bridge fdb dumps every fdb entry held. With this change we are going to filter on selected bridge port Jamal Hadi Salim
2014-06-01 11:56 ` [net-next PATCH 2/2] bridge netlink dump interface at par with brctl Actually better than brctl showmacs because we can filter by bridge port in the kernel Jamal Hadi Salim
2014-06-01 12:16 ` Jamal Hadi Salim
2014-06-01 12:24 ` Jamal Hadi Salim
2014-06-02 15:34 ` Vlad Yasevich
2014-06-02 22:17 ` Jamal Hadi Salim [this message]
2014-06-05 7:15 ` [net-next PATCH 1/2] bridge fdb dumping takes a filter device Dumping a bridge fdb dumps every fdb entry held. With this change we are going to filter on selected bridge port David Miller
2014-06-07 12:41 ` Jamal Hadi Salim
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=538CF80E.5010009@mojatatu.com \
--to=jhs@mojatatu$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=john.r.fastabend@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=sfeldma@cumulusnetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=vyasevic@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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