linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Bridging wired to STA interfaces.
Date: Wed, 03 Aug 2011 09:37:42 -0700	[thread overview]
Message-ID: <4E397956.4070300@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmon2Xwv3VqDhH9EouGiYgr0wfoEh3_41D4EscmForRDgaA@mail.gmail.com>

On 08/03/2011 02:16 AM, Adrian Chadd wrote:
> How do you propose handling the case where people will hook up>1 device?
> Print out a very loud warning? :-)

I think you'd end up mapping the MAC of the PC to the STA, 1-to-1 mapping,
and possibly re-writing the src MAC when coming from the PC to the STA,
and dest MAC when coming from STA to PC.

Users wanting more than one PC could use a different virtual STA.

> I did something like this a while ago for a company and their first
> request was exactly that - "Customer X now wants two devices in a
> vehicle hooked up to the wireless, it doesn't work, what do we do?"

Did it at least work for 1-to-1 mapping OK?  Did you re-write MACs?

Thanks,
Ben

>
>
> Adrian
>
>
> On 3 August 2011 13:33, 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?
>>
>> Thanks,
>> Ben
>>
>> --
>> Ben Greear<greearb@candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>> --
>> 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
>>
> --
> 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

  reply	other threads:[~2011-08-03 16:37 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 [this message]
2011-08-03 22:37 ` Sam Leffler
2011-08-04  0:44   ` Ben Greear
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=4E397956.4070300@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --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;
as well as URLs for NNTP newsgroup(s).