From: Maxime Bizon <mbizon@freebox.fr>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH] bridge: mark packets sent to any local mac address as PACKET_HOST
Date: Thu, 26 Jun 2014 13:15:52 +0200 [thread overview]
Message-ID: <1403781352.52578.103.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20140625161335.11598f09@haswell>
On Wed, 2014-06-25 at 16:13 -0700, Stephen Hemminger wrote:
> > The bridge code only set PACKET_HOST on packets sent to the bridge mac
> > address, packets sent to other local mac addresses are sent to upper
> > layers, but ignored because they are marked as PACKET_OTHERHOST.
> >
> > Signed-off-by: Maxime Bizon <mbizon@freebox.fr>
>
> What are you trying to do? Bridge device itself only has one MAC address.
> Are you trying to run macvlan on top of bridge?
> We only respond to ARP with bridge's MAC address.
host1 uses a bridge with two interfaces: ethernet and wireless (AP mode
using hostapd)
for some reasons, hostapd kept adding and removing the interface from
the bridge, triggering a mac address of the bridge change each time (I
did not notice that).
Another host had a static arp entry for host1, using the ethernet mac
address, so its packets to host1 were randomly trashed depending on the
current mac of the bridge.
I have since fixed this by setting a static mac address on the bridge to
prevent dynamic change, but I thought this patch would prevent other
people from having the same bug in the future.
What do you think ?
--
Maxime
next prev parent reply other threads:[~2014-06-26 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 14:33 [PATCH] bridge: mark packets sent to any local mac address as PACKET_HOST Maxime Bizon
2014-06-25 23:09 ` David Miller
2014-06-25 23:13 ` Stephen Hemminger
2014-06-26 11:15 ` Maxime Bizon [this message]
2014-06-26 20:35 ` David Miller
2014-06-26 21:19 ` Maxime Bizon
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=1403781352.52578.103.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--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 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).