From: Jochen Hebbrecht <jochenhebbrecht@gmail.com>
To: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails
Date: Sat, 02 May 2009 15:15:16 +0200 [thread overview]
Message-ID: <49FC4764.3030707@gmail.com> (raw)
In-Reply-To: <49FA1E28.5020604@free.fr>
Nicolas de Pesloüan schreef:
>
> Can you also explain why you are trying to use bridge ?
>
> Are you just trying to share a common IP address between two links
> (Ethernet and wifi), in order to switch automatically to wifi when you
> unplug the Ethernet wire, without loosing any active connections ?
>
> If this is what you are trying to do, you might try the bonding module
> instead of bridge, and have a look at the ifenslave-2.6 package from
> Debian, which should work on Ubuntu. This package enhance the ifupdown
> system and allow you to bond an Ethernet and a Wifi link, in an
> active/backup mode. An "Ethernet+wifi" example configuration is
> provided in the documentation.
>
> You configuration should look like this :
>
> auto bond0
> iface bond0 inet dhcp
> bond-slaves eth0
> bond-mode 1
> bond-miimon 100
> bond-primary eth0
>
> iface eth0 inet manual
> # Useless, unless NetworkManager is enabled on you system.
>
> auto eth1
> iface eth1 inet manual
> bond-master bond0
> bond-give-a-chance 10
> wpa-bridge bond0
> wpa-driver wext
> wpa-ssid ##SSID##
> wpa-ap-scan 1
> wpa-proto RSN
> wpa-pariwire CCMP
> wpa-group CCMP
> wpa-key-mgmt WPA-PSK
> wpa-psk ##PSK KEY##
>
> 'hope this help.
>
> Nicolas.
Nicolas,
I'm not sure that bonding is the thing I need. I'll explain what I want
to do.
Please check this image: http://www.jochus.be/brol/networking.png
* Purple lines: wired (UTP)
* Blue (dashed) lines: wireless
So in this building, there are 2 locations. Location A and B. There's no
possibility to link them using a wired cable, and I don't like the net
adapters who transmits packets using the 50Hz channel.
In location A, there's a desktop and a notebook a. In location B,
there's a notebook, a server which maintains e-mails, backup,
Subversion, Archiva, ... and there's also printer (a network printer).
So, notebook B needs to print to the network printer, which is very easy
by using the switch that's on location B. So that works. But now I want
to print from location A on the desktop and notebook A. So I needed to
connect them in the same subnet of the networkprinter.
So, I wanted to created a bridge on the Ubuntu server (who has a
wireless WMP54G network card), and on eth0 an ethernet controller. So by
connecting eth0 to the switch, all notebooks and desktop would be able
to print to the networkprinter
This situation works fine if the server is running Windows, but not
Ubuntu as the bridge isn't working there :-(
Hope this clears out what I'm trying to do
Best regards,
Jochen
next prev parent reply other threads:[~2009-05-02 13:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 21:13 [Bridge] Ubuntu: network bridging between wireless and wired connection fails Jochen Hebbrecht
2009-04-27 21:36 ` richardvoigt
2009-04-28 6:44 ` Jochen Hebbrecht
2009-04-28 12:40 ` Ross Vandegrift
2009-04-28 12:52 ` Jochen Hebbrecht
2009-04-28 13:37 ` Ross Vandegrift
2009-04-28 17:36 ` Jochen Hebbrecht
2009-04-28 19:00 ` richardvoigt
2009-04-28 21:16 ` Jochen Hebbrecht
2009-04-28 23:00 ` richardvoigt
2009-04-29 16:16 ` Jochen Hebbrecht
2009-04-29 16:26 ` Ross Vandegrift
2009-04-29 16:40 ` Jochen Hebbrecht
2009-04-29 16:53 ` Ross Vandegrift
2009-04-29 21:21 ` Jochen Hebbrecht
2009-04-30 4:18 ` richardvoigt
2009-04-30 6:30 ` Jochen Hebbrecht
2009-04-30 21:54 ` Nicolas de Pesloüan
2009-05-02 13:15 ` Jochen Hebbrecht [this message]
2009-05-03 17:46 ` Nicolas de Pesloüan
2009-05-04 3:59 ` richardvoigt
2009-05-04 19:29 ` Jochen Hebbrecht
2009-05-04 19:28 ` Jochen Hebbrecht
2009-05-04 19:34 ` Nicolas de Pesloüan
2009-05-04 19:42 ` Jochen Hebbrecht
2009-05-04 20:07 ` Nicolas de Pesloüan
2009-05-04 21:06 ` Jochen Hebbrecht
2009-05-04 23:33 ` richardvoigt
2009-05-05 5:49 ` Nicolas de Pesloüan
2009-05-05 16:59 ` Jochen Hebbrecht
2009-05-05 6:20 ` Nicolas de Pesloüan
2009-05-05 17:01 ` Jochen Hebbrecht
2009-05-05 18:08 ` richardvoigt
2009-05-05 19:19 ` Jochen Hebbrecht
2009-05-05 19:53 ` Jonathan Thibault
2009-05-05 20:52 ` Jochen Hebbrecht
2009-05-05 21:44 ` Nicolas de Pesloüan
2009-05-06 6:57 ` Jochen Hebbrecht
2009-05-06 15:37 ` Jochen Hebbrecht
2009-05-06 16:55 ` Jonathan Thibault
2009-05-09 11:15 ` Jochen Hebbrecht
2009-05-06 16:47 ` Jochen Hebbrecht
2009-05-06 20:07 ` Nicolas de Pesloüan
2009-05-09 11:17 ` Jochen Hebbrecht
2009-05-09 23:30 ` richardvoigt
2009-05-10 15:39 ` Nicolas de Pesloüan
2009-04-29 16:41 ` Jochen Hebbrecht
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=49FC4764.3030707@gmail.com \
--to=jochenhebbrecht@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=nicolas.2p.debian@free.fr \
/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