From: Brandon Carpenter <brandon.carpenter@cypherpath.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: [Bridge] Sending 802.1Q packets using AF_PACKET socket on filtered bridge forwards with wrong MAC addresses
Date: Tue, 28 Nov 2017 09:21:17 -0800 [thread overview]
Message-ID: <1511889677.1204.0@smtp.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
While attempting to send ARP DAD packets on a bridge device, I noticed
that hosts attached to the bridge ports were not responding. After
digging in with tcpdump/wireshark, I noticed that the MAC addresses of
the packets (the first 12 bytes of the Ethernet frame) were wrong and
were an exact duplicate of the following 12 bytes (bytes 13-24), but
only on slave bridge ports. The bridge device itself had the correct
addresses. Here is an example setup:
> # ip link add br0 type bridge vlan_filtering 1
--
Brandon Carpenter | Software Engineer
Cypherpath, Inc.
400 Columbia Point Drive Ste 101 | Richland, Washington USA
Office: (650) 713-3060
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain proprietary,
confidential or privileged information or otherwise be protected by law.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please notify the sender and destroy
all copies and the original message.
[-- Attachment #2: Type: text/html, Size: 1309 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Brandon Carpenter <brandon.carpenter@cypherpath.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Sending 802.1Q packets using AF_PACKET socket on filtered bridge forwards with wrong MAC addresses
Date: Tue, 28 Nov 2017 09:21:17 -0800 [thread overview]
Message-ID: <1511889677.1204.0@smtp.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
While attempting to send ARP DAD packets on a bridge device, I noticed
that hosts attached to the bridge ports were not responding. After
digging in with tcpdump/wireshark, I noticed that the MAC addresses of
the packets (the first 12 bytes of the Ethernet frame) were wrong and
were an exact duplicate of the following 12 bytes (bytes 13-24), but
only on slave bridge ports. The bridge device itself had the correct
addresses. Here is an example setup:
> # ip link add br0 type bridge vlan_filtering 1
--
Brandon Carpenter | Software Engineer
Cypherpath, Inc.
400 Columbia Point Drive Ste 101 | Richland, Washington USA
Office: (650) 713-3060
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain proprietary,
confidential or privileged information or otherwise be protected by law.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please notify the sender and destroy
all copies and the original message.
[-- Attachment #2: Type: text/html, Size: 1309 bytes --]
next reply other threads:[~2017-11-28 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 17:21 Brandon Carpenter [this message]
2017-11-28 17:21 ` Sending 802.1Q packets using AF_PACKET socket on filtered bridge forwards with wrong MAC addresses Brandon Carpenter
-- strict thread matches above, loose matches on Subject: below --
2017-11-28 19:11 [Bridge] " Brandon Carpenter
2017-11-28 23:37 ` Brandon Carpenter
2017-11-29 22:01 ` Brandon Carpenter
2017-12-06 4:44 ` Toshiaki Makita
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=1511889677.1204.0@smtp.gmail.com \
--to=brandon.carpenter@cypherpath.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.