netdev - Re: support for bridging ethernet and 802.11

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: <1178817575.3806.36.camel@johannes.berg>
Date:	Thu, 10 May 2007 19:19:35 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Jouni Malinen <jkm@...icescape.com>
Cc:	Kumar Gala <galak@...nel.crashing.org>,
	netdev <netdev@...r.kernel.org>,
	linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: support for bridging ethernet and 802.11

On Thu, 2007-05-10 at 10:12 -0700, Jouni Malinen wrote:

> IEEE 802.11 allows only the own MAC address to be used as the source
> address (addr2) when operating as a non-AP STA in BSS (client in Managed
> mode). In other words, layer 2 bridging does not work properly. AP mode
> and WDS links can be used for bridging without problems, but this will
> of course require the driver to support these.

Ah forgot about that, I had only thought about AP/wired bridging. How
would the prism driver actually do bridging in STA mode though?

johannes

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