From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: bridge packets option
Date: Tue, 4 Sep 2007 19:38:24 -0700 [thread overview]
Message-ID: <20070905023824.GE5273@jm.kir.nu> (raw)
In-Reply-To: <1188915742.9942.33.camel@johannes.berg>
On Tue, Sep 04, 2007 at 04:22:22PM +0200, Johannes Berg wrote:
> On Mon, 2007-09-03 at 16:57 -0700, Jouni Malinen wrote:
> > Kernel
> > bridging code does not (or at least did not the last time I looked)
> > allow packets to be bridged back to the same interface which would be
> > needed for the case of two wireless stations which are associated to the
> > same AP sending packets to each other.
>
> I was thinking more of routing in the unicast case, if a packet comes in
> you'd have to route it back to wireless if the destination is there.
> Isn't that possible?
Well, it may be possible, but that would not be the way IEEE 802.11
access points normally work. AP is a layer 2 bridge and it should bridge
the packets regardless of what ethertype is used. There is no need for
it to keep up ARP tables for the associated stations to figure out where
to route packets. Furthermore, I would rather not see ICMP redirects
showing up on the wireless interface because IP routing needed to send
the packet back to the same interface. I would assume that this can be
disabled, but anyway, layer 2 bridge is the location that would be much
close to what AP does between two associated wireless stations.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2007-09-05 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:31 bridge packets option Johannes Berg
2007-09-03 23:57 ` Jouni Malinen
2007-09-04 14:22 ` Johannes Berg
2007-09-05 2:38 ` Jouni Malinen [this message]
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=20070905023824.GE5273@jm.kir.nu \
--to=j@w1.fi \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox