[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f5ec9f1-800a-2bc4-2f41-9d803343bb22@fami-braun.de>
Date: Mon, 9 Jan 2017 12:44:19 +0100
From: "M. Braun" <michael-dev@...i-braun.de>
To: Johannes Berg <johannes@...solutions.net>,
Linus Lüssing <linus.luessing@...3.blue>
Cc: Felix Fietkau <nbd@....name>, netdev@...r.kernel.org,
"David S . Miller" <davem@...emloft.net>,
Stephen Hemminger <stephen@...workplumber.org>,
bridge@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH net-next] bridge: multicast to unicast
Am 09.01.2017 um 09:08 schrieb Johannes Berg:
> Does it make sense to implement the two in separate layers though?
>
> Clearly, this part needs to be implemented in the bridge layer due to
> the snooping knowledge, but the code is very similar to what mac80211
> has now.
Does the bridge always know about all stations connected?
That is bridge fdb entries (need to) expire so the bridge might "forget"
a still-connected station not sending but only consuming broadcast traffic.
E.g. there is a television broadcast station here that receives a video
stream (via wifi, udp packets) and then airs it (dvb-t) but (on its own)
would not send any data packet on wifi (static ip, etc.).
An other reason to implement this in mac80211 initially was that
mac80211 could encapsulate broacast/multicast ethernet packtes in
unicast A-MSDU packets in a way, so that the receiver would still see
process ethernet packets (after conversion) but have unicast wifi
frames. This cannot be done in bridge easily but one might want to add
this later to mac80211.
Michael
Powered by blists - more mailing lists