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 for Android: free password hash cracker in your pocket

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

Message-ID: <20070510171213.GD24712@devicescape.com>
Date:	Thu, 10 May 2007 10:12:13 -0700
From:	"Jouni Malinen" <jkm@...icescape.com>
To:	Johannes Berg <johannes@...solutions.net>
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, May 10, 2007 at 07:06:21PM +0200, Johannes Berg wrote:

> On Thu, 2007-05-10 at 11:18 -0500, Kumar Gala wrote:
> > I'm wondering how to tell if a given driver/device in the kernel  
> > supports the ability to bridge between ethernet and 802.11.  From  
> > searching the web it looks like only the prism driver/device supports  
> > this.

> Normally wireless drivers do 802.3 framing as the 802.11 standard more
> or less requires, so it should "just work". Am I missing something?

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.

-- 
Jouni Malinen                                            PGP id EFC895FA
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html