From: Luis Carlos Cobo <luisca-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
shemminger-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org,
bridge-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
Linux Netdev List
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] Do not activate promiscuous mode on wlan interfaces for bridging.
Date: Thu, 12 Jun 2008 11:10:50 -0700 [thread overview]
Message-ID: <1213294251.6615.5.camel@localhost> (raw)
In-Reply-To: <20080612053323.GC4919-mgr6C1c9aYeHXe+LvDLADg@public.gmane.org>
Thank you very much for your comments Jouni.
On Thu, 2008-06-12 at 08:33 +0300, Jouni Malinen wrote:
> 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.. ;-)
Indeed, but the bridge sets promiscuous mode, not monitor. This means
that the device will receive every frame within its configured BSS
whether it is addressed to it or not. For an AP actually this mode
should make no difference, since every frame not coming from the AP is
addressed to the AP.
> 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.
Agreed, will reword that.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2008-06-12 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1213232760.6645.24.camel@localhost>
[not found] ` <20080612053323.GC4919@jm.kir.nu>
[not found] ` <20080612053323.GC4919-mgr6C1c9aYeHXe+LvDLADg@public.gmane.org>
2008-06-12 18:10 ` Luis Carlos Cobo [this message]
[not found] ` <1213255570.3871.8.camel@johannes.berg>
2008-06-12 18:19 ` [RFC] Do not activate promiscuous mode on wlan interfaces for bridging Luis Carlos Cobo
2008-06-12 18:20 ` Johannes Berg
[not found] ` <1213294852.3730.31.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-12 18:34 ` Luis Carlos Cobo
2008-06-12 18:44 ` Johannes Berg
[not found] ` <1213296250.3730.33.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-12 18:53 ` Luis Carlos Cobo
2008-06-12 18:59 ` Johannes Berg
2008-06-12 19:01 ` Johannes Berg
2008-06-11 23:18 luisca
2008-06-12 18:13 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 23:18 luisca
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=1213294251.6615.5.camel@localhost \
--to=luisca-w/olz77bvjtbdgjk7y7tuq@public.gmane.org \
--cc=bridge-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=j@w1.fi \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shemminger-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).