netdev - Re: [RFC] Do not activate promiscuous mode on wlan interfaces for bridging.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1213294852.3730.31.camel@johannes.berg>
Date:	Thu, 12 Jun 2008 20:20:52 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Luis Carlos Cobo <luisca@...ybit.com>
Cc:	linux-wireless@...r.kernel.org, shemminger@...ux-foundation.org,
	j@...fi, bridge@...ux-foundation.org,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [RFC] Do not activate promiscuous mode on wlan interfaces for
	bridging.


> 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.

Is this a mac80211 driver? When are you activating promisc?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)