All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Umar Qureshey <umar.qureshey@lantronix.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Hardware requirements for bridging wired+wireless together
Date: Tue, 18 May 2010 16:51:12 -0700	[thread overview]
Message-ID: <20100518165112.18669700@nehalam> (raw)
In-Reply-To: <F24C979D1AFD4E4292B911441CBA242407FCC7@2putt.int.lantronix.com>

On Tue, 18 May 2010 16:38:54 -0700
"Umar Qureshey" <umar.qureshey@lantronix.com> wrote:

> -----Original Message-----
> From: Nicolas de Pesloüan [mailto:nicolas.2p.debian@free.fr] 
> Sent: Tuesday, May 18, 2010 12:32 PM
> To: Umar Qureshey
> Cc: bridge@lists.linux-foundation.org
> Subject: Re: [Bridge] Hardware requirements for bridging wired+wireless together
> 
> Umar Qureshey wrote:
> > Hi,
> >
> > I have been trolling the 'net as well as the archives of this list for
> > quite a while now.
> >
> > I am still unclear on the requirements for getting an Ethernet and
> > Wireless interface to bridge together.
> >
> > Currently, I am working with an esoteric radio that only supports Ad-Hoc
> > and Managed modes.  There seemingly is not support for WDS (Wireless
> > Distribution System) on this radio.
> >
> > I have been trying to bridge my eth0 and wlan0 but it doesn't seem to
> > work.  Currently, my commands to get the bridge up are:
> >
> > ifconfig eth0 0.0.0.0
> > ifconfig wlan0 0.0.0.0
> > brctl addbr br0
> > brctl addif br0 eth0
> > brctl setfd br0 1           #BusyBox version of brctl doesn't take 0 as
> > a time parameter so I change it to 1 (sec)
> > ifconfig br0 up
> > wpa_supplicant -Dwext -iwlan0 -bbr0 -c/root/wpa_supplicant.conf
> 
> I think you forgot to add wlan0 to the bridge:
> 
> brctl addif br0 wlan0
> 

I believe bridging in station mode won't work (usually).
Recent kernels even reject the attempt.

There are exceptions with some devices and if the stack supports WDS
(which Linux wireless doesn't yet).

There are some cases like VMware that appear to do MAC level NAT
(ie replace Ethernet address), but the regular kernel doesn't support that.

  reply	other threads:[~2010-05-18 23:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 20:17 [Bridge] Hardware requirements for bridging wired+wireless together Umar Qureshey
2010-05-18 19:32 ` Nicolas de Pesloüan
2010-05-18 23:38   ` Umar Qureshey
2010-05-18 23:51     ` Stephen Hemminger [this message]
2010-05-19 17:15       ` Umar Qureshey
2010-05-19 19:20         ` John W. Linville
2010-05-19 20:59           ` Simon Barber
2010-05-19 21:08             ` Umar Qureshey
2010-05-19 22:55               ` Simon Barber
2010-05-19 21:01           ` Umar Qureshey
2010-05-19 23:02             ` Simon Barber

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=20100518165112.18669700@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=umar.qureshey@lantronix.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 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.