From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Jouni Malinen <j@w1.fi>, Michael Wu <flamingice@sourmilk.net>
Subject: bridge packets option
Date: Wed, 29 Aug 2007 18:31:11 +0200 [thread overview]
Message-ID: <1188405071.1757.5.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Hey,
Looking through the receive code, the bridge_packets config option has
the effect of copying multicast traffic to the air right away and
passing frames to a station without having them go all the way through
the network stack.
I think there's a flaw with this: when you turn it off, nothing will
copy multicast frames to the network as expected by an AP, as far as I
can tell. Hence, I think that the bridge_packets must not be honoured
for multicast packets.
OTOH, for multicast, is it actually correct? Doesn't the AP need to
rewrite some fields?
As for unicast packets, what is the gain? There's obviously the loss
that netfilter won't see the packet which is generally very much frowned
upon. Is the performance benefit really that high?
I really need more devices for testing :/
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2007-08-30 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:31 Johannes Berg [this message]
2007-09-03 23:57 ` bridge packets option Jouni Malinen
2007-09-04 14:22 ` Johannes Berg
2007-09-05 2:38 ` Jouni Malinen
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=1188405071.1757.5.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--cc=j@w1.fi \
--cc=linux-wireless@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