Ethernet Bridge development
 help / color / mirror / Atom feed
From: Mauro Condarelli <mc5686@mclink.it>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Transparent wired/wirless bridge: is it possible?
Date: Sat, 30 Oct 2010 18:20:57 +0200	[thread overview]
Message-ID: <4CCC45E9.7070801@mclink.it> (raw)
In-Reply-To: <AANLkTi=xHJyMbMqssrSaPabOp9mddGVv15SboU33h10G@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

On 26/10/2010 14.36, Ryan Whelan wrote:
> Have you looked at hostapd (http://hostap.epitest.fi/hostapd/)?
Sorry,
I was not clear enough.

I have the wireless card up-and-running in ap-mode using hostapd.
I *can* connect a laptop to the wireless Access Point.
I also know how to setup a masquerading router on the linux machine to 
share the landline connection (e.g.: using firestarter).
This would create a second net for wireless with double natting.
I would like to avoid this and I'm looking for a "bridge" configuration 
so that all machines (wireless & wired) can share the same subnet 
(192.68.1.0/24).

I tried something like:
=====================
auto lo
iface lo inet loopback

auto wlan2
iface wlan2 inet manual
     up /usr/sbin/service hostapd start
     up /sbin/ifconfig wlan2 up
     down /sbin/ifconfig wlan2 down
     down /usr/sbin/service hostapd stop

auto eth2
iface eth2 inet manual
     up /sbin/ifconfig eth2 up
     down /sbin/ifconfig eth2 down

auto br0
iface br0 inet dhcp
     bridge_ports eth2 wlan2
     bridge_maxwait 0
=====================
... but it does not seem to work as hoped.

Thanks in Advance for *ANY* hint ;)

Regards
Mauro
>
> On Tue, Oct 26, 2010 at 5:24 AM, Mauro Condarelli <mc5686@mclink.it 
> <mailto:mc5686@mclink.it>> wrote:
>
>     Hi,
>     I read a lot on the Internet, but didn't find quite what I need.
>     I'm not even sure it's possible.
>
>     I have a machine with ethernet access and wireless card (in master
>     mode).
>     Both are running ok under ubuntu maverick.
>     I also have a separate firewall (wired) acting as DHCP server for my
>     whole home network.
>     I would like to bind the two interfaces together with no
>     translation (no
>     NAT, SNAT, masquerading, ...) so that the machines connecting to the
>     wireless lan can get their address from the firewall and access the
>     Internet.
>
>     Is this possible with bridging?
>     If so: can someone point me to the right documentation?
>
>     TiA
>     Mauro
>     _______________________________________________
>     Bridge mailing list
>     Bridge@lists.linux-foundation.org
>     <mailto:Bridge@lists.linux-foundation.org>
>     https://lists.linux-foundation.org/mailman/listinfo/bridge
>
>


[-- Attachment #2: Type: text/html, Size: 4023 bytes --]

  reply	other threads:[~2010-10-30 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  9:24 [Bridge] Transparent wired/wirless bridge: is it possible? Mauro Condarelli
2010-10-26 12:36 ` Ryan Whelan
2010-10-30 16:20   ` Mauro Condarelli [this message]
2010-10-30 22:16     ` Nicolas de Pesloüan
2010-11-01 12:40       ` Mauro Condarelli
2010-11-01 12:49     ` Ryan Whelan

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=4CCC45E9.7070801@mclink.it \
    --to=mc5686@mclink.it \
    --cc=bridge@lists.linux-foundation.org \
    --cc=rcwhelan@gmail.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