All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filtering in layer 2 [but is not a bridge]
Date: Sat, 13 Jan 2007 03:54:03 +0000	[thread overview]
Message-ID: <45A857DB.2030208@riverviewtech.net> (raw)
In-Reply-To: <200701091052.37604.luciano@lugmen.org.ar>

On 01/11/07 06:01, Zoilo Gomez wrote:
> Isn't an AP just a bridge with a wireless interface?

In a sense, yes.  However the 802.11 wireless side of the bridge is a 
very complex physical layer, (IMHO) more so than 802.3 ethernet.

Host AP is probably listening to requests at the physical tranceiver 
level.  If the Host AP is operating in an AP mode (wouldn't it be?) it 
will have to be involved in passing the traffic from one 802.11 client 
to another.  This is really a form of bridging on the physical layer, 
not layer 2 in the kernel.  Thus EB / IP Tables will not help here.

I have not (yet) personally worked with Host AP, though I plan to.  As 
such, I'm not sure if it includes functionality to filter the traffic 
that it sees.

I wonder if it would be a possibility to (theoretically) move / extend 
the functionality of Host AP such that each associated wireless client 
would (logically / theoretically) appear as a separate interface to a 
custom bridge that could then be presented / controlled via EBTables. 
However, this is quite likely exceeding the 802.11 specification in such 
a way that it would really no longer be 802.11.

Something to keep in mind is that in Infrastructure wireless mode, one 
wireless client has to talk to the AP and have the AP talk to another 
wireless client on it's behalf.  I believe this is the ""bridging that 
the OP is referring to.  Note, I use the term bridging loosely here.

On a side note, how well do you like Host AP?



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-01-13  3:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 13:52 [LARTC] filtering in layer 2 [but is not a bridge] Luciano Ruete
2007-01-09 14:00 ` Zoilo Gomez
2007-01-11 11:56 ` Luciano Ruete
2007-01-11 12:01 ` Zoilo Gomez
2007-01-13  3:54 ` Grant Taylor [this message]
2007-01-13 13:42 ` Zoilo Gomez

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=45A857DB.2030208@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@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.