[Bridge] Ubuntu: network bridging between wireless and wired connection fails

Jochen Hebbrecht jochenhebbrecht at gmail.com
Wed Apr 29 09:16:14 PDT 2009


No, the DHCP server gives addresses to every MAC address that is possible.

So this is the current situation:

jochus at Bacardi ~ $ sudo brctl show br0
bridge name     bridge id               STP enabled     interfaces
br0             8000.000ae4ae7e4c       no              eth0
                                                                           
eth1

jochus at 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 at 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 at gmail.com <mailto:jochenhebbrecht at 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 at gmail.com <mailto:richardvoigt at 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 at gmail.com <mailto:jochenhebbrecht at 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 at Bacardi ~ $ sudo brctl show br0
>>         [sudo] password for jochus: bridge name     bridge id        
>>               STP enabled     interfaces
>>         br0             8000.000ae4ae7e4c       no              eth0
>>                                                               eth1
>>
>>         My routing table looks like this:
>>
>>         Code:
>>
>>
>>         Kernel IP routing table
>>         Destination     Gateway         Genmask         Flags Metric
>>         Ref    Use Iface
>>         192.168.1.0     0.0.0.0         255.255.255.0   U     0    
>>          0        0 eth1
>>
>>         169.254.0.0     0.0.0.0         255.255.0.0     U     0    
>>          0        0 br0
>>         0.0.0.0         192.168.1.1     0.0.0.0         UG    0    
>>          0        0 eth1
>>         0.0.0.0         0.0.0.0         0.0.0.0         U     1000  
>>         0        0 br0
>>
>>         But I'm not able to ping my router ...
>>
>>         Code:
>>
>>         PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
>>         From 192.168.1.111 icmp_seq=1 Destination Host Unreachable
>>         From 192.168.1.111 icmp_seq=2 Destination Host Unreachable
>>         From 192.168.1.111 icmp_seq=3 Destination Host Unreachable
>>
>>         --- 192.168.1.1 ping statistics ---
>>         5 packets transmitted, 0 received, +3 errors, 100% packet
>>         loss, time 4018ms
>>
>>         I don't understand why eth1 is in my routing table. It
>>         shouldn't be I guess?
>>         Anybody some idea's?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/bridge/attachments/20090429/43537e03/attachment-0001.htm 


More information about the Bridge mailing list