From: "Jouni Malinen" <jkm@devicescape.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kumar Gala <galak@kernel.crashing.org>,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: support for bridging ethernet and 802.11
Date: Thu, 10 May 2007 10:12:13 -0700 [thread overview]
Message-ID: <20070510171213.GD24712@devicescape.com> (raw)
In-Reply-To: <1178816781.3806.31.camel@johannes.berg>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Jouni Malinen" <jkm-r/za7OOdgF0ztatW0fm/fQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: Kumar Gala
<galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: support for bridging ethernet and 802.11
Date: Thu, 10 May 2007 10:12:13 -0700 [thread overview]
Message-ID: <20070510171213.GD24712@devicescape.com> (raw)
In-Reply-To: <1178816781.3806.31.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
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
next prev parent reply other threads:[~2007-05-10 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 16:18 support for bridging ethernet and 802.11 Kumar Gala
2007-05-10 17:06 ` Johannes Berg
2007-05-10 17:06 ` Johannes Berg
2007-05-10 17:12 ` Jouni Malinen [this message]
2007-05-10 17:12 ` Jouni Malinen
2007-05-10 17:19 ` Johannes Berg
2007-05-10 17:19 ` Johannes Berg
2007-05-10 17:25 ` Jouni Malinen
2007-05-10 17:25 ` Jouni Malinen
2007-05-10 18:25 ` Kumar Gala
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=20070510171213.GD24712@devicescape.com \
--to=jkm@devicescape.com \
--cc=galak@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.