From: Jochen Hebbrecht <jochenhebbrecht@gmail.com>
To: Ross Vandegrift <ross@kallisti.us>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails
Date: Tue, 28 Apr 2009 19:36:26 +0200 [thread overview]
Message-ID: <49F73E9A.7090706@gmail.com> (raw)
In-Reply-To: <20090428133702.GA26738@kallisti.us>
Ross Vandegrift schreef:
> On Tue, Apr 28, 2009 at 02:52:10PM +0200, Jochen Hebbrecht wrote:
>
>> Okay, thnx!
>> Just a small question, I think I need to configure eth0 and eth1 to
>> manual? And not to DHCP?
>>
>> Like this:
>> ----------------------------------------
>> auto eth0
>> iface eth0 inet manual
>>
>> auto eth1
>> iface eth1 inet manual
>> ----------------------------------------
>>
>
> Ah - I missed that. Yes, you definitely want to set the member
> interfaces to manual.
>
>
>> The thing I don't understand then: if you execute a dhclient on br0,
>> how does br0 know the configuration of eth1? Because there's a WPA2
>> configuration on it. Will it use that settings too while bridging?
>>
>
> I'll be honest, I'm not sure - I've never done that with
> wpa_supplicant and the debian tools. You might need to activate
> wpa_supplicant in the pre-up for br0.
>
> Check out the manpage for interfaces - it may have more details.
>
Ok, I made it myself a little easier by temporarly switching from WPA2
to unsecure wireless networking.
I'm having the following configuration:
Code:
to lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
wireless-essid ##MY-ESSID##
wireless-mode managed
auto br0
iface br0 inet dhcp
bridge_ports eth0, eth1
When I reboot, my interfaces are getting the following config:
Code:
br0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c
inet6 addr: fe80::20a:e4ff:feae:7e4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:87 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17544 (17.1 KB) TX bytes:3744 (3.6 KB)
br0:avahi Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c
inet addr:169.254.7.81 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c
inet6 addr: fe80::20a:e4ff:feae:7e4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1770 (1.7 KB) TX bytes:23069 (22.5 KB)
Interrupt:20 Base address:0xc000
eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6
inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:223 errors:0 dropped:0 overruns:0 frame:0
TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18762 (18.3 KB) TX bytes:8392 (8.1 KB)
Interrupt:21 Base address:0xa000 Memory:c8006000-c8006fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1879 errors:0 dropped:0 overruns:0 frame:0
TX packets:1879 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:94956 (92.7 KB) TX bytes:94956 (92.7 KB
The bridge looks ok:
Code:
jochus@Bacardi ~ $ sudo brctl show br0
[sudo] password for jochus:
bridge name bridge id STP enabled interfaces
br0 8000.000ae4ae7e4c no eth0
eth1
My routing table looks like this:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 br0
But I'm not able to ping my router ...
Code:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.111 icmp_seq=1 Destination Host Unreachable
From 192.168.1.111 icmp_seq=2 Destination Host Unreachable
From 192.168.1.111 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4018ms
I don't understand why eth1 is in my routing table. It shouldn't be I guess?
Anybody some idea's?
next prev parent reply other threads:[~2009-04-28 17:36 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 [this message]
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
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=49F73E9A.7090706@gmail.com \
--to=jochenhebbrecht@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=ross@kallisti.us \
/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