From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
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 21:32:08 +0200 [thread overview]
Message-ID: <4BF2EB38.4060408@free.fr> (raw)
In-Reply-To: <F24C979D1AFD4E4292B911441CBA242407FCC1@2putt.int.lantronix.com>
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
Nicolas.
> Then I try to run udhcpc (DHCP client) on the bridge hoping to get DHCP
> from the AP/router:
>
> # udhcpc -ibr0 -b
> udhcpc (v1.15.2) started
> Sending discover...
> Sending discover...
> Sending discover...
> No lease, forking to background
>
> What I'd like to inquire is that is WDS support in the firmware/hardware
> of the radio required to bridge eth0 and wlan0?
> Any other tips to get the above interfaces to successfully bridge
> together would be great.
>
> Thanks,
> Umar
>
> **********************************************************************
> This e-mail is the property of Lantronix. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited.
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
next prev parent reply other threads:[~2010-05-18 19:32 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 [this message]
2010-05-18 23:38 ` Umar Qureshey
2010-05-18 23:51 ` Stephen Hemminger
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=4BF2EB38.4060408@free.fr \
--to=nicolas.2p.debian@free.fr \
--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.