From: David Ahern <dsahern@gmail.com>
To: Lawrence Kreeger <lkreeger@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: "wrong" ifindex on received VLAN tagged packet?
Date: Mon, 12 Mar 2018 13:26:15 -0700 [thread overview]
Message-ID: <0448b3dd-d60f-b5f2-f833-fa63476f4a80@gmail.com> (raw)
In-Reply-To: <CAOfa6T1QU+ukwTvujxN8xdSGjnEz=dXzMmGp1TQQGxaZU7ESaQ@mail.gmail.com>
On 3/6/18 5:27 PM, Lawrence Kreeger wrote:
> Using ETH_P_ALL instead of ETH_P_802_2, is causing mstpd to get 3
> copies of the same BPDU. One from eth0, one from eth0.100, and
> another from vlan100 (the bridge).
> mstpd will drop the one from vlan100, but since there is also an
> instance of spanning tree running on the native VLAN, there is now no
> way to differentiate BPDUs coming in
> tagged vs untagged because they all show up with eth0. So, there
> isn't some kernel knob to get the BPDUs to only come from eth0.100?
not that I am aware of. You could bind your socket or program to
eth0.100, but I suspect you actually have more than the one vlan
interface coming into the bridge that you want to snoop.
prev parent reply other threads:[~2018-03-12 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 22:02 "wrong" ifindex on received VLAN tagged packet? Lawrence Kreeger
2018-03-07 0:43 ` David Ahern
2018-03-07 1:27 ` Lawrence Kreeger
2018-03-12 20:26 ` David Ahern [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=0448b3dd-d60f-b5f2-f833-fa63476f4a80@gmail.com \
--to=dsahern@gmail.com \
--cc=lkreeger@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).