From: Jouni Malinen <j@w1.fi>
To: Luis Carlos Cobo <luisca@cozybit.com>
Cc: linux-wireless@vger.kernel.org, shemminger@linux-foundation.org,
johannes@sipsolutions.net, bridge@linux-foundation.org
Subject: Re: [RFC] Do not activate promiscuous mode on wlan interfaces for bridging.
Date: Thu, 12 Jun 2008 08:33:24 +0300 [thread overview]
Message-ID: <20080612053323.GC4919@jm.kir.nu> (raw)
In-Reply-To: <1213232760.6645.24.camel@localhost>
On Wed, Jun 11, 2008 at 06:06:00PM -0700, Luis Carlos Cobo wrote:
> It seems that it is not really necessary to activate promiscuous mode when
> attaching a wlan interface to a bridge, and it causes unnecessary processing
> overhead to any wlan device.
Yes, agreed, IEEE 802.11 interfaces should not be changed into "monitor
mode" that receives all frames on the channel for normal bridging.
Whether the "promiscuous mode" is really a suitable name for this mode
is another question, though, since there are more ways to be
promiscuous in wireless networks than wired.. ;-)
> Please let me know what you think of this patch and whether it could interfere
> with any functionality.
Its desired goal sounds reasonable. I'm not sure whether
dev->ieee80211_ptr is guaranteed to be set with all drivers and all
configurations, though. Anyway, this should not break normal IEEE 802.11
bridging cases.
> + * 802.11 interfaces working as Access Points do not need to be set to
> + * promiscuous mode for bridging, as every frame is addressed to them.
> + *
> + * Bridging of 802.11 interfaces which are not in AP mode is not
> + * supported.
This is not strictly speaking correct. 4-address frame format (WDS) can
be used in other (non-AP) modes, too. Anyway, they do not require the
interface to be in promiscuous mode since addr1 of the frames is the
unicast address of the receiving device regardless of the original
destination address.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-06-12 5:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 1:06 [RFC] Do not activate promiscuous mode on wlan interfaces for bridging Luis Carlos Cobo
2008-06-12 5:33 ` Jouni Malinen [this message]
2008-06-12 18:10 ` Luis Carlos Cobo
2008-06-12 7:26 ` Johannes Berg
2008-06-12 18:19 ` Luis Carlos Cobo
2008-06-12 18:20 ` Johannes Berg
2008-06-12 18:34 ` Luis Carlos Cobo
2008-06-12 18:44 ` Johannes Berg
2008-06-12 18:53 ` Luis Carlos Cobo
2008-06-12 18:59 ` Johannes Berg
2008-06-12 19:01 ` Johannes Berg
[not found] <4850672a.1abd600a.56e0.ffffa374@mx.google.com>
2008-06-12 18:13 ` Stephen Hemminger
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=20080612053323.GC4919@jm.kir.nu \
--to=j@w1.fi \
--cc=bridge@linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@cozybit.com \
--cc=shemminger@linux-foundation.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).