netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, shemminger@linux-foundation.org,
	j@w1.fi, bridge@linux-foundation.org,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC] Do not activate promiscuous mode on wlan interfaces for bridging.
Date: Thu, 12 Jun 2008 11:19:53 -0700	[thread overview]
Message-ID: <1213294793.6615.16.camel@localhost> (raw)
In-Reply-To: <1213255570.3871.8.camel@johannes.berg>

On Thu, 2008-06-12 at 09:26 +0200, Johannes Berg wrote:
> All your description makes a lot of sense, but I don't see why altering
> the bridge code is necessary. In mac80211, we decided that the "promisc"
> bit only means to capture all frames in the current BSS (remember that
> in ethernet there is no way to capture frames from different LAN
> segments) and hence an AP would not behave differently in promisc mode
> at all since, by definition, it sees all BSS traffic.

You are right, within the BSS every frame is going to be addressed to
the AP anyway, so we should not receive more or less frames when
activating promiscuous mode.

When activating promiscuous mode in this device, it stops acknowledging
frames, and this impairs the association process. The other solution
would be to ignore the promiscuous mode commands (i.e. never send the
command to the device) for interfaces in AP mode. If this is the only
device showing this behavior, maybe that would be the best solution.

-- 
Luis Carlos Cobo Rus       GnuPG ID: 44019B60
cozybit Inc.



  parent reply	other threads:[~2008-06-12 18:19 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     ` [RFC] Do not activate promiscuous mode on wlan interfaces for bridging Luis Carlos Cobo
     [not found] ` <1213255570.3871.8.camel@johannes.berg>
2008-06-12 18:19   ` Luis Carlos Cobo [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-06-11 23:18 luisca
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=1213294793.6615.16.camel@localhost \
    --to=luisca@cozybit.com \
    --cc=bridge@linux-foundation.org \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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).