* [Bridge] Ubuntu: network bridging between wireless and wired connection fails
@ 2009-04-27 21:13 Jochen Hebbrecht
2009-04-27 21:36 ` richardvoigt
0 siblings, 1 reply; 47+ messages in thread
From: Jochen Hebbrecht @ 2009-04-27 21:13 UTC (permalink / raw)
To: bridge
Hi everybody,
First of all, let me say that I searched a lot on the internet. I
spent several hours sitting after my notebook, but I can't configure
my network bridge in Ubuntu. I'm really desperate, so I hope somebody
can point me out what I'm doing
Hardware:
-----------------------------------------------------------
$ lspci | grep controller
06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG
Network Connection (rev 05)
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
-----------------------------------------------------------
Kernel:
-----------------------------------------------------------
$ uname -a
Linux Bacardi 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009
i686 GNU/Linux
-----------------------------------------------------------
I first tested the hardware in windows xp sp3. I selected the 2
interfaces, right clicked on them and picked up: "Create network
bridge". 30 seconds later, I was having a network bridge between my
wired and wireless controller :-). Everything was working smoothly.
Now, I want to do the same thing on my Ubuntu installation (same
notebook, just dual booting to Ubuntu). I thought it would be easy,
but apparantly, it isn't :-( ...
This is my /etc/network/interfaces file:
-----------------------------------------------------------
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid ##SSID##
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk ##PSK KEY##
auto br0
iface br0 inet dhcp
bridge_ports eth0 eth1
-----------------------------------------------------------
So, eth1 is my wireless connection, eth0 is my wired connection.
Without the bridge, I'm able to make a connection on my wireless side,
as on my wired side.
When I bring up the bridge, nothing works ... I'm not able to ping anything.
This is my routing table:
-----------------------------------------------------------
$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 b
-----------------------------------------------------------
And ifconfig -a information
-----------------------------------------------------------
$ ifconfig -a
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:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3927 (3.8 KB) TX bytes:6970 (6.8 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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:107 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:12221 (11.9 KB)
Interrupt:20 Base address:0xc000
eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6
inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:844783 (824.9 KB) TX bytes:128864 (125.8 KB)
Interrupt:21 Base address:0xc000 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:1734 errors:0 dropped:0 overruns:0 frame:0
TX packets:1734 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:88276 (86.2 KB) TX bytes:88276 (86.2 KB)
-----------------------------------------------------------
This is the output of syslog after restarting the networking daemon
-----------------------------------------------------------
Apr 27 23:01:32 Bacardi dhclient: There is already a pid file
/var/run/dhclient.eth1.pid with pid 134519072
Apr 27 23:01:32 Bacardi dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 27 23:01:32 Bacardi dhclient: Copyright 2004-2007 Internet Systems
Consortium.
Apr 27 23:01:32 Bacardi dhclient: All rights reserved.
Apr 27 23:01:32 Bacardi dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Apr 27 23:01:32 Bacardi dhclient:
Apr 27 23:01:32 Bacardi kernel: [ 158.946623]
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Apr 27 23:01:33 Bacardi dhclient: Listening on LPF/eth1/00:15:00:1f:20:a6
Apr 27 23:01:33 Bacardi dhclient: Sending on LPF/eth1/00:15:00:1f:20:a6
Apr 27 23:01:33 Bacardi dhclient: Sending on Socket/fallback
Apr 27 23:01:36 Bacardi dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 8
Apr 27 23:01:36 Bacardi dhclient: DHCPOFFER of 192.168.1.111 from 192.168.1.1
Apr 27 23:01:36 Bacardi dhclient: DHCPREQUEST of 192.168.1.111 on eth1
to 255.255.255.255 port 67
Apr 27 23:01:37 Bacardi dhclient: DHCPACK of 192.168.1.111 from 192.168.1.1
Apr 27 23:01:37 Bacardi dhclient: bound to 192.168.1.111 -- renewal in
42920 seconds.
Apr 27 23:01:42 Bacardi kernel: [ 161.516967] eth1: no IPv6 routers present
Apr 27 23:01:43 Bacardi kernel: [ 74.578698] Bridge firewalling registered
Apr 27 23:01:43 Bacardi kernel: [ 74.578967] br0: Dropping
NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Apr 27 23:01:43 Bacardi kernel: [ 74.581732] device eth0 entered
promiscuous mode
Apr 27 23:01:43 Bacardi kernel: [ 74.581740]
audit(1240866103.181:3): dev=eth0 prom=256 old_prom=0 auid=4294967295
Apr 27 23:01:43 Bacardi kernel: [ 74.583808] device eth1 entered
promiscuous mode
Apr 27 23:01:43 Bacardi kernel: [ 74.583816]
audit(1240866103.181:4): dev=eth1 prom=256 old_prom=0 auid=4294967295
Apr 27 23:01:43 Bacardi kernel: [ 74.586637] br0: port 2(eth1)
entering learning state
Apr 27 23:01:43 Bacardi kernel: [ 74.586641] br0: port 1(eth0)
entering learning state
Apr 27 23:01:48 Bacardi ntpdate[7485]: can't find host ntp.univ-lyon1.fr
Apr 27 23:01:48 Bacardi ntpdate[7485]: sendto(91.189.94.4): Network is
unreachable
Apr 27 23:01:51 Bacardi last message repeated 3 times
Apr 27 23:01:52 Bacardi ntpdate[7485]: no server suitable for
synchronization found
Apr 27 23:01:53 Bacardi kernel: [ 162.782421] br0: no IPv6 routers present
Apr 27 23:01:58 Bacardi kernel: [ 164.002241] br0: topology change
detected, propagating
Apr 27 23:01:58 Bacardi kernel: [ 164.002252] br0: port 2(eth1)
entering forwarding state
Apr 27 23:01:58 Bacardi kernel: [ 164.002257] br0: topology change
detected, propagating
Apr 27 23:01:58 Bacardi kernel: [ 164.002262] br0: port 1(eth0)
entering forwarding state
Apr 27 23:01:58 Bacardi dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 27 23:01:58 Bacardi dhclient: Copyright 2004-2007 Internet Systems
Consortium.
Apr 27 23:01:58 Bacardi dhclient: All rights reserved.
Apr 27 23:01:58 Bacardi dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Apr 27 23:01:58 Bacardi dhclient:
Apr 27 23:01:59 Bacardi dhclient: Listening on LPF/br0/00:0a:e4:ae:7e:4c
Apr 27 23:01:59 Bacardi dhclient: Sending on LPF/br0/00:0a:e4:ae:7e:4c
Apr 27 23:01:59 Bacardi dhclient: Sending on Socket/fallback
Apr 27 23:02:02 Bacardi dhclient: DHCPDISCOVER on br0 to
255.255.255.255 port 67 interval 8
Apr 27 23:02:10 Bacardi dhclient: DHCPDISCOVER on br0 to
255.255.255.255 port 67 interval 12
Apr 27 23:02:22 Bacardi dhclient: DHCPDISCOVER on br0 to
255.255.255.255 port 67 interval 11
Apr 27 23:02:33 Bacardi dhclient: No DHCPOFFERS received.
Apr 27 23:02:33 Bacardi dhclient: No working leases in persistent
database - sleeping.
Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Found user
'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully called chroot().
Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully dropped
root privileges.
Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Starting with
address 169.254.7.81
Apr 27 23:02:38 Bacardi avahi-autoipd(br0)[7686]: Callout BIND,
address 169.254.7.81 on interface br0
Apr 27 23:02:42 Bacardi avahi-autoipd(br0)[7686]: Successfully claimed
IP address 169.254.7.81
-----------------------------------------------------------
So I'm sure the wireless network card is able to bridge (as it works
in Windows). I'm not sure if it works in Ubuntu. But what can the
problem be? Is there something wrong in my configuration file? When do
you choose dhcp/static/manual Which log files should I check, just to
understand what's going wrong?
Thanks for you time to read this mail. I really hope somebody can help
me out here :-( ...
Jochen
^ permalink raw reply [flat|nested] 47+ messages in thread* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 0 siblings, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-04-27 21:36 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 10113 bytes --] Don't run dhcp on interfaces (eth1) that are joined to the bridge, only on the bridge interface itself. On Mon, Apr 27, 2009 at 4:13 PM, Jochen Hebbrecht <jochenhebbrecht@gmail.com > wrote: > Hi everybody, > > First of all, let me say that I searched a lot on the internet. I > spent several hours sitting after my notebook, but I can't configure > my network bridge in Ubuntu. I'm really desperate, so I hope somebody > can point me out what I'm doing > > Hardware: > ----------------------------------------------------------- > $ lspci | grep controller > 06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG > Network Connection (rev 05) > 06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 > Gigabit Ethernet (rev 10) > ----------------------------------------------------------- > > Kernel: > ----------------------------------------------------------- > $ uname -a > Linux Bacardi 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009 > i686 GNU/Linux > ----------------------------------------------------------- > > I first tested the hardware in windows xp sp3. I selected the 2 > interfaces, right clicked on them and picked up: "Create network > bridge". 30 seconds later, I was having a network bridge between my > wired and wireless controller :-). Everything was working smoothly. > > Now, I want to do the same thing on my Ubuntu installation (same > notebook, just dual booting to Ubuntu). I thought it would be easy, > but apparantly, it isn't :-( ... > > This is my /etc/network/interfaces file: > > ----------------------------------------------------------- > $ cat /etc/network/interfaces > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet manual > > auto eth1 > iface eth1 inet dhcp > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > > auto br0 > iface br0 inet dhcp > bridge_ports eth0 eth1 > ----------------------------------------------------------- > > So, eth1 is my wireless connection, eth0 is my wired connection. > Without the bridge, I'm able to make a connection on my wireless side, > as on my wired side. > > When I bring up the bridge, nothing works ... I'm not able to ping > anything. > This is my routing table: > > ----------------------------------------------------------- > $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0 > 0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 b > ----------------------------------------------------------- > > And ifconfig -a information > ----------------------------------------------------------- > $ ifconfig -a > 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:11 errors:0 dropped:0 overruns:0 frame:0 > TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3927 (3.8 KB) TX bytes:6970 (6.8 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:12221 (11.9 KB) > Interrupt:20 Base address:0xc000 > > eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 > inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:80 errors:0 dropped:0 overruns:0 frame:0 > TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:844783 (824.9 KB) TX bytes:128864 (125.8 KB) > Interrupt:21 Base address:0xc000 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:1734 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1734 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:88276 (86.2 KB) TX bytes:88276 (86.2 KB) > ----------------------------------------------------------- > > This is the output of syslog after restarting the networking daemon > > ----------------------------------------------------------- > Apr 27 23:01:32 Bacardi dhclient: There is already a pid file > /var/run/dhclient.eth1.pid with pid 134519072 > Apr 27 23:01:32 Bacardi dhclient: Internet Systems Consortium DHCP Client > V3.0.6 > Apr 27 23:01:32 Bacardi dhclient: Copyright 2004-2007 Internet Systems > Consortium. > Apr 27 23:01:32 Bacardi dhclient: All rights reserved. > Apr 27 23:01:32 Bacardi dhclient: For info, please visit > http://www.isc.org/sw/dhcp/ > Apr 27 23:01:32 Bacardi dhclient: > Apr 27 23:01:32 Bacardi kernel: [ 158.946623] > ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready > Apr 27 23:01:33 Bacardi dhclient: Listening on LPF/eth1/00:15:00:1f:20:a6 > Apr 27 23:01:33 Bacardi dhclient: Sending on LPF/eth1/00:15:00:1f:20:a6 > Apr 27 23:01:33 Bacardi dhclient: Sending on Socket/fallback > Apr 27 23:01:36 Bacardi dhclient: DHCPDISCOVER on eth1 to > 255.255.255.255 port 67 interval 8 > Apr 27 23:01:36 Bacardi dhclient: DHCPOFFER of 192.168.1.111 from > 192.168.1.1 > Apr 27 23:01:36 Bacardi dhclient: DHCPREQUEST of 192.168.1.111 on eth1 > to 255.255.255.255 port 67 > Apr 27 23:01:37 Bacardi dhclient: DHCPACK of 192.168.1.111 from 192.168.1.1 > Apr 27 23:01:37 Bacardi dhclient: bound to 192.168.1.111 -- renewal in > 42920 seconds. > Apr 27 23:01:42 Bacardi kernel: [ 161.516967] eth1: no IPv6 routers > present > Apr 27 23:01:43 Bacardi kernel: [ 74.578698] Bridge firewalling > registered > Apr 27 23:01:43 Bacardi kernel: [ 74.578967] br0: Dropping > NETIF_F_UFO since no NETIF_F_HW_CSUM feature. > Apr 27 23:01:43 Bacardi kernel: [ 74.581732] device eth0 entered > promiscuous mode > Apr 27 23:01:43 Bacardi kernel: [ 74.581740] > audit(1240866103.181:3): dev=eth0 prom=256 old_prom=0 auid=4294967295 > Apr 27 23:01:43 Bacardi kernel: [ 74.583808] device eth1 entered > promiscuous mode > Apr 27 23:01:43 Bacardi kernel: [ 74.583816] > audit(1240866103.181:4): dev=eth1 prom=256 old_prom=0 auid=4294967295 > Apr 27 23:01:43 Bacardi kernel: [ 74.586637] br0: port 2(eth1) > entering learning state > Apr 27 23:01:43 Bacardi kernel: [ 74.586641] br0: port 1(eth0) > entering learning state > Apr 27 23:01:48 Bacardi ntpdate[7485]: can't find host ntp.univ-lyon1.fr > Apr 27 23:01:48 Bacardi ntpdate[7485]: sendto(91.189.94.4): Network is > unreachable > Apr 27 23:01:51 Bacardi last message repeated 3 times > Apr 27 23:01:52 Bacardi ntpdate[7485]: no server suitable for > synchronization found > Apr 27 23:01:53 Bacardi kernel: [ 162.782421] br0: no IPv6 routers present > Apr 27 23:01:58 Bacardi kernel: [ 164.002241] br0: topology change > detected, propagating > Apr 27 23:01:58 Bacardi kernel: [ 164.002252] br0: port 2(eth1) > entering forwarding state > Apr 27 23:01:58 Bacardi kernel: [ 164.002257] br0: topology change > detected, propagating > Apr 27 23:01:58 Bacardi kernel: [ 164.002262] br0: port 1(eth0) > entering forwarding state > Apr 27 23:01:58 Bacardi dhclient: Internet Systems Consortium DHCP Client > V3.0.6 > Apr 27 23:01:58 Bacardi dhclient: Copyright 2004-2007 Internet Systems > Consortium. > Apr 27 23:01:58 Bacardi dhclient: All rights reserved. > Apr 27 23:01:58 Bacardi dhclient: For info, please visit > http://www.isc.org/sw/dhcp/ > Apr 27 23:01:58 Bacardi dhclient: > Apr 27 23:01:59 Bacardi dhclient: Listening on LPF/br0/00:0a:e4:ae:7e:4c > Apr 27 23:01:59 Bacardi dhclient: Sending on LPF/br0/00:0a:e4:ae:7e:4c > Apr 27 23:01:59 Bacardi dhclient: Sending on Socket/fallback > Apr 27 23:02:02 Bacardi dhclient: DHCPDISCOVER on br0 to > 255.255.255.255 port 67 interval 8 > Apr 27 23:02:10 Bacardi dhclient: DHCPDISCOVER on br0 to > 255.255.255.255 port 67 interval 12 > Apr 27 23:02:22 Bacardi dhclient: DHCPDISCOVER on br0 to > 255.255.255.255 port 67 interval 11 > Apr 27 23:02:33 Bacardi dhclient: No DHCPOFFERS received. > Apr 27 23:02:33 Bacardi dhclient: No working leases in persistent > database - sleeping. > Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Found user > 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113). > Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully called > chroot(). > Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully dropped > root privileges. > Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Starting with > address 169.254.7.81 > Apr 27 23:02:38 Bacardi avahi-autoipd(br0)[7686]: Callout BIND, > address 169.254.7.81 on interface br0 > Apr 27 23:02:42 Bacardi avahi-autoipd(br0)[7686]: Successfully claimed > IP address 169.254.7.81 > ----------------------------------------------------------- > > > So I'm sure the wireless network card is able to bridge (as it works > in Windows). I'm not sure if it works in Ubuntu. But what can the > problem be? Is there something wrong in my configuration file? When do > you choose dhcp/static/manual Which log files should I check, just to > understand what's going wrong? > > > Thanks for you time to read this mail. I really hope somebody can help > me out here :-( ... > > Jochen > _______________________________________________ > Bridge mailing list > Bridge@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/bridge > [-- Attachment #2: Type: text/html, Size: 11458 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-27 21:36 ` richardvoigt @ 2009-04-28 6:44 ` Jochen Hebbrecht 2009-04-28 12:40 ` Ross Vandegrift 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-28 6:44 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge Thnx Richard! I will try this when I'm back home. So the configuration is good? I just need to: $ ifconfig br0 up $ dhclient br0 Right? 2009/4/27 richardvoigt@gmail.com <richardvoigt@gmail.com>: > Don't run dhcp on interfaces (eth1) that are joined to the bridge, only on > the bridge interface itself. > > On Mon, Apr 27, 2009 at 4:13 PM, Jochen Hebbrecht > <jochenhebbrecht@gmail.com> wrote: >> >> Hi everybody, >> >> First of all, let me say that I searched a lot on the internet. I >> spent several hours sitting after my notebook, but I can't configure >> my network bridge in Ubuntu. I'm really desperate, so I hope somebody >> can point me out what I'm doing >> >> Hardware: >> ----------------------------------------------------------- >> $ lspci | grep controller >> 06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG >> Network Connection (rev 05) >> 06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 >> Gigabit Ethernet (rev 10) >> ----------------------------------------------------------- >> >> Kernel: >> ----------------------------------------------------------- >> $ uname -a >> Linux Bacardi 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009 >> i686 GNU/Linux >> ----------------------------------------------------------- >> >> I first tested the hardware in windows xp sp3. I selected the 2 >> interfaces, right clicked on them and picked up: "Create network >> bridge". 30 seconds later, I was having a network bridge between my >> wired and wireless controller :-). Everything was working smoothly. >> >> Now, I want to do the same thing on my Ubuntu installation (same >> notebook, just dual booting to Ubuntu). I thought it would be easy, >> but apparantly, it isn't :-( ... >> >> This is my /etc/network/interfaces file: >> >> ----------------------------------------------------------- >> $ cat /etc/network/interfaces >> auto lo >> iface lo inet loopback >> >> auto eth0 >> iface eth0 inet manual >> >> auto eth1 >> iface eth1 inet dhcp >> wpa-driver wext >> wpa-ssid ##SSID## >> wpa-ap-scan 1 >> wpa-proto RSN >> wpa-pairwise CCMP >> wpa-group CCMP >> wpa-key-mgmt WPA-PSK >> wpa-psk ##PSK KEY## >> >> auto br0 >> iface br0 inet dhcp >> bridge_ports eth0 eth1 >> ----------------------------------------------------------- >> >> So, eth1 is my wireless connection, eth0 is my wired connection. >> Without the bridge, I'm able to make a connection on my wireless side, >> as on my wired side. >> >> When I bring up the bridge, nothing works ... I'm not able to ping >> anything. >> This is my routing table: >> >> ----------------------------------------------------------- >> $ route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use >> Iface >> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 >> br0 >> 0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 b >> ----------------------------------------------------------- >> >> And ifconfig -a information >> ----------------------------------------------------------- >> $ ifconfig -a >> 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:11 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:3927 (3.8 KB) TX bytes:6970 (6.8 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:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:107 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 B) TX bytes:12221 (11.9 KB) >> Interrupt:20 Base address:0xc000 >> >> eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 >> inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:80 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:844783 (824.9 KB) TX bytes:128864 (125.8 KB) >> Interrupt:21 Base address:0xc000 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:1734 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:1734 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:88276 (86.2 KB) TX bytes:88276 (86.2 KB) >> ----------------------------------------------------------- >> >> This is the output of syslog after restarting the networking daemon >> >> ----------------------------------------------------------- >> Apr 27 23:01:32 Bacardi dhclient: There is already a pid file >> /var/run/dhclient.eth1.pid with pid 134519072 >> Apr 27 23:01:32 Bacardi dhclient: Internet Systems Consortium DHCP Client >> V3.0.6 >> Apr 27 23:01:32 Bacardi dhclient: Copyright 2004-2007 Internet Systems >> Consortium. >> Apr 27 23:01:32 Bacardi dhclient: All rights reserved. >> Apr 27 23:01:32 Bacardi dhclient: For info, please visit >> http://www.isc.org/sw/dhcp/ >> Apr 27 23:01:32 Bacardi dhclient: >> Apr 27 23:01:32 Bacardi kernel: [ 158.946623] >> ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready >> Apr 27 23:01:33 Bacardi dhclient: Listening on LPF/eth1/00:15:00:1f:20:a6 >> Apr 27 23:01:33 Bacardi dhclient: Sending on LPF/eth1/00:15:00:1f:20:a6 >> Apr 27 23:01:33 Bacardi dhclient: Sending on Socket/fallback >> Apr 27 23:01:36 Bacardi dhclient: DHCPDISCOVER on eth1 to >> 255.255.255.255 port 67 interval 8 >> Apr 27 23:01:36 Bacardi dhclient: DHCPOFFER of 192.168.1.111 from >> 192.168.1.1 >> Apr 27 23:01:36 Bacardi dhclient: DHCPREQUEST of 192.168.1.111 on eth1 >> to 255.255.255.255 port 67 >> Apr 27 23:01:37 Bacardi dhclient: DHCPACK of 192.168.1.111 from >> 192.168.1.1 >> Apr 27 23:01:37 Bacardi dhclient: bound to 192.168.1.111 -- renewal in >> 42920 seconds. >> Apr 27 23:01:42 Bacardi kernel: [ 161.516967] eth1: no IPv6 routers >> present >> Apr 27 23:01:43 Bacardi kernel: [ 74.578698] Bridge firewalling >> registered >> Apr 27 23:01:43 Bacardi kernel: [ 74.578967] br0: Dropping >> NETIF_F_UFO since no NETIF_F_HW_CSUM feature. >> Apr 27 23:01:43 Bacardi kernel: [ 74.581732] device eth0 entered >> promiscuous mode >> Apr 27 23:01:43 Bacardi kernel: [ 74.581740] >> audit(1240866103.181:3): dev=eth0 prom=256 old_prom=0 auid=4294967295 >> Apr 27 23:01:43 Bacardi kernel: [ 74.583808] device eth1 entered >> promiscuous mode >> Apr 27 23:01:43 Bacardi kernel: [ 74.583816] >> audit(1240866103.181:4): dev=eth1 prom=256 old_prom=0 auid=4294967295 >> Apr 27 23:01:43 Bacardi kernel: [ 74.586637] br0: port 2(eth1) >> entering learning state >> Apr 27 23:01:43 Bacardi kernel: [ 74.586641] br0: port 1(eth0) >> entering learning state >> Apr 27 23:01:48 Bacardi ntpdate[7485]: can't find host ntp.univ-lyon1.fr >> Apr 27 23:01:48 Bacardi ntpdate[7485]: sendto(91.189.94.4): Network is >> unreachable >> Apr 27 23:01:51 Bacardi last message repeated 3 times >> Apr 27 23:01:52 Bacardi ntpdate[7485]: no server suitable for >> synchronization found >> Apr 27 23:01:53 Bacardi kernel: [ 162.782421] br0: no IPv6 routers >> present >> Apr 27 23:01:58 Bacardi kernel: [ 164.002241] br0: topology change >> detected, propagating >> Apr 27 23:01:58 Bacardi kernel: [ 164.002252] br0: port 2(eth1) >> entering forwarding state >> Apr 27 23:01:58 Bacardi kernel: [ 164.002257] br0: topology change >> detected, propagating >> Apr 27 23:01:58 Bacardi kernel: [ 164.002262] br0: port 1(eth0) >> entering forwarding state >> Apr 27 23:01:58 Bacardi dhclient: Internet Systems Consortium DHCP Client >> V3.0.6 >> Apr 27 23:01:58 Bacardi dhclient: Copyright 2004-2007 Internet Systems >> Consortium. >> Apr 27 23:01:58 Bacardi dhclient: All rights reserved. >> Apr 27 23:01:58 Bacardi dhclient: For info, please visit >> http://www.isc.org/sw/dhcp/ >> Apr 27 23:01:58 Bacardi dhclient: >> Apr 27 23:01:59 Bacardi dhclient: Listening on LPF/br0/00:0a:e4:ae:7e:4c >> Apr 27 23:01:59 Bacardi dhclient: Sending on LPF/br0/00:0a:e4:ae:7e:4c >> Apr 27 23:01:59 Bacardi dhclient: Sending on Socket/fallback >> Apr 27 23:02:02 Bacardi dhclient: DHCPDISCOVER on br0 to >> 255.255.255.255 port 67 interval 8 >> Apr 27 23:02:10 Bacardi dhclient: DHCPDISCOVER on br0 to >> 255.255.255.255 port 67 interval 12 >> Apr 27 23:02:22 Bacardi dhclient: DHCPDISCOVER on br0 to >> 255.255.255.255 port 67 interval 11 >> Apr 27 23:02:33 Bacardi dhclient: No DHCPOFFERS received. >> Apr 27 23:02:33 Bacardi dhclient: No working leases in persistent >> database - sleeping. >> Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Found user >> 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113). >> Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully called >> chroot(). >> Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Successfully dropped >> root privileges. >> Apr 27 23:02:33 Bacardi avahi-autoipd(br0)[7686]: Starting with >> address 169.254.7.81 >> Apr 27 23:02:38 Bacardi avahi-autoipd(br0)[7686]: Callout BIND, >> address 169.254.7.81 on interface br0 >> Apr 27 23:02:42 Bacardi avahi-autoipd(br0)[7686]: Successfully claimed >> IP address 169.254.7.81 >> ----------------------------------------------------------- >> >> >> So I'm sure the wireless network card is able to bridge (as it works >> in Windows). I'm not sure if it works in Ubuntu. But what can the >> problem be? Is there something wrong in my configuration file? When do >> you choose dhcp/static/manual Which log files should I check, just to >> understand what's going wrong? >> >> >> Thanks for you time to read this mail. I really hope somebody can help >> me out here :-( ... >> >> Jochen >> _______________________________________________ >> Bridge mailing list >> Bridge@lists.linux-foundation.org >> https://lists.linux-foundation.org/mailman/listinfo/bridge > > ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 6:44 ` Jochen Hebbrecht @ 2009-04-28 12:40 ` Ross Vandegrift 2009-04-28 12:52 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Ross Vandegrift @ 2009-04-28 12:40 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On Tue, Apr 28, 2009 at 08:44:50AM +0200, Jochen Hebbrecht wrote: > Thnx Richard! I will try this when I'm back home. > > So the configuration is good? I just need to: > > $ ifconfig br0 up > $ dhclient br0 That will work, but note that you configured the bridge in the Debian interfaces file: > >> iface br0 inet dhcp > >> bridge_ports eth0 eth1 So now all you need to do is "ifup br0" to activate it and "ifdown br0" to deactivate it. -- Ross Vandegrift ross@kallisti.us "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 12:40 ` Ross Vandegrift @ 2009-04-28 12:52 ` Jochen Hebbrecht 2009-04-28 13:37 ` Ross Vandegrift 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-28 12:52 UTC (permalink / raw) To: Ross Vandegrift; +Cc: bridge 2009/4/28 Ross Vandegrift <ross@kallisti.us>: > On Tue, Apr 28, 2009 at 08:44:50AM +0200, Jochen Hebbrecht wrote: >> Thnx Richard! I will try this when I'm back home. >> >> So the configuration is good? I just need to: >> >> $ ifconfig br0 up >> $ dhclient br0 > > That will work, but note that you configured the bridge in the Debian > interfaces file: > >> >> iface br0 inet dhcp >> >> bridge_ports eth0 eth1 > > So now all you need to do is "ifup br0" to activate it and "ifdown > br0" to deactivate it. 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 ---------------------------------------- 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? ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 12:52 ` Jochen Hebbrecht @ 2009-04-28 13:37 ` Ross Vandegrift 2009-04-28 17:36 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Ross Vandegrift @ 2009-04-28 13:37 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On Tue, Apr 28, 2009 at 02:52:10PM +0200, Jochen Hebbrecht wrote: > 2009/4/28 Ross Vandegrift <ross@kallisti.us>: > > On Tue, Apr 28, 2009 at 08:44:50AM +0200, Jochen Hebbrecht wrote: > >> Thnx Richard! I will try this when I'm back home. > >> > >> So the configuration is good? I just need to: > >> > >> $ ifconfig br0 up > >> $ dhclient br0 > > > > That will work, but note that you configured the bridge in the Debian > > interfaces file: > > > >> >> iface br0 inet dhcp > >> >> bridge_ports eth0 eth1 > > > > So now all you need to do is "ifup br0" to activate it and "ifdown > > br0" to deactivate it. > > 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. -- Ross Vandegrift ross@kallisti.us "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 13:37 ` Ross Vandegrift @ 2009-04-28 17:36 ` Jochen Hebbrecht 2009-04-28 19:00 ` richardvoigt 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-28 17:36 UTC (permalink / raw) To: Ross Vandegrift; +Cc: bridge 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? ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 17:36 ` Jochen Hebbrecht @ 2009-04-28 19:00 ` richardvoigt 2009-04-28 21:16 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-04-28 19:00 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 5116 bytes --] Do some packet monitoring on your wireless network to see if the DHCP request is going out over the air... your problems stem from not getting a DHCP address. At first I thought the address given to eth1 might be interfering with br0... but it seems not. On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht < jochenhebbrecht@gmail.com> wrote: > > > 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? > [-- Attachment #2: Type: text/html, Size: 6470 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 19:00 ` richardvoigt @ 2009-04-28 21:16 ` Jochen Hebbrecht 2009-04-28 23:00 ` richardvoigt 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-28 21:16 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 13639 bytes --] Richard, After rebooting a second time, eth1 isn't appearing in the routing tabel any longer. The bridge seems to be working perfectly now! However, I'm not able to retreive any DHCP offers. I did some packet monitoring: br0 1 0.000000000 fe80::20a:e4ff:feae:7e4c ff02::2 ICMPv6 Router solicitation 2 24.824098000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 3 28.824043000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 4 33.685106000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 5 33.688946000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 6 33.692700000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 7 33.698081000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 8 33.701656000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 33.705492000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 10 33.708885000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 11 33.712502000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 12 33.716242000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 13 33.719929000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 14 38.824050000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 15 48.824039000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 16 56.768033000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 17 57.992048000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 18 59.019954000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 19 61.020124000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 20 62.004532000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> 21 62.004582000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> 22 62.004615000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> 23 62.004647000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> 24 62.004679000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> 25 62.004775000 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 26 63.023921000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 27 64.003996000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> 28 64.004033000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> 29 64.004054000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> 30 64.004075000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> 31 64.004097000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> 32 64.004156000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> 33 64.004179000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> 34 64.004200000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> 35 64.004220000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> 36 64.004240000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> 37 65.127895000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 38 66.004121000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> 39 66.004177000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> 40 66.004197000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> 41 66.004219000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> 42 66.004239000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> 43 66.127931000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 44 67.127989000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 45 70.127967000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 46 71.128025000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 eth0 1 0.000000 Wistron_ae:7e:4c Broadcast ARP Who has 192.168.1.1? Tell 192.168.1.112 2 19.840146 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 3 24.840168 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 4 38.840099 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 5 45.513321 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 6 45.516537 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 7 45.520384 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 8 45.524058 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 45.527325 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 10 45.530872 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 11 45.534676 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 12 45.538019 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 13 45.541774 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 14 45.545417 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 15 45.549231 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 16 51.412036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 17 53.360036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 18 54.716034 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 19 56.716135 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 20 58.716070 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 21 60.775980 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 eth1 1 0.000000 fe80::215:ff:fe1f:20a6 ff02::2 ICMPv6 Router solicitation 2 25.983879 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c 3 30.983864 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c 4 32.949057 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 5 32.952404 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 6 32.957215 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 7 32.960893 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 8 32.964222 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 32.970023 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 10 32.973868 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 11 32.977056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 12 32.981455 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 13 32.985056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 14 32.988717 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 15 44.983895 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c 16 54.983846 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c 17 57.199856 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 18 58.967801 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 19 60.039785 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 20 62.039897 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 21 64.039860 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) 22 66.107737 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 23 66.164183 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> 24 66.164203 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> 25 66.164222 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> 26 66.164241 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> 27 66.164258 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> 28 66.164314 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 You can see the DHCP discovers, but nobody's answering richardvoigt@gmail.com schreef: > Do some packet monitoring on your wireless network to see if the DHCP > request is going out over the air... your problems stem from not > getting a DHCP address. At first I thought the address given to eth1 > might be interfering with br0... but it seems not. > > On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht > <jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: > > > > 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? > > [-- Attachment #2: Type: text/html, Size: 17229 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 21:16 ` Jochen Hebbrecht @ 2009-04-28 23:00 ` richardvoigt 2009-04-29 16:16 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-04-28 23:00 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 13851 bytes --] Does your DHCP server only give out addresses to specific MAC addresses? Turning on bridge mode probably results in using the MAC address of eth0, rather than eth1 which had been successfully getting a DHCP assignment? I had actually meant for you to run packet capture from some other node on the wireless, to make sure the DHCP discover actually went out the radio. But you clearly are joined properly. So check for any sort of MAC-based security in the DHCP server. On Tue, Apr 28, 2009 at 4:16 PM, Jochen Hebbrecht <jochenhebbrecht@gmail.com > wrote: > Richard, > > After rebooting a second time, eth1 isn't appearing in the routing tabel > any longer. The bridge seems to be working perfectly now! > However, I'm not able to retreive any DHCP offers. > > I did some packet monitoring: > > br0 > > 1 0.000000000 fe80::20a:e4ff:feae:7e4c ff02::2 ICMPv6 Router solicitation > 2 24.824098000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 3 28.824043000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 4 33.685106000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 5 33.688946000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 33.692700000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 33.698081000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 33.701656000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 33.705492000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 33.708885000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 33.712502000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 33.716242000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 33.719929000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 38.824050000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 15 48.824039000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 16 56.768033000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 17 57.992048000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 59.019954000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 61.020124000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 20 62.004532000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 21 62.004582000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 22 62.004615000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 23 62.004647000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 24 62.004679000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 25 62.004775000 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 > 26 63.023921000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 27 64.003996000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 28 64.004033000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 29 64.004054000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 30 64.004075000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 31 64.004097000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 32 64.004156000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 33 64.004179000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 34 64.004200000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 35 64.004220000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 36 64.004240000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 37 65.127895000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 38 66.004121000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 39 66.004177000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 40 66.004197000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 41 66.004219000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 42 66.004239000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 43 66.127931000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 44 67.127989000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 45 70.127967000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 > 46 71.128025000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 > > > > eth0 > > 1 0.000000 Wistron_ae:7e:4c Broadcast ARP Who has 192.168.1.1? Tell 192.168.1.112 > 2 19.840146 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 3 24.840168 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 4 38.840099 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 5 45.513321 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 45.516537 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 45.520384 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 45.524058 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 45.527325 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 45.530872 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 45.534676 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 45.538019 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 45.541774 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 45.545417 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 15 45.549231 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 16 51.412036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 17 53.360036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 54.716034 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 56.716135 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 20 58.716070 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 21 60.775980 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > > > > eth1 > > 1 0.000000 fe80::215:ff:fe1f:20a6 ff02::2 ICMPv6 Router solicitation > 2 25.983879 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 3 30.983864 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 4 32.949057 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 5 32.952404 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 32.957215 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 32.960893 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 32.964222 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 32.970023 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 32.973868 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 32.977056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 32.981455 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 32.985056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 32.988717 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 15 44.983895 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 16 54.983846 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 17 57.199856 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 58.967801 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 60.039785 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 20 62.039897 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 21 64.039860 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 22 66.107737 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 23 66.164183 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 24 66.164203 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 25 66.164222 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 26 66.164241 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 27 66.164258 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 28 66.164314 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 > > > > You can see the DHCP discovers, but nobody's answering > > > > richardvoigt@gmail.com schreef: > > Do some packet monitoring on your wireless network to see if the DHCP > request is going out over the air... your problems stem from not getting a > DHCP address. At first I thought the address given to eth1 might be > interfering with br0... but it seems not. > > On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht < > jochenhebbrecht@gmail.com> wrote: > >> >> >> 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? >> > > [-- Attachment #2: Type: text/html, Size: 16275 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-28 23:00 ` richardvoigt @ 2009-04-29 16:16 ` Jochen Hebbrecht 2009-04-29 16:26 ` Ross Vandegrift 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-29 16:16 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 16708 bytes --] No, the DHCP server gives addresses to every MAC address that is possible. So this is the current situation: jochus@Bacardi ~ $ sudo brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.000ae4ae7e4c no eth0 eth1 jochus@Bacardi ~ $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0 0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 br0 I also found this thread: http://www.linuxquestions.org/questions/debian-26/howto-bridge-wireless-and-wired-network-interfaces-369455/, but that solution didn't work either. I'm not receiving any DHCP offers on eth1 I guess I'm stuck with it, and returning to windows is the best solution now :-) richardvoigt@gmail.com schreef: > Does your DHCP server only give out addresses to specific MAC > addresses? Turning on bridge mode probably results in using the MAC > address of eth0, rather than eth1 which had been successfully getting > a DHCP assignment? > > I had actually meant for you to run packet capture from some other > node on the wireless, to make sure the DHCP discover actually went out > the radio. But you clearly are joined properly. > > So check for any sort of MAC-based security in the DHCP server. > > On Tue, Apr 28, 2009 at 4:16 PM, Jochen Hebbrecht > <jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: > > Richard, > > After rebooting a second time, eth1 isn't appearing in the routing > tabel any longer. The bridge seems to be working perfectly now! > However, I'm not able to retreive any DHCP offers. > > I did some packet monitoring: > > br0 > > 1 0.000000000 fe80::20a:e4ff:feae:7e4c ff02::2 ICMPv6 Router solicitation > 2 24.824098000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 3 28.824043000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 4 33.685106000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 5 33.688946000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 33.692700000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 33.698081000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 33.701656000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 33.705492000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 33.708885000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 33.712502000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 33.716242000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 33.719929000 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 38.824050000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 15 48.824039000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xa117a72 > 16 56.768033000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 17 57.992048000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 59.019954000 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 61.020124000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 20 62.004532000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 21 62.004582000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 22 62.004615000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 23 62.004647000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 24 62.004679000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 25 62.004775000 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 > 26 63.023921000 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 27 64.003996000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 28 64.004033000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 29 64.004054000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 30 64.004075000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 31 64.004097000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 32 64.004156000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 33 64.004179000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 34 64.004200000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 35 64.004220000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 36 64.004240000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 37 65.127895000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 38 66.004121000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 39 66.004177000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 40 66.004197000 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 41 66.004219000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 42 66.004239000 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 43 66.127931000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 44 67.127989000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 45 70.127967000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 > 46 71.128025000 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.130.165? Tell 169.254.7.81 > > > > > eth0 > > 1 0.000000 Wistron_ae:7e:4c Broadcast ARP Who has 192.168.1.1? Tell 192.168.1.112 > 2 19.840146 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 3 24.840168 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 4 38.840099 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x8537ad48 > 5 45.513321 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 45.516537 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 45.520384 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 45.524058 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 45.527325 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 45.530872 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 45.534676 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 45.538019 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 45.541774 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 45.545417 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 15 45.549231 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 16 51.412036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 17 53.360036 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 54.716034 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 56.716135 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 20 58.716070 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 21 60.775980 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > > > > eth1 > > 1 0.000000 fe80::215:ff:fe1f:20a6 ff02::2 ICMPv6 Router solicitation > 2 25.983879 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 3 30.983864 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 4 32.949057 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 5 32.952404 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 6 32.957215 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 7 32.960893 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 8 32.964222 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 9 32.970023 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 10 32.973868 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 11 32.977056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 12 32.981455 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 13 32.985056 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 14 32.988717 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > 15 44.983895 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 16 54.983846 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe2640e1c > 17 57.199856 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 18 58.967801 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 19 60.039785 Wistron_ae:7e:4c Broadcast ARP Who has 169.254.7.81? Tell 0.0.0.0 > 20 62.039897 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 21 64.039860 Wistron_ae:7e:4c Broadcast ARP Gratuitous ARP for 169.254.7.81 (Request) > 22 66.107737 Wistron_ae:7e:4c Broadcast ARP Who has 195.130.129.165? Tell 169.254.7.81 > 23 66.164183 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<20> > 24 66.164203 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<03> > 25 66.164222 169.254.7.81 169.254.255.255 NBNS Registration NB BACARDI<00> > 26 66.164241 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<00> > 27 66.164258 169.254.7.81 169.254.255.255 NBNS Registration NB MSHOME<1e> > 28 66.164314 169.254.7.81 169.254.255.255 BROWSER Host Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Potential Browser, Unknown server type:23 > > > > You can see the DHCP discovers, but nobody's answering > > > > richardvoigt@gmail.com <mailto:richardvoigt@gmail.com> schreef: >> Do some packet monitoring on your wireless network to see if the >> DHCP request is going out over the air... your problems stem from >> not getting a DHCP address. At first I thought the address given >> to eth1 might be interfering with br0... but it seems not. >> >> On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht >> <jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: >> >> >> >> 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? >> >> > [-- Attachment #2: Type: text/html, Size: 21004 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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:41 ` Jochen Hebbrecht 0 siblings, 2 replies; 47+ messages in thread From: Ross Vandegrift @ 2009-04-29 16:26 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On Wed, Apr 29, 2009 at 06:16:14PM +0200, Jochen Hebbrecht wrote: > No, the DHCP server gives addresses to every MAC address that is possible. Is eth0 plugged in? Does it work if you statically assign an IP to br0? Ross > > So this is the current situation: > > jochus@Bacardi ~ $ sudo brctl show br0 > bridge name bridge id STP enabled interfaces > br0 8000.000ae4ae7e4c no eth0 > > eth1 > > jochus@Bacardi ~ $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > 0 br0 > 0.0.0.0 0.0.0.0 0.0.0.0 U 1000 > 0 0 br0 > > > I also found this thread: > http://www.linuxquestions.org/questions/debian-26/howto-bridge-wireless-and-wired-network-interfaces-369455/, > but that solution didn't work either. I'm not receiving any DHCP offers on > eth1 > > I guess I'm stuck with it, and returning to windows is the best solution > now :-) > > > > richardvoigt@gmail.com schreef: > >Does your DHCP server only give out addresses to specific MAC > >addresses? Turning on bridge mode probably results in using the MAC > >address of eth0, rather than eth1 which had been successfully getting > >a DHCP assignment? > > > >I had actually meant for you to run packet capture from some other > >node on the wireless, to make sure the DHCP discover actually went out > >the radio. But you clearly are joined properly. > > > >So check for any sort of MAC-based security in the DHCP server. > > > >On Tue, Apr 28, 2009 at 4:16 PM, Jochen Hebbrecht > ><jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: > > > > Richard, > > > > After rebooting a second time, eth1 isn't appearing in the routing > > tabel any longer. The bridge seems to be working perfectly now! > > However, I'm not able to retreive any DHCP offers. > > > > I did some packet monitoring: > > > > br0 > > > > 1 0.000000000 fe80::20a:e4ff:feae:7e4c ff02::2 ICMPv6 > > Router solicitation > > 2 24.824098000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0xa117a72 > > 3 28.824043000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0xa117a72 > > 4 33.685106000 192.168.1.1 239.255.255.250 SSDP NOTIFY * > > HTTP/1.1 5 33.688946000 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 6 33.692700000 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 7 33.698081000 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 8 33.701656000 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 > > 33.705492000 192.168.1.1 239.255.255.250 SSDP NOTIFY * > > HTTP/1.1 10 33.708885000 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 11 33.712502000 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 12 33.716242000 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 13 33.719929000 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 14 > > 38.824050000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0xa117a72 > > 15 48.824039000 0.0.0.0 255.255.255.255 DHCP DHCP > > Discover - Transaction ID 0xa117a72 > > 16 56.768033000 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 17 57.992048000 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 18 59.019954000 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 19 61.020124000 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 20 62.004532000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<20> > > 21 62.004582000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<03> > > 22 62.004615000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<00> > > 23 62.004647000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<00> > > 24 62.004679000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<1e> > > 25 62.004775000 169.254.7.81 169.254.255.255 BROWSER Host > > Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix > > Server, NT Workstation, NT Server, Potential Browser, Unknown server > > type:23 > > 26 63.023921000 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 27 64.003996000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<20> > > 28 64.004033000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<03> > > 29 64.004054000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<00> > > 30 64.004075000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<00> > > 31 64.004097000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<1e> > > 32 64.004156000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<20> > > 33 64.004179000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<03> > > 34 64.004200000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<00> > > 35 64.004220000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<00> > > 36 64.004240000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<1e> > > 37 65.127895000 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.129.165? Tell 169.254.7.81 > > 38 66.004121000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<20> > > 39 66.004177000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<03> > > 40 66.004197000 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<00> > > 41 66.004219000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<00> > > 42 66.004239000 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<1e> > > 43 66.127931000 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.129.165? Tell 169.254.7.81 > > 44 67.127989000 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.129.165? Tell 169.254.7.81 > > 45 70.127967000 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.130.165? Tell 169.254.7.81 > > 46 71.128025000 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.130.165? Tell 169.254.7.81 > > > > > > > > > > eth0 > > > > 1 0.000000 Wistron_ae:7e:4c Broadcast ARP Who > > has 192.168.1.1? Tell 192.168.1.112 > > 2 19.840146 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0x8537ad48 > > 3 24.840168 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0x8537ad48 > > 4 38.840099 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0x8537ad48 > > 5 45.513321 192.168.1.1 239.255.255.250 SSDP NOTIFY * > > HTTP/1.1 6 45.516537 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 7 45.520384 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 8 45.524058 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 45.527325 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 10 > > 45.530872 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > > 11 45.534676 192.168.1.1 239.255.255.250 SSDP NOTIFY > > * HTTP/1.1 12 45.538019 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 13 45.541774 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 14 45.545417 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 15 45.549231 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 16 > > 51.412036 Wistron_ae:7e:4c Broadcast ARP Who has > > 169.254.7.81? Tell 0.0.0.0 > > 17 53.360036 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 18 54.716034 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 19 56.716135 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 20 58.716070 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 21 60.775980 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.129.165? Tell 169.254.7.81 > > > > > > > > eth1 > > > > 1 0.000000 fe80::215:ff:fe1f:20a6 ff02::2 ICMPv6 Router > > solicitation > > 2 25.983879 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0xe2640e1c > > 3 30.983864 0.0.0.0 255.255.255.255 DHCP DHCP Discover - > > Transaction ID 0xe2640e1c > > 4 32.949057 192.168.1.1 239.255.255.250 SSDP NOTIFY * > > HTTP/1.1 5 32.952404 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 6 32.957215 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 7 32.960893 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 8 32.964222 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 9 > > 32.970023 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 > > 10 32.973868 192.168.1.1 239.255.255.250 SSDP NOTIFY > > * HTTP/1.1 11 32.977056 192.168.1.1 239.255.255.250 SSDP > > NOTIFY * HTTP/1.1 12 32.981455 192.168.1.1 239.255.255.250 > > SSDP NOTIFY * HTTP/1.1 13 32.985056 192.168.1.1 > > 239.255.255.250 SSDP NOTIFY * HTTP/1.1 14 32.988717 > > 192.168.1.1 239.255.255.250 SSDP NOTIFY * HTTP/1.1 15 > > 44.983895 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction > > ID 0xe2640e1c > > 16 54.983846 0.0.0.0 255.255.255.255 DHCP DHCP > > Discover - Transaction ID 0xe2640e1c > > 17 57.199856 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 18 58.967801 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 19 60.039785 Wistron_ae:7e:4c Broadcast ARP > > Who has 169.254.7.81? Tell 0.0.0.0 > > 20 62.039897 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 21 64.039860 Wistron_ae:7e:4c Broadcast ARP > > Gratuitous ARP for 169.254.7.81 (Request) > > 22 66.107737 Wistron_ae:7e:4c Broadcast ARP > > Who has 195.130.129.165? Tell 169.254.7.81 > > 23 66.164183 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<20> > > 24 66.164203 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<03> > > 25 66.164222 169.254.7.81 169.254.255.255 NBNS > > Registration NB BACARDI<00> > > 26 66.164241 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<00> > > 27 66.164258 169.254.7.81 169.254.255.255 NBNS > > Registration NB MSHOME<1e> > > 28 66.164314 169.254.7.81 169.254.255.255 BROWSER Host > > Announcement BACARDI, Workstation, Server, Print Queue Server, Xenix > > Server, NT Workstation, NT Server, Potential Browser, Unknown server > > type:23 > > > > > > > > You can see the DHCP discovers, but nobody's answering > > > > > > > > richardvoigt@gmail.com <mailto:richardvoigt@gmail.com> schreef: > >> Do some packet monitoring on your wireless network to see if the > >> DHCP request is going out over the air... your problems stem from > >> not getting a DHCP address. At first I thought the address given > >> to eth1 might be interfering with br0... but it seems not. > >> > >> On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht > >> <jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: > >> > >> > >> > >> 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? > >> > >> > > -- Ross Vandegrift ross@kallisti.us "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-29 16:26 ` Ross Vandegrift @ 2009-04-29 16:40 ` Jochen Hebbrecht 2009-04-29 16:53 ` Ross Vandegrift 2009-04-29 16:41 ` Jochen Hebbrecht 1 sibling, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-29 16:40 UTC (permalink / raw) To: Ross Vandegrift; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 395 bytes --] Ross Vandegrift schreef: > On Wed, Apr 29, 2009 at 06:16:14PM +0200, Jochen Hebbrecht wrote: > >> No, the DHCP server gives addresses to every MAC address that is possible. >> > > Is eth0 plugged in? Does it work if you statically assign an IP to br0? > > Ross > > Yes, it is plugged in ( Ubuntu says: link is ready ). I also tried statically, but no improvements :-( ... Jochen [-- Attachment #2: Type: text/html, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-29 16:40 ` Jochen Hebbrecht @ 2009-04-29 16:53 ` Ross Vandegrift 2009-04-29 21:21 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Ross Vandegrift @ 2009-04-29 16:53 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On Wed, Apr 29, 2009 at 06:40:25PM +0200, Jochen Hebbrecht wrote: > Yes, it is plugged in ( Ubuntu says: link is ready ). > I also tried statically, but no improvements :-( ... Is your wireless access point also bridging between the wired and the wireless? If so, then you have two bridges circulating packets between the wired and wireless networks. You should either turn on STP so loops can be detected and prevented or unplug eth0 to simulate that scenario. Ross -- Ross Vandegrift ross@kallisti.us "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-29 16:53 ` Ross Vandegrift @ 2009-04-29 21:21 ` Jochen Hebbrecht 2009-04-30 4:18 ` richardvoigt 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-29 21:21 UTC (permalink / raw) To: Ross Vandegrift; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 794 bytes --] Ross Vandegrift schreef: > On Wed, Apr 29, 2009 at 06:40:25PM +0200, Jochen Hebbrecht wrote: > >> Yes, it is plugged in ( Ubuntu says: link is ready ). >> I also tried statically, but no improvements :-( ... >> > > Is your wireless access point also bridging between the wired and the > wireless? If so, then you have two bridges circulating packets > between the wired and wireless networks. > What do you mean with "wireless access point"? My eth1? I think the bridge is ok. In one of my previous mails, you see the sniffer logging DHCP discovers on eth0 AND eth1 > > You should either turn on STP so loops can be detected and prevented > or unplug eth0 to simulate that scenario. > If I unplug eth0, the situation stays the same. Bridge is ok. But no IP received ... [-- Attachment #2: Type: text/html, Size: 1396 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-29 21:21 ` Jochen Hebbrecht @ 2009-04-30 4:18 ` richardvoigt 2009-04-30 6:30 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-04-30 4:18 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 1362 bytes --] On Wed, Apr 29, 2009 at 9:21 PM, Jochen Hebbrecht <jochenhebbrecht@gmail.com > wrote: > Ross Vandegrift schreef: > > On Wed, Apr 29, 2009 at 06:40:25PM +0200, Jochen Hebbrecht wrote: > > > Yes, it is plugged in ( Ubuntu says: link is ready ). > I also tried statically, but no improvements :-( ... > > > Is your wireless access point also bridging between the wired and the > wireless? If so, then you have two bridges circulating packets > between the wired and wireless networks. > > > What do you mean with "wireless access point"? My eth1? I think the bridge > is ok. In one of my previous mails, you see the sniffer logging DHCP > discovers on eth0 AND eth1 > That's at the IP stack. At the firmware level, most wireless cards will refuse to transmit/receive packets with other MAC addresses, making them useless for AP or bridging. Yours is apparently not one of those since bridging works in Windows (or else the Windows bridge code does transparent routing w/MAC address replacement, rather like NAT or PAT but working at layer 2 instead of 3). That's why I suggested testing for the DHCP discover on a different wireless node. > > You should either turn on STP so loops can be detected and prevented > or unplug eth0 to simulate that scenario. > > If I unplug eth0, the situation stays the same. Bridge is ok. But no IP > received ... > [-- Attachment #2: Type: text/html, Size: 2246 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-30 4:18 ` richardvoigt @ 2009-04-30 6:30 ` Jochen Hebbrecht 2009-04-30 21:54 ` Nicolas de Pesloüan 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-30 6:30 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge 2009/4/30 richardvoigt@gmail.com <richardvoigt@gmail.com>: > > > On Wed, Apr 29, 2009 at 9:21 PM, Jochen Hebbrecht > <jochenhebbrecht@gmail.com> wrote: >> >> Ross Vandegrift schreef: >> >> On Wed, Apr 29, 2009 at 06:40:25PM +0200, Jochen Hebbrecht wrote: >> >> >> Yes, it is plugged in ( Ubuntu says: link is ready ). >> I also tried statically, but no improvements :-( ... >> >> >> Is your wireless access point also bridging between the wired and the >> wireless? If so, then you have two bridges circulating packets >> between the wired and wireless networks. >> >> >> What do you mean with "wireless access point"? My eth1? I think the bridge >> is ok. In one of my previous mails, you see the sniffer logging DHCP >> discovers on eth0 AND eth1 > > That's at the IP stack. At the firmware level, most wireless cards will > refuse to transmit/receive packets with other MAC addresses, making them > useless for AP or bridging. Yours is apparently not one of those since > bridging works in Windows (or else the Windows bridge code does transparent > routing w/MAC address replacement, rather like NAT or PAT but working at > layer 2 instead of 3). > > That's why I suggested testing for the DHCP discover on a different wireless > node. Hmm, can you explain to me how I can try to use a different wireless node? ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-30 6:30 ` Jochen Hebbrecht @ 2009-04-30 21:54 ` Nicolas de Pesloüan 2009-05-02 13:15 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-04-30 21:54 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge > 2009/4/30 richardvoigt@gmail.com <richardvoigt@gmail.com>: >> >> That's at the IP stack. At the firmware level, most wireless cards will >> refuse to transmit/receive packets with other MAC addresses, making them >> useless for AP or bridging. Yours is apparently not one of those since >> bridging works in Windows (or else the Windows bridge code does transparent >> routing w/MAC address replacement, rather like NAT or PAT but working at >> layer 2 instead of 3). >> >> That's why I suggested testing for the DHCP discover on a different wireless >> node. 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. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-02 13:15 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge 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 ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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:28 ` Jochen Hebbrecht 0 siblings, 2 replies; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-03 17:46 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht wrote: > Nicolas de Pesloüan schreef: >> >> Can you also explain why you are trying to use bridge ? > 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). Ok, now we understand what you are trying to do. In particular, I assume the DHCP server is on the subnet of location B (or behind a router connected on this subnet), so the expected DHCP offer will come from the wire interface (eth0) and definitely not from the wireless interface (eth1). > 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. Let's try a step-by-step bridge configuration : 1/ Try to setup a non-bridge configuration and ensure you successfully get a DHCP answer using eth0. auto eth0 iface eth0 inet dhcp #auto eth1 #iface eth1 inet dhcp #wpa-driver wext #wpa-ssid ##SSID## #wpa-ap-scan 1 #wpa-proto RSN #wpa-pairwise CCMP #wpa-group CCMP #wpa-key-mgmt WPA-PSK #wpa-psk ##PSK KEY## #auto br0 #iface br0 inet dhcp #bridge_ports eth0 eth1 2/ Try to setup a bridge with only eth0 (wire interface) and ensure this work well, using a static IP address. #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet static bridge_ports eth0 address 192.168.1.111 netmask 255.255.255.0 3/ Try to setup a bridge with only eth0 (wire interface) and ensure this work well, using DHCP. #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 4/ Then add the eth1 (wireless interface). #auto eth0 iface eth0 inet manual auto eth1 iface eth1 inet manual wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## # The wpa-bridge option is expected to instruct wpa_supplicant # to listen on br0 instead of eth1. This is a workaround which # should net be necessary after kernel 2.6.28 or 2.6.29, for # as far as I remember. wpa-bridge br0 auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 5/ If the previous fail, can you please test the following configuration: #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 # the wpa-iface option is expected to instruct wpa_supplicant # to setup the wifi link using eth1 instead of br0. wpa-iface eth1 wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## # The wpa-bridge option is expected to instruct wpa_supplicant # to listen on br0 instead of eth1. This is a workaround which # should net be necessary after kernel 2.6.28 or 2.6.29, for # as far as I remember. wpa-bridge br0 6/ If all this fail, please try the above (#5), without the wpa-bridge option. 7/ If all this fail... let's try something really different (and totally out of topic for the bridge list, sorry guys) : Why do you need location A to be in the same subnet as the printer in location B ? The Ubuntu server in location B might be setup as a normal router (with two different IP in two different subnets). Then, the default route on the printer should be set to the LAN IP address of the ubuntu server. If you cannot change de default route for the printer, then add a route on the router of this subnet. This new route should ask the router to forward packet for the subnet of location A through the Ubuntu server. If you cannot change de routing table in this router, then I suggest you try some sort of NAT configuration to arrange for all host in location A to be NATted to an IP address of location B subnet (using proxy ARP). Nicolas. > 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 :-( ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 1 sibling, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-05-04 3:59 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge, Jochen Hebbrecht [-- Attachment #1: Type: text/plain, Size: 1706 bytes --] On Sun, May 3, 2009 at 12:46 PM, Nicolas de Pesloüan < nicolas.2p.debian@free.fr> wrote: > Jochen Hebbrecht wrote: > > Nicolas de Pesloüan schreef: > >> > >> Can you also explain why you are trying to use bridge ? > > > 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). > > Ok, now we understand what you are trying to do. In particular, I assume > the DHCP server is on the subnet of location B (or behind a router > connected on this subnet), so the expected DHCP offer will come from the > wire interface (eth0) and definitely not from the wireless interface > (eth1). Looking at "router" in the provided diagram, plus the placement of A and B, I am led to believe that location A is the primary network providing DHCP and outbound access. Furthermore, Jochen was getting a DHCP assignment over his wireless interface before he tried to enable bridging. Your suggestion of configuration as a router could work. But NAT would not if A is the primary location, because the printer would no longer have a address visible to location A. [-- Attachment #2: Type: text/html, Size: 2269 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-04 3:59 ` richardvoigt @ 2009-05-04 19:29 ` Jochen Hebbrecht 0 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-04 19:29 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 1200 bytes --] richardvoigt@gmail.com schreef: > > > On Sun, May 3, 2009 at 12:46 PM, Nicolas de Pesloüan > <nicolas.2p.debian@free.fr <mailto:nicolas.2p.debian@free.fr>> wrote: > > > > Ok, now we understand what you are trying to do. In particular, I > assume > the DHCP server is on the subnet of location B (or behind a router > connected on this subnet), so the expected DHCP offer will come > from the > wire interface (eth0) and definitely not from the wireless interface > (eth1). > > > > Looking at "router" in the provided diagram, plus the placement of A > and B, I am led to believe that location A is the primary network > providing DHCP and outbound access. Furthermore, Jochen was getting a > DHCP assignment over his wireless interface before he tried to enable > bridging. > > Your suggestion of configuration as a router could work. But NAT > would not if A is the primary location, because the printer would no > longer have a address visible to location A. Indeed, location A is my primary network which provides DHCP. And yes, you are correct with your last sentence. The printer should be visible for location A too :-) [-- Attachment #2: Type: text/html, Size: 1899 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-03 17:46 ` Nicolas de Pesloüan 2009-05-04 3:59 ` richardvoigt @ 2009-05-04 19:28 ` Jochen Hebbrecht 2009-05-04 19:34 ` Nicolas de Pesloüan 2009-05-04 20:07 ` Nicolas de Pesloüan 1 sibling, 2 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-04 19:28 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > Ok, now we understand what you are trying to do. In particular, I > assume the DHCP server is on the subnet of location B (or behind a > router connected on this subnet), so the expected DHCP offer will come > from the wire interface (eth0) and definitely not from the wireless > interface (eth1). > Maybe my picture isn't very clear, but my WAN access is on location A. There's a router which receives an ip from the ISP. On the other side, I'm having a 192.168.1.0/24 network > Let's try a step-by-step bridge configuration : > > 1/ Try to setup a non-bridge configuration and ensure you successfully > get a DHCP answer using eth0. > > auto eth0 > iface eth0 inet dhcp > > #auto eth1 > #iface eth1 inet dhcp > #wpa-driver wext > #wpa-ssid ##SSID## > #wpa-ap-scan 1 > #wpa-proto RSN > #wpa-pairwise CCMP > #wpa-group CCMP > #wpa-key-mgmt WPA-PSK > #wpa-psk ##PSK KEY## > > #auto br0 > #iface br0 inet dhcp > #bridge_ports eth0 eth1 I tried this: $ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth1 iface eth1 inet dhcp wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## This configuration works fine. I'm receiving a DHCP offer from my router (in location A) > > 2/ Try to setup a bridge with only eth0 (wire interface) and ensure > this work well, using a static IP address. > > #auto eth0 > iface eth0 inet manual > > #auto eth1 > iface eth1 inet manual > > auto br0 > iface br0 inet static > bridge_ports eth0 > address 192.168.1.111 > netmask 255.255.255.0 $ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth1 iface eth1 inet manual wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## auto br0 iface br0 inet static bridge_ports eth1 address 192.168.1.111 netmask 255.255.255.0 gateway 192.168.1.1 $ sudo /etc/init.d/networking restart * Reconfiguring network interfaces... Waiting for br0 to get ready (MAXWAIT is 32 seconds). [ OK ] $ route -n 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 br0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0 $ sudo brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.0015001f20a6 no eth1 $ ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:7 errors:82 dropped:84 overruns:0 frame:0 TX packets:1 errors:0 dropped:19 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1056452 (1.0 MB) TX bytes:149964 (146.4 KB) Interrupt:21 Base address:0xa000 Memory:c8006000-c8006fff $ ifconfig br0 br0 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:1350 (1.3 KB) $ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.111 icmp_seq=2 Destination Host Unreachable From 192.168.1.111 icmp_seq=3 Destination Host Unreachable From 192.168.1.111 icmp_seq=5 Destination Host Unreachable From 192.168.1.111 icmp_seq=6 Destination Host Unreachable So here it goes wrong. I didn't execute any other steps as step 2 fails :-( ... ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 1 sibling, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-04 19:34 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht a écrit : > > > Nicolas de Pesloüan schreef: >> Ok, now we understand what you are trying to do. In particular, I >> assume the DHCP server is on the subnet of location B (or behind a >> router connected on this subnet), so the expected DHCP offer will come >> from the wire interface (eth0) and definitely not from the wireless >> interface (eth1). >> > Maybe my picture isn't very clear, but my WAN access is on location A. > There's a router which receives an ip from the ISP. On the other side, > I'm having a 192.168.1.0/24 network I'm no more really sure I understand your configuration. The server you are curently trying to setup as a bridge is located in location B (UBUNTU SERVER) and has two interfaces : eth0 (ethernet) and eth1 (wifi). Am I right ? >> Let's try a step-by-step bridge configuration : >> >> 1/ Try to setup a non-bridge configuration and ensure you successfully >> get a DHCP answer using eth0. >> >> auto eth0 >> iface eth0 inet dhcp >> >> #auto eth1 >> #iface eth1 inet dhcp >> #wpa-driver wext >> #wpa-ssid ##SSID## >> #wpa-ap-scan 1 >> #wpa-proto RSN >> #wpa-pairwise CCMP >> #wpa-group CCMP >> #wpa-key-mgmt WPA-PSK >> #wpa-psk ##PSK KEY## >> >> #auto br0 >> #iface br0 inet dhcp >> #bridge_ports eth0 eth1 > I tried this: > > $ cat /etc/network/interfaces > auto lo > iface lo inet loopback > > auto eth1 > iface eth1 inet dhcp > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > > This configuration works fine. I'm receiving a DHCP offer from my router > (in location A) >> >> 2/ Try to setup a bridge with only eth0 (wire interface) and ensure >> this work well, using a static IP address. >> >> #auto eth0 >> iface eth0 inet manual >> >> #auto eth1 >> iface eth1 inet manual >> >> auto br0 >> iface br0 inet static >> bridge_ports eth0 >> address 192.168.1.111 >> netmask 255.255.255.0 > $ cat /etc/network/interfaces > auto lo > iface lo inet loopback > > auto eth1 > iface eth1 inet manual > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > > auto br0 > iface br0 inet static > bridge_ports eth1 > address 192.168.1.111 > netmask 255.255.255.0 > gateway 192.168.1.1 > > $ sudo /etc/init.d/networking restart > * Reconfiguring network > interfaces... > Waiting for br0 to get ready (MAXWAIT is 32 seconds). > > [ OK ] > $ route -n > 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 br0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0 > > $ sudo brctl show br0 > bridge name bridge id STP enabled interfaces > br0 8000.0015001f20a6 no eth1 > > $ ifconfig eth1 > eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 inet6 > addr: fe80::215:ff:fe1f:20a6/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:7 errors:82 dropped:84 overruns:0 frame:0 > TX packets:1 errors:0 dropped:19 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1056452 (1.0 MB) TX bytes:149964 (146.4 KB) > Interrupt:21 Base address:0xa000 Memory:c8006000-c8006fff > > $ ifconfig br0 > br0 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:1350 (1.3 KB) > > $ ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > From 192.168.1.111 icmp_seq=2 Destination Host Unreachable > From 192.168.1.111 icmp_seq=3 Destination Host Unreachable > From 192.168.1.111 icmp_seq=5 Destination Host Unreachable > From 192.168.1.111 icmp_seq=6 Destination Host Unreachable > > So here it goes wrong. I didn't execute any other steps as step 2 fails > :-( ... > > ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-04 19:34 ` Nicolas de Pesloüan @ 2009-05-04 19:42 ` Jochen Hebbrecht 0 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-04 19:42 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > Jochen Hebbrecht a écrit : >> >> >> Nicolas de Pesloüan schreef: >>> Ok, now we understand what you are trying to do. In particular, I >>> assume the DHCP server is on the subnet of location B (or behind a >>> router connected on this subnet), so the expected DHCP offer will >>> come from the wire interface (eth0) and definitely not from the >>> wireless interface (eth1). >>> >> Maybe my picture isn't very clear, but my WAN access is on location >> A. There's a router which receives an ip from the ISP. On the other >> side, I'm having a 192.168.1.0/24 network > > I'm no more really sure I understand your configuration. > > The server you are curently trying to setup as a bridge is located in > location B (UBUNTU SERVER) and has two interfaces : eth0 (ethernet) > and eth1 (wifi). > > Am I right ? Yes, that's totally correct. I want to receive an IP on my eth1 so my UBUNTU server is in the same subnet as desktop A and notebook A. By bridging eth0 and eth1 of UBUNTU SERVER, the IP packets on eth0 will be forwarded on eth1 to the router, so my printer can ask for a DHCP OFFER message, by sending a DHCP DISCOVER on the switch. That switch will send the message to eth0 of UBUNTU SERVER whichs forwards (bridging!) the packet on eth1 to the router. The router sends a DHCP OFFER back to eth1 of UBUNTU SERVER, which eventually forwards (bridging!) the message back to switch (and so on to the printer :-)) ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-04 19:28 ` Jochen Hebbrecht 2009-05-04 19:34 ` Nicolas de Pesloüan @ 2009-05-04 20:07 ` Nicolas de Pesloüan 2009-05-04 21:06 ` Jochen Hebbrecht 1 sibling, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-04 20:07 UTC (permalink / raw) To: Jochen Hebbrecht, bridge Jochen Hebbrecht wrote: > Maybe my picture isn't very clear, but my WAN access is on location A. > There's a router which receives an ip from the ISP. On the other side, > I'm having a 192.168.1.0/24 network > $ cat /etc/network/interfaces > auto lo > iface lo inet loopback > > auto eth1 > iface eth1 inet manual > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > > auto br0 > iface br0 inet static > bridge_ports eth1 > address 192.168.1.111 > netmask 255.255.255.0 > gateway 192.168.1.1 > > $ ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > From 192.168.1.111 icmp_seq=2 Destination Host Unreachable > From 192.168.1.111 icmp_seq=3 Destination Host Unreachable > From 192.168.1.111 icmp_seq=5 Destination Host Unreachable > From 192.168.1.111 icmp_seq=6 Destination Host Unreachable > > So here it goes wrong. I didn't execute any other steps as step 2 fails I think that the "Destination Host Unreachable" is caused by some sort of "down link", because wpa_supplicant failed to establish the wifi link. When eth1 is part of the br0, packets received on eth1 is "forwarded" to br0 and not available on eth1. So wpa_supplicant must be instructed to listen for incoming packets on br0, not on eth1. Can you try the exact same configuration, adding wpa-bridge br0 in the eth1 stanza, to inform wpa_supplicant where to listen from ? auto lo iface lo inet loopback auto eth1 iface eth1 inet manual wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## wpa-bridge br0 <--- HERE. auto br0 iface br0 inet static bridge_ports eth1 address 192.168.1.111 netmask 255.255.255.0 gateway 192.168.1.1 If this fail, please provide the output of i_w_config eth1 and arp -an. Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 6:20 ` Nicolas de Pesloüan 0 siblings, 2 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-04 21:06 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > > I think that the "Destination Host Unreachable" is caused by some sort > of "down link", because wpa_supplicant failed to establish the wifi > link. When eth1 is part of the br0, packets received on eth1 is > "forwarded" to br0 and not available on eth1. So wpa_supplicant must > be instructed to listen for incoming packets on br0, not on eth1. > > Can you try the exact same configuration, adding wpa-bridge br0 in the > eth1 stanza, to inform wpa_supplicant where to listen from ? > > auto lo > iface lo inet loopback > > auto eth1 > iface eth1 inet manual > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > wpa-bridge br0 <--- HERE. > > auto br0 > iface br0 inet static > bridge_ports eth1 > address 192.168.1.111 > netmask 255.255.255.0 > gateway 192.168.1.1 I changed the configuration and restarted the networking daemon. I'm getting this output jochus@Bacardi ~ $ sudo /etc/init.d/networking restart * Reconfiguring network interfaces... ioctl[SIOCGIFINDEX]: No such device Failed to open l2_packet connection for the bridge interface 'br0' wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Waiting for br0 to get ready (MAXWAIT is 32 seconds). I'm worried about the wpa_supplicant error. The file is present: jochus@Bacardi ~ $ ls -al /sbin/wpa_supplicant -rwxr-xr-x 1 root root 319812 2008-03-12 22:28 /sbin/wpa_supplicant The output of ifconfig: jochus@Bacardi ~ $ route -n 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 br0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0 jochus@Bacardi ~ $ ifconfig br0 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:720 (720.0 B) eth0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Base address:0xc000 eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:5255 errors:12 dropped:12 overruns:0 frame:0 TX packets:466 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:912108 (890.7 KB) TX bytes:113643 (110.9 KB) Interrupt:21 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:1974 errors:0 dropped:0 overruns:0 frame:0 TX packets:1974 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:101385 (99.0 KB) TX bytes:101385 (99.0 KB) The output of iwconfig of eth1 jochus@Bacardi ~ $ iwconfig eth1 eth1 unassociated ESSID:"Jochus" Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:146 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 The output of arp -an: jochus@Bacardi ~ $ arp -an ? (192.168.1.1) at <incomplete> on br0 ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 6:20 ` Nicolas de Pesloüan 1 sibling, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-05-04 23:33 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 5173 bytes --] On Mon, May 4, 2009 at 4:06 PM, Jochen Hebbrecht <jochenhebbrecht@gmail.com>wrote: > Nicolas de Pesloüan schreef: > > > > I think that the "Destination Host Unreachable" is caused by some sort > > of "down link", because wpa_supplicant failed to establish the wifi > > link. When eth1 is part of the br0, packets received on eth1 is > > "forwarded" to br0 and not available on eth1. So wpa_supplicant must > > be instructed to listen for incoming packets on br0, not on eth1. > > > > Can you try the exact same configuration, adding wpa-bridge br0 in the > > eth1 stanza, to inform wpa_supplicant where to listen from ? > > > > auto lo > > iface lo inet loopback > > > > auto eth1 > > iface eth1 inet manual > > wpa-driver wext > > wpa-ssid ##SSID## > > wpa-ap-scan 1 > > wpa-proto RSN > > wpa-pairwise CCMP > > wpa-group CCMP > > wpa-key-mgmt WPA-PSK > > wpa-psk ##PSK KEY## > > wpa-bridge br0 <--- HERE. > > > > auto br0 > > iface br0 inet static > > bridge_ports eth1 > > address 192.168.1.111 > > netmask 255.255.255.0 > > gateway 192.168.1.1 > I changed the configuration and restarted the networking daemon. I'm > getting this output > > jochus@Bacardi ~ $ sudo /etc/init.d/networking restart > * Reconfiguring network > interfaces... > ioctl[SIOCGIFINDEX]: No such device > Failed to open l2_packet connection for the bridge interface 'br0' > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 > > Waiting for br0 to get ready (MAXWAIT is 32 seconds). > Surely things are getting run in the wrong order. First, the bridge should be created. Then, the interfaces should be configured, joined to the bridge, and brought up. Then wpa_supplicant should run. After wpa_supplicant associates to the wireless access point, then dhcp should succeed. It seems like ubuntu's network scripts don't create the bridge until too late. > > > I'm worried about the wpa_supplicant error. The file is present: > > jochus@Bacardi ~ $ ls -al /sbin/wpa_supplicant > -rwxr-xr-x 1 root root 319812 2008-03-12 22:28 /sbin/wpa_supplicant > > The output of ifconfig: > > jochus@Bacardi ~ $ route -n > 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 br0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0 > > jochus@Bacardi ~ $ ifconfig > br0 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:720 (720.0 B) > > eth0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:20 Base address:0xc000 > > eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:5255 errors:12 dropped:12 overruns:0 frame:0 > TX packets:466 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:912108 (890.7 KB) TX bytes:113643 (110.9 KB) > Interrupt:21 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:1974 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1974 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:101385 (99.0 KB) TX bytes:101385 (99.0 KB) > > The output of iwconfig of eth1 > > jochus@Bacardi ~ $ iwconfig eth1 > eth1 unassociated ESSID:"Jochus" > Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated > Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0 > Retry limit:7 RTS thr:off Fragment thr:off > Power Management:off > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:146 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > The output of arp -an: > > jochus@Bacardi ~ $ arp -an > ? (192.168.1.1) at <incomplete> on br0 > > _______________________________________________ > Bridge mailing list > Bridge@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/bridge > [-- Attachment #2: Type: text/html, Size: 6494 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-04 23:33 ` richardvoigt @ 2009-05-05 5:49 ` Nicolas de Pesloüan 2009-05-05 16:59 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-05 5:49 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge richardvoigt@gmail.com wrote: > > On Mon, May 4, 2009 at 4:06 PM, Jochen Hebbrecht > <jochenhebbrecht@gmail.com <mailto:jochenhebbrecht@gmail.com>> wrote: > > I changed the configuration and restarted the networking daemon. I'm > getting this output > > jochus@Bacardi ~ $ sudo /etc/init.d/networking restart > * Reconfiguring network > interfaces... > ioctl[SIOCGIFINDEX]: No such device > Failed to open l2_packet connection for the bridge interface 'br0' > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return > code 1 > > Waiting for br0 to get ready (MAXWAIT is 32 seconds). > > > Surely things are getting run in the wrong order. > > First, the bridge should be created. > Then, the interfaces should be configured, joined to the bridge, and > brought up. > Then wpa_supplicant should run. > After wpa_supplicant associates to the wireless access point, then dhcp > should succeed. > > It seems like ubuntu's network scripts don't create the bridge until too > late. I agree with Richard. Jochen, can you please try the following configuration (step #5 in my previous e-mail) ? #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 # the wpa-iface option is expected to instruct wpa_supplicant # to setup the wifi link using eth1 instead of br0. wpa-iface eth1 wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK KEY## # The wpa-bridge option is expected to instruct wpa_supplicant # to listen on br0 instead of eth1. wpa-bridge br0 And if this fail, please try the same configuration, without the wpa-bridge option. If both fail, please provide the list of files in /etc/network/if*/*. Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 5:49 ` Nicolas de Pesloüan @ 2009-05-05 16:59 ` Jochen Hebbrecht 0 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-05 16:59 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > I agree with Richard. > > Jochen, can you please try the following configuration (step #5 in my > previous e-mail) ? > > #auto eth0 > iface eth0 inet manual > > #auto eth1 > iface eth1 inet manual > > auto br0 > iface br0 inet dhcp > bridge_ports eth0 eth1 > # the wpa-iface option is expected to instruct wpa_supplicant > # to setup the wifi link using eth1 instead of br0. > wpa-iface eth1 > wpa-driver wext > wpa-ssid ##SSID## > wpa-ap-scan 1 > wpa-proto RSN > wpa-pairwise CCMP > wpa-group CCMP > wpa-key-mgmt WPA-PSK > wpa-psk ##PSK KEY## > # The wpa-bridge option is expected to instruct wpa_supplicant > # to listen on br0 instead of eth1. > wpa-bridge br0 > Nicoloas, First of all, thanks for your effort and time. I'm really appreciating this and I'm really willing to let this bridge works. So I tried what you suggested here: $ cat /etc/network/interfaces #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 # the wpa-iface option is expected to instruct wpa_supplicant # to setup the wifi link using eth1 instead of br0. wpa-iface eth1 wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK## # The wpa-bridge option is expected to instruct wpa_supplicant # to listen on br0 instead of eth1. wpa-bridge br0 $ sudo /etc/init.d/networking restart * Reconfiguring network interfaces... Waiting for br0 to get ready (MAXWAIT is 32 seconds). Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/br0/00:0a:e4:ae:7e:4c Sending on LPF/br0/00:0a:e4:ae:7e:4c Sending on Socket/fallback DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 6 No DHCPOFFERS received. No working leases in persistent database - sleeping. [ OK ] jochus@Bacardi ~ $ ifconfig 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:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:387 (387.0 B) TX bytes:5743 (5.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 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Base address:0xc000 eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:42 dropped:42 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:277199 (270.7 KB) TX bytes:95538 (93.2 KB) Interrupt:21 Base address:0xc000 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:1942 errors:0 dropped:0 overruns:0 frame:0 TX packets:1942 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:97578 (95.2 KB) TX bytes:97578 (95.2 KB) jochus@Bacardi ~ $ iwconfig lo no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11g ESSID:"Jochus" Mode:Managed Frequency:2.462 GHz Access Point: 00:16:B6:3B:1E:3C Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=67/100 Signal level=-52 dBm Noise level=-85 dBm Rx invalid nwid:0 Rx invalid crypt:48 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 br0 no wireless extensions. jochus@Bacardi ~ $ arp -an ? (195.130.130.165) at <incomplete> on br0 ? (195.130.129.165) at <incomplete> on br0 So, no luck :-( > And if this fail, please try the same configuration, without the > wpa-bridge option. Ok, so this is what I tried: $ cat /etc/network/interfaces #auto eth0 iface eth0 inet manual #auto eth1 iface eth1 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 # the wpa-iface option is expected to instruct wpa_supplicant # to setup the wifi link using eth1 instead of br0. wpa-iface eth1 wpa-driver wext wpa-ssid ##SSID## wpa-ap-scan 1 wpa-proto RSN wpa-pairwise CCMP wpa-group CCMP wpa-key-mgmt WPA-PSK wpa-psk ##PSK## $ sudo /etc/init.d/networking restart * Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.br0.pid with pid 7828 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/br0/00:0a:e4:ae:7e:4c Sending on LPF/br0/00:0a:e4:ae:7e:4c Sending on Socket/fallback DHCPRELEASE on br0 to 192.168.1.1 port 67 Waiting for br0 to get ready (MAXWAIT is 32 seconds). There is already a pid file /var/run/dhclient.br0.pid with pid 134519072 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/br0/00:0a:e4:ae:7e:4c Sending on LPF/br0/00:0a:e4:ae:7e:4c Sending on Socket/fallback DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 No DHCPOFFERS received. No working leases in persistent database - sleeping. $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0 0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 br0 jochus@Bacardi ~ $ ifconfig 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:53 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:5233 (5.1 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 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Base address:0xc000 eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:3 errors:79 dropped:79 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:292724 (285.8 KB) TX bytes:95750 (93.5 KB) Interrupt:21 Base address:0xc000 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:1957 errors:0 dropped:0 overruns:0 frame:0 TX packets:1957 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:98999 (96.6 KB) TX bytes:98999 (96.6 KB) jochus@Bacardi ~ $ iwconfig lo no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11g ESSID:"Jochus" Mode:Managed Frequency:2.462 GHz Access Point: 00:16:B6:3B:1E:3C Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=76/100 Signal level=-49 dBm Noise level=-85 dBm Rx invalid nwid:0 Rx invalid crypt:79 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 br0 no wireless extensions. jochus@Bacardi ~ $ arp -an ? (195.130.130.165) at <incomplete> on br0 ? (195.130.129.165) at <incomplete> on br0 > > If both fail, please provide the list of files in /etc/network/if*/*. jochus@Bacardi ~ $ ls /etc/network/if*/* -al -rwxr-xr-x 1 root root 979 2007-10-04 17:04 /etc/network/if-down.d/avahi-autoipd lrwxrwxrwx 1 root root 32 2009-04-26 11:27 /etc/network/if-down.d/wpasupplicant -> ../../wpa_supplicant/ifupdown.sh lrwxrwxrwx 1 root root 23 2009-04-26 11:36 /etc/network/if-post-down.d/avahi-daemon -> ../if-up.d/avahi-daemon -rwxr-xr-x 1 root root 1903 2007-10-23 21:45 /etc/network/if-post-down.d/bridge -rwxr-xr-x 1 root root 997 2007-04-27 23:37 /etc/network/if-post-down.d/wireless-tools lrwxrwxrwx 1 root root 32 2009-04-26 11:27 /etc/network/if-post-down.d/wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -rwxr-xr-x 1 root root 3593 2007-10-23 21:45 /etc/network/if-pre-up.d/bridge -rwxr-xr-x 1 root root 2358 2007-04-27 23:37 /etc/network/if-pre-up.d/wireless-tools lrwxrwxrwx 1 root root 32 2009-04-26 11:27 /etc/network/if-pre-up.d/wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -rwxr-xr-x 1 root root 886 2007-10-04 17:04 /etc/network/if-up.d/avahi-autoipd -rwxr-xr-x 1 root root 504 2008-12-18 19:35 /etc/network/if-up.d/avahi-daemon -rwxr-xr-x 1 root root 90 2009-01-23 16:01 /etc/network/if-up.d/mountnfs -rwxr-xr-x 1 root root 664 2009-01-06 16:51 /etc/network/if-up.d/ntpdate lrwxrwxrwx 1 root root 32 2009-04-26 11:27 /etc/network/if-up.d/wpasupplicant -> ../../wpa_supplicant/ifupdown.sh ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-04 21:06 ` Jochen Hebbrecht 2009-05-04 23:33 ` richardvoigt @ 2009-05-05 6:20 ` Nicolas de Pesloüan 2009-05-05 17:01 ` Jochen Hebbrecht 1 sibling, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-05 6:20 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht wrote: > Nicolas de Pesloüan schreef: >> >> I think that the "Destination Host Unreachable" is caused by some sort >> of "down link", because wpa_supplicant failed to establish the wifi >> link. When eth1 is part of the br0, packets received on eth1 is >> "forwarded" to br0 and not available on eth1. So wpa_supplicant must >> be instructed to listen for incoming packets on br0, not on eth1. >> >> Can you try the exact same configuration, adding wpa-bridge br0 in the >> eth1 stanza, to inform wpa_supplicant where to listen from ? >> >> auto lo >> iface lo inet loopback >> >> auto eth1 >> iface eth1 inet manual >> wpa-driver wext >> wpa-ssid ##SSID## >> wpa-ap-scan 1 >> wpa-proto RSN >> wpa-pairwise CCMP >> wpa-group CCMP >> wpa-key-mgmt WPA-PSK >> wpa-psk ##PSK KEY## >> wpa-bridge br0 <--- HERE. >> >> auto br0 >> iface br0 inet static >> bridge_ports eth1 >> address 192.168.1.111 >> netmask 255.255.255.0 >> gateway 192.168.1.1 > I changed the configuration and restarted the networking daemon. I'm > getting this output > > jochus@Bacardi ~ $ sudo /etc/init.d/networking restart > * Reconfiguring network > interfaces... > ioctl[SIOCGIFINDEX]: No such device > Failed to open l2_packet connection for the bridge interface 'br0' > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Can you also please try to change the order of the scanzas in /etc/network/interfaces, so that iface br0 comes before iface eth1 in the file ? ifup -a is expected to bring the interface in the order they appear in the file... Also, you could add "bridge-fd 0" in the br0 stanza. Because you bridge is by design loop-free, there is no reason to wait 32 seconds before entering the forwarding stat. 'hope this helps. Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 21:44 ` Nicolas de Pesloüan 0 siblings, 2 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-05 17:01 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > Can you also please try to change the order of the scanzas in > /etc/network/interfaces, so that iface br0 comes before iface eth1 in > the file ? ifup -a is expected to bring the interface in the order > they appear in the file... I tried that. I'm not posting all the outcomes of all the commands here, because it didn''t change the situation :-(. So no success ... > > Also, you could add "bridge-fd 0" in the br0 stanza. Because you > bridge is by design loop-free, there is no reason to wait 32 seconds > before entering the forwarding stat. Thnx :-). That saves me some time! Now, I changed my wireless security to unsecure, and I was able to get this: => with this configuration, the bridge works! auto lo iface lo inet loopback auto br0 iface br0 inet dhcp bridge_ports eth1 bridge-fd 0 auto eth0 iface eth0 inet manual auto eth1 iface eth1 inet manual wireless-essid ##SSID## jochus@Bacardi ~ $ ping www.google.be PING www.l.google.com (74.125.77.99) 56(84) bytes of data. 64 bytes from ew-in-f99.google.com (74.125.77.99): icmp_seq=1 ttl=242 time=74.5 ms 64 bytes from ew-in-f99.google.com (74.125.77.99): icmp_seq=2 ttl=242 time=17.4 ms 64 bytes from ew-in-f99.google.com (74.125.77.99): icmp_seq=3 ttl=242 time=21.4 ms But, when I add eth0 to bridge_ports, it doesn't work any longer So, maybe, we should try to focus why it doesn't work without security. If that works, we could check the WPA side. But I think we first need the bridge running in a "easy" situation, with no security ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 17:01 ` Jochen Hebbrecht @ 2009-05-05 18:08 ` richardvoigt 2009-05-05 19:19 ` Jochen Hebbrecht 2009-05-05 21:44 ` Nicolas de Pesloüan 1 sibling, 1 reply; 47+ messages in thread From: richardvoigt @ 2009-05-05 18:08 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 706 bytes --] > But, when I add eth0 to bridge_ports, it doesn't work any longer That and this are your problem: eth1 Link encap:Ethernet HWaddr 00:15:00:1f:20:a6 inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:3 errors:79 dropped:79 overruns:0 frame:0 All those dropped packets on receive... your wireless card isn't accepting packets with other destination MAC addresses. And when you add eth0 into the bridge, Linux must be choosing eth0's MAC address as the bridge address. Since bridging works in Windows, your card is capable of doing this with the right configuration. But I don't know what to suggest trying next. [-- Attachment #2: Type: text/html, Size: 977 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 18:08 ` richardvoigt @ 2009-05-05 19:19 ` Jochen Hebbrecht 2009-05-05 19:53 ` Jonathan Thibault 0 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-05 19:19 UTC (permalink / raw) To: richardvoigt@gmail.com; +Cc: bridge richardvoigt@gmail.com schreef: > Since bridging works in Windows, your card is capable of doing this > with the right configuration. But I don't know what to suggest trying > next. Are there other places where I could get some help? I already asked it at the ubuntuforums ... :-( ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 19:19 ` Jochen Hebbrecht @ 2009-05-05 19:53 ` Jonathan Thibault 2009-05-05 20:52 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Jonathan Thibault @ 2009-05-05 19:53 UTC (permalink / raw) To: Jochen Hebbrecht, bridge I believe that to allow bridging on a 'client', you need to enable WDS on the interface (and likely on the AP as well). Check to see if WDS is supported by your driver. Basically (but I could be wrong), it is an 'ethernet over wifi' encapsulation since the wifi does not allow for mac spoofing on a client endpoint which would be required for normal bridging. Jochen Hebbrecht wrote: > richardvoigt@gmail.com schreef: >> Since bridging works in Windows, your card is capable of doing this >> with the right configuration. But I don't know what to suggest trying >> next. > > Are there other places where I could get some help? I already asked it > at the ubuntuforums ... :-( > _______________________________________________ > Bridge mailing list > Bridge@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/bridge ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 19:53 ` Jonathan Thibault @ 2009-05-05 20:52 ` Jochen Hebbrecht 0 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-05 20:52 UTC (permalink / raw) To: Jonathan Thibault; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 1348 bytes --] Jonathan Thibault schreef: > I believe that to allow bridging on a 'client', you need to enable WDS on the interface (and likely on the AP as well). Check to see if WDS is supported by your driver. Basically (but I could be wrong), it is an 'ethernet over wifi' encapsulation since the wifi does not allow for mac spoofing on a client endpoint which would be required for normal bridging. > > > Thnx Jonathan. I found this information: ________________________________ Doing full bridging of wireless (802.11) requires supporting WDS <http://www.linuxfoundation.org/en/index.php?title=Net:WDS&action=edit&redlink=1>. The current implementation doesn't do it. It is possible to do limited wireless to Ethernet functionality with some wireless drivers. This requires the device to be able to support a different sender address and source address. That is what WDS provides. There are ways to make it work, but it is not always straightforward and you probably won't get it right without a pretty solid understanding of 802.11, it's modes, and the frame header format. ________________________________ ... so, the current implementation doesn't do it? So I can conclude Linux isn't ready for bridging a wired and wireless network? I didn't install any drivers for my wireless card, so I assume it uses the default driver of Ubuntu. [-- Attachment #2: Type: text/html, Size: 1769 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-05 17:01 ` Jochen Hebbrecht 2009-05-05 18:08 ` richardvoigt @ 2009-05-05 21:44 ` Nicolas de Pesloüan 2009-05-06 6:57 ` Jochen Hebbrecht ` (2 more replies) 1 sibling, 3 replies; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-05 21:44 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht wrote: > Nicolas de Pesloüan schreef: >> Can you also please try to change the order of the scanzas in >> /etc/network/interfaces, so that iface br0 comes before iface eth1 in >> the file ? ifup -a is expected to bring the interface in the order >> they appear in the file... > I tried that. I'm not posting all the outcomes of all the commands here, > because it didn''t change the situation :-(. So no success ... >> >> Also, you could add "bridge-fd 0" in the br0 stanza. Because you >> bridge is by design loop-free, there is no reason to wait 32 seconds >> before entering the forwarding stat. > Thnx :-). That saves me some time! 32 seconds per test... :-) > Now, I changed my wireless security to unsecure, and I was able to get > this: > > => with this configuration, the bridge works! > > But, when I add eth0 to bridge_ports, it doesn't work any longer > > So, maybe, we should try to focus why it doesn't work without security. > If that works, we could check the WPA side. But I think we first need > the bridge running in a "easy" situation, with no security When you setup the bridge at the beginning, the br0 interface takes the MAC address of eth1. Then you add eth0 and the bridge takes the MAC address of eth0, because it is lower. Can you try to use the bridge-hw option of /etc/network/interfaces, to force the bridge MAC address to the MAC address of the wireless interface ? This might solve the communication problem for UBUNTU SERVER... but unfortunately probably not for the bridging function. That beeing said, Jonathan might be right about the need for WDS... Can you have a look at the AP configuration, searching for a WDS setup ? Because if it works on Windows, without WDS (if disabled or unavailable on the AP), then we can assume that WDS is not required, even on Linux (the wifi interface is able to receive traffic for another MAC). If the AP is WDS enabled, then... WDS might be necessary... and nothing can be done if the driver for you wifi interface does not support it... Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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:47 ` Jochen Hebbrecht 2 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-06 6:57 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge 2009/5/5 Nicolas de Pesloüan <nicolas.2p.debian@free.fr>: > When you setup the bridge at the beginning, the br0 interface takes the MAC > address of eth1. Then you add eth0 and the bridge takes the MAC address of > eth0, because it is lower. > > Can you try to use the bridge-hw option of /etc/network/interfaces, to force > the bridge MAC address to the MAC address of the wireless interface ? This > might solve the communication problem for UBUNTU SERVER... but unfortunately > probably not for the bridging function. I think you mean bridge_hw (with an underscore instead of a dash?). I can't find any information about bridge-hw in the man pages. So, I need to specify it in the bridge stanza like this: bridge_hw ##HERE_COMES_THE_MAC_ADDRESS_OF_THE_EHT1_INTERFACE## Right? > > That beeing said, Jonathan might be right about the need for WDS... Can you > have a look at the AP configuration, searching for a WDS setup ? Because if > it works on Windows, without WDS (if disabled or unavailable on the AP), > then we can assume that WDS is not required, even on Linux (the wifi > interface is able to receive traffic for another MAC). > > If the AP is WDS enabled, then... WDS might be necessary... and nothing can > be done if the driver for you wifi interface does not support it... Just to be sure: with AP you mean: Access Point? So in my case, the router? I will check it tonight (I'm not at home right now!) Thanks for your tips, I'll keep you updated! ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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-06 16:47 ` Jochen Hebbrecht 2 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-06 15:37 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > That beeing said, Jonathan might be right about the need for WDS... > Can you have a look at the AP configuration, searching for a WDS setup > ? Because if it works on Windows, without WDS (if disabled or > unavailable on the AP), then we can assume that WDS is not required, > even on Linux (the wifi interface is able to receive traffic for > another MAC). > > If the AP is WDS enabled, then... WDS might be necessary... and > nothing can be done if the driver for you wifi interface does not > support it... http://www.linksysinfo.org/forums/showthread.php?t=47118 I'm having the WRT54GS router, and the explanation above tells me how to configre WDS. However, when I look in my admin panel, I cannot find a tab: "WDS". I guess my firmware is pretty old :-) ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-06 15:37 ` Jochen Hebbrecht @ 2009-05-06 16:55 ` Jonathan Thibault 2009-05-09 11:15 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Jonathan Thibault @ 2009-05-06 16:55 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On a wrt54gs, wds is probably enabled by default when applicable to be compatible with Linksys' WET hardware. Many vendors do not support mixing wds with WPA however, limiting you to WEP for encryption. I advise you disable encryption alltogether first to see if you can get bridging to work before you try with encryption. Jochen Hebbrecht wrote: > > Nicolas de Pesloüan schreef: >> That beeing said, Jonathan might be right about the need for WDS... >> Can you have a look at the AP configuration, searching for a WDS setup >> ? Because if it works on Windows, without WDS (if disabled or >> unavailable on the AP), then we can assume that WDS is not required, >> even on Linux (the wifi interface is able to receive traffic for >> another MAC). >> >> If the AP is WDS enabled, then... WDS might be necessary... and >> nothing can be done if the driver for you wifi interface does not >> support it... > http://www.linksysinfo.org/forums/showthread.php?t=47118 > > I'm having the WRT54GS router, and the explanation above tells me how to > configre WDS. > However, when I look in my admin panel, I cannot find a tab: "WDS". I > guess my firmware is pretty old :-) > _______________________________________________ > Bridge mailing list > Bridge@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/bridge ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-06 16:55 ` Jonathan Thibault @ 2009-05-09 11:15 ` Jochen Hebbrecht 0 siblings, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-09 11:15 UTC (permalink / raw) To: Jonathan Thibault; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 1551 bytes --] Hi Jonathan, I tried it without no security, but no luck. Jochen Jonathan Thibault schreef: > On a wrt54gs, wds is probably enabled by default when applicable to be compatible with Linksys' WET hardware. Many vendors do not support mixing wds with WPA however, limiting you to WEP for encryption. > > I advise you disable encryption alltogether first to see if you can get bridging to work before you try with encryption. > > Jochen Hebbrecht wrote: > >> Nicolas de Pesloüan schreef: >> >>> That beeing said, Jonathan might be right about the need for WDS... >>> Can you have a look at the AP configuration, searching for a WDS setup >>> ? Because if it works on Windows, without WDS (if disabled or >>> unavailable on the AP), then we can assume that WDS is not required, >>> even on Linux (the wifi interface is able to receive traffic for >>> another MAC). >>> >>> If the AP is WDS enabled, then... WDS might be necessary... and >>> nothing can be done if the driver for you wifi interface does not >>> support it... >>> >> http://www.linksysinfo.org/forums/showthread.php?t=47118 >> >> I'm having the WRT54GS router, and the explanation above tells me how to >> configre WDS. >> However, when I look in my admin panel, I cannot find a tab: "WDS". I >> guess my firmware is pretty old :-) >> _______________________________________________ >> Bridge mailing list >> Bridge@lists.linux-foundation.org >> https://lists.linux-foundation.org/mailman/listinfo/bridge >> > > [-- Attachment #2: Type: text/html, Size: 2319 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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:47 ` Jochen Hebbrecht 2009-05-06 20:07 ` Nicolas de Pesloüan 2 siblings, 1 reply; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-06 16:47 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > > When you setup the bridge at the beginning, the br0 interface takes > the MAC address of eth1. Then you add eth0 and the bridge takes the > MAC address of eth0, because it is lower. > > Can you try to use the bridge-hw option of /etc/network/interfaces, to > force the bridge MAC address to the MAC address of the wireless > interface ? This might solve the communication problem for UBUNTU > SERVER... but unfortunately probably not for the bridging function. > Now the bridge comes up perfectly, and ubuntu server can ping the internet. But nobody on the eth0 of ubuntu server can access the network :-( ... so no bridging indeed ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-06 16:47 ` Jochen Hebbrecht @ 2009-05-06 20:07 ` Nicolas de Pesloüan 2009-05-09 11:17 ` Jochen Hebbrecht 0 siblings, 1 reply; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-06 20:07 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht a wrote: > I think you mean bridge_hw (with an underscore instead of a dash?). I > can't find any information about bridge-hw in the man pages. bridge-hw and bridge_hw is exactly the same. (No difference between underscore and dash). Both will set a variable $IF_BRIDGE_HW, to be used by the scripts in /etc/network/if-*.d/*. From interfaces(5) : "Additionally, all options given in an interface definition stanza are exported to the environment in upper case with "IF_" prepended and with hyphens converted to underscores and non-alphanumeric characters discarded." >> Can you try to use the bridge-hw option of /etc/network/interfaces, to >> force the bridge MAC address to the MAC address of the wireless >> interface ? This might solve the communication problem for UBUNTU >> SERVER... but unfortunately probably not for the bridging function. >> > Now the bridge comes up perfectly, and ubuntu server can ping the > internet. But nobody on the eth0 of ubuntu server can access the network > :-( ... so no bridging indeed This is unfortunately what I expected. Now, you can have a last try with your current bridge configuration, by upgrading the firmware of your router, ensuring WDS is enabled in the router, and hope that the driver of your wifi adapter support WDS... By the way, what is the type of your wifi adapter ? If that fail, I think we have two options : - Try to setup a very special bridge configuration, with some sort of masquerading of the MAC address. This would require at least to use ebtables to replace the source MAC address in the header (and in the payload for ARP) of packets sent on the wifi interface, to route packets in the server, to stop the server from sending ICMP redirect in the wifi interface and to setup a proxy_dhcp on the server. It would be hard to setup, hard to debug and impossible to maintain... Probably not a good idea... Funny to try, but not a good target. - Setup a simple router configuration on the server, using another private subnet on location B. Using a simple NAT/Masquerading configuration (with iptables), it could be possible to hide the subnet of location B from location A, but still allow access to the printer of location B from location A and access to location A and to Internet from location B. If you don't have a really good reason to stick to bridge (like using a non-IP protocol), I suggest you try this. Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 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 0 siblings, 2 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-05-09 11:17 UTC (permalink / raw) To: Nicolas de Pesloüan; +Cc: bridge Nicolas de Pesloüan schreef: > bridge-hw and bridge_hw is exactly the same. (No difference between > underscore and dash). Both will set a variable $IF_BRIDGE_HW, to be > used by the scripts in /etc/network/if-*.d/*. > > From interfaces(5) : "Additionally, all options given in an interface > definition stanza are exported to the environment in upper case with > "IF_" prepended and with hyphens converted to underscores and > non-alphanumeric characters discarded." Ah, ok, thnx! > > This is unfortunately what I expected. > > Now, you can have a last try with your current bridge configuration, > by upgrading the firmware of your router, ensuring WDS is enabled in > the router, and hope that the driver of your wifi adapter support > WDS... By the way, what is the type of your wifi adapter ? I had a "chat" with somebody of the support site of Linksys. The WRT54GS enables WDS. So we can say this is my problem. My wifi adapter is a WMP54G > > If that fail, I think we have two options : > > - Try to setup a very special bridge configuration, with some sort of > masquerading of the MAC address. This would require at least to use > ebtables to replace the source MAC address in the header (and in the > payload for ARP) of packets sent on the wifi interface, to route > packets in the server, to stop the server from sending ICMP redirect > in the wifi interface and to setup a proxy_dhcp on the server. It > would be hard to setup, hard to debug and impossible to maintain... > Probably not a good idea... Funny to try, but not a good target. This really sounds like Chinese in my ears :-D > > - Setup a simple router configuration on the server, using another > private subnet on location B. Using a simple NAT/Masquerading > configuration (with iptables), it could be possible to hide the subnet > of location B from location A, but still allow access to the printer > of location B from location A and access to location A and to Internet > from location B. If you don't have a really good reason to stick to > bridge (like using a non-IP protocol), I suggest you try this. I was thinking on this situation too. But how will be somebody in subnet A able to reach someone of subnet B? We are gonna have to change the routing tables on the client side too? Jochen ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-09 11:17 ` Jochen Hebbrecht @ 2009-05-09 23:30 ` richardvoigt 2009-05-10 15:39 ` Nicolas de Pesloüan 1 sibling, 0 replies; 47+ messages in thread From: richardvoigt @ 2009-05-09 23:30 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge On Sat, May 9, 2009 at 6:17 AM, Jochen Hebbrecht <jochenhebbrecht@gmail.com> wrote: > Nicolas de Pesloüan schreef: >> bridge-hw and bridge_hw is exactly the same. (No difference between >> underscore and dash). Both will set a variable $IF_BRIDGE_HW, to be >> used by the scripts in /etc/network/if-*.d/*. >> >> From interfaces(5) : "Additionally, all options given in an interface >> definition stanza are exported to the environment in upper case with >> "IF_" prepended and with hyphens converted to underscores and >> non-alphanumeric characters discarded." > Ah, ok, thnx! >> >> This is unfortunately what I expected. >> >> Now, you can have a last try with your current bridge configuration, >> by upgrading the firmware of your router, ensuring WDS is enabled in >> the router, and hope that the driver of your wifi adapter support >> WDS... By the way, what is the type of your wifi adapter ? > I had a "chat" with somebody of the support site of Linksys. The WRT54GS > enables WDS. So we can say this is my problem. My wifi adapter is a WMP54G >> >> If that fail, I think we have two options : >> >> - Try to setup a very special bridge configuration, with some sort of >> masquerading of the MAC address. This would require at least to use >> ebtables to replace the source MAC address in the header (and in the >> payload for ARP) of packets sent on the wifi interface, to route >> packets in the server, to stop the server from sending ICMP redirect >> in the wifi interface and to setup a proxy_dhcp on the server. It >> would be hard to setup, hard to debug and impossible to maintain... >> Probably not a good idea... Funny to try, but not a good target. > This really sounds like Chinese in my ears :-D http://en.wikipedia.org/wiki/Proxy_ARP http://lists.netfilter.org/pipermail/netfilter/2007-May/068615.html >> >> - Setup a simple router configuration on the server, using another >> private subnet on location B. Using a simple NAT/Masquerading >> configuration (with iptables), it could be possible to hide the subnet >> of location B from location A, but still allow access to the printer >> of location B from location A and access to location A and to Internet >> from location B. If you don't have a really good reason to stick to >> bridge (like using a non-IP protocol), I suggest you try this. > I was thinking on this situation too. But how will be somebody in subnet > A able to reach someone of subnet B? We are gonna have to change the > routing tables on the client side too? > > Jochen > _______________________________________________ > Bridge mailing list > Bridge@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/bridge > ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-05-09 11:17 ` Jochen Hebbrecht 2009-05-09 23:30 ` richardvoigt @ 2009-05-10 15:39 ` Nicolas de Pesloüan 1 sibling, 0 replies; 47+ messages in thread From: Nicolas de Pesloüan @ 2009-05-10 15:39 UTC (permalink / raw) To: Jochen Hebbrecht; +Cc: bridge Jochen Hebbrecht wrote: > I had a "chat" with somebody of the support site of Linksys. The WRT54GS > enables WDS. So we can say this is my problem. My wifi adapter is a WMP54G OK. Until the driver for this adapter support WDS, it would be impossible to bridge between Ethernet and Wifi. >> If that fail, I think we have two options : >> >> - Try to setup a very special bridge configuration, with some sort of >> masquerading of the MAC address. This would require at least to use >> ebtables to replace the source MAC address in the header (and in the >> payload for ARP) of packets sent on the wifi interface, to route >> packets in the server, to stop the server from sending ICMP redirect >> in the wifi interface and to setup a proxy_dhcp on the server. It >> would be hard to setup, hard to debug and impossible to maintain... >> Probably not a good idea... Funny to try, but not a good target. > This really sounds like Chinese in my ears :-D It is ! :-D From a theoretical point of view, it is possible to build such a setup, but really, you should keep away from that. I didn't tested it and won't have enough time to support you on this way. >> - Setup a simple router configuration on the server, using another >> private subnet on location B. Using a simple NAT/Masquerading >> configuration (with iptables), it could be possible to hide the subnet >> of location B from location A, but still allow access to the printer >> of location B from location A and access to location A and to Internet >> from location B. If you don't have a really good reason to stick to >> bridge (like using a non-IP protocol), I suggest you try this. > I was thinking on this situation too. But how will be somebody in subnet > A able to reach someone of subnet B? We are gonna have to change the > routing tables on the client side too? Yes, you are right. If the network you are talking about is your home network (not a company network), why don't you create a different subnet for both location (let's say 192.168.0.0/24 and 192.168.1.0/24) ? You just need to add a static route to the subnet of location B, through UBUNTU SERVER, in the main router at location A. In location B, you need to setup every hosts to use UBUNTU SERVER as the default route. If you don't have access to the routing table of the main router in location A, you can try to run a ripd daemon in UBUNTU SERVER, to inform the main router of location A that UBUNTU SERVER is a router to the subnet of location B. You can find ripd in the quagga package, for example. (The documentation is in the quagga-doc package). It would be by far the simplest way to achieve your goal. Nicolas. ^ permalink raw reply [flat|nested] 47+ messages in thread
* Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails 2009-04-29 16:26 ` Ross Vandegrift 2009-04-29 16:40 ` Jochen Hebbrecht @ 2009-04-29 16:41 ` Jochen Hebbrecht 1 sibling, 0 replies; 47+ messages in thread From: Jochen Hebbrecht @ 2009-04-29 16:41 UTC (permalink / raw) To: Ross Vandegrift; +Cc: bridge [-- Attachment #1: Type: text/plain, Size: 395 bytes --] Ross Vandegrift schreef: > On Wed, Apr 29, 2009 at 06:16:14PM +0200, Jochen Hebbrecht wrote: > >> No, the DHCP server gives addresses to every MAC address that is possible. >> > > Is eth0 plugged in? Does it work if you statically assign an IP to br0? > > Ross > > Yes, it is plugged in ( Ubuntu says: link is ready ). I also tried statically, but no improvements :-( ... Jochen [-- Attachment #2: Type: text/html, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 47+ messages in thread
end of thread, other threads:[~2009-05-10 15:39 UTC | newest] Thread overview: 47+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
