From: Ben Greear <greearb@candelatech.com>
To: Sam Leffler <sleffler@google.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Bridging wired to STA interfaces.
Date: Wed, 03 Aug 2011 17:44:02 -0700 [thread overview]
Message-ID: <4E39EB52.1090401@candelatech.com> (raw)
In-Reply-To: <CA+yqC4YvAMLaao4dy2aXM7H5zPXySk4eAUZ2KSM4QnP+kQqF-A@mail.gmail.com>
On 08/03/2011 03:37 PM, Sam Leffler wrote:
> On Tue, Aug 2, 2011 at 10:33 PM, Ben Greear<greearb@candelatech.com> wrote:
>> We have some interest in being able to bridge wired systems to
>> (virtual) STA interfaces, primarily for using third-party
>> traffic generation tools over virtual stations.
>>
>> I was thinking of writing a sta-bridge module that mapped
>> incoming packets on a wired interface to a STA with MAC
>> that matched the source MAC of the packet. All packets
>> received on the STA would be forwarded un-modified out
>> the wired port.
>>
>> I think this would allow someone to create a STA interface
>> with MAC matching a PC connected to the wired port and effectively
>> have it be a transparent bridge between STA and PC.
>>
>> Has anyone attempted something like this before?
>>
>> Any interest in having this feature in the upstream kernel?
>
> You've just described what's done in several products and it is indeed
> useful. The main issue is supporting it can incur overhead so you may
> want to make it a compile-time option.
I got some basic functionality working today with some
user-space bridging code I've already written for other purposes...
Can you think of any reason (beyond a bit of performance) that
this should be in the kernel?
My target hardware is fast enough that copying through user-space
at moderate (ie, fast as STA can go) speeds isn't too big of a deal, but
if someone wanted to run this on weak hardware, that might be reason
enough... It might also make it easier to filter our management frames
(EAPOL, etc), but we should be able to do that easily enough in user-space
with a small bit of work.
Thanks,
Ben
>
> -Sam
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-08-04 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 5:33 Bridging wired to STA interfaces Ben Greear
2011-08-03 9:16 ` Adrian Chadd
2011-08-03 16:37 ` Ben Greear
2011-08-03 22:37 ` Sam Leffler
2011-08-04 0:44 ` Ben Greear [this message]
2011-08-09 18:11 ` Sam Leffler
2011-08-11 7:14 ` Ben Greear
2011-08-11 8:48 ` Adrian Chadd
2011-08-25 18:17 ` Ben Greear
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=4E39EB52.1090401@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sleffler@google.com \
/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;
as well as URLs for NNTP newsgroup(s).