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.<br>
<br><div class="gmail_quote">On Tue, Apr 28, 2009 at 12:36 PM, Jochen Hebbrecht <span dir="ltr"><<a href="mailto:jochenhebbrecht@gmail.com">jochenhebbrecht@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Ross Vandegrift schreef:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
On Tue, Apr 28, 2009 at 02:52:10PM +0200, Jochen Hebbrecht wrote:<br>
<br>
</div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Okay, thnx!<br>
Just a small question, I think I need to configure eth0 and eth1 to<br>
manual? And not to DHCP?<br>
<br>
Like this:<br>
----------------------------------------<br>
auto eth0<br>
iface eth0 inet manual<br>
<br>
auto eth1<br>
iface eth1 inet manual<br>
----------------------------------------<br>
<br>
</blockquote>
<br>
Ah - I missed that. Yes, you definitely want to set the member<br>
interfaces to manual.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The thing I don't understand then: if you execute a dhclient on br0,<br>
how does br0 know the configuration of eth1? Because there's a WPA2<br>
configuration on it. Will it use that settings too while bridging?<br>
<br>
</blockquote>
<br>
I'll be honest, I'm not sure - I've never done that with<br>
wpa_supplicant and the debian tools. You might need to activate<br>
wpa_supplicant in the pre-up for br0.<br>
<br>
Check out the manpage for interfaces - it may have more details.<br>
<br>
</div></blockquote>
<br>
Ok, I made it myself a little easier by temporarly switching from WPA2 to unsecure wireless networking.<br>
<br>
I'm having the following configuration:<br>
<br>
Code:<div class="im"><br>
<br>
to lo<br>
iface lo inet loopback<br>
<br></div><div class="im">
auto eth0<br>
iface eth0 inet manual<br>
<br>
auto eth1<br>
iface eth1 inet manual<br></div>
wireless-essid ##MY-ESSID##<br>
wireless-mode managed<br>
<br>
auto br0<div class="im"><br>
iface br0 inet dhcp<br>
bridge_ports eth0, eth1<br>
<br></div>
When I reboot, my interfaces are getting the following config:<br>
<br>
Code:<div class="im"><br>
<br>
br0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c inet6 addr: fe80::20a:e4ff:feae:7e4c/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br></div>
RX packets:87 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:0 RX bytes:17544 (17.1 KB) TX bytes:3744 (3.6 KB)<div class="im"><br>
<br>
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<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
<br>
eth0 Link encap:Ethernet HWaddr 00:0a:e4:ae:7e:4c inet6 addr: fe80::20a:e4ff:feae:7e4c/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br></div>
RX packets:3 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:89 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:1000 RX bytes:1770 (1.7 KB) TX bytes:23069 (22.5 KB)<div class="im"><br>
Interrupt:20 Base address:0xc000 <br></div>
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<div class="im"><br>
inet6 addr: fe80::215:ff:fe1f:20a6/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br></div>
RX packets:223 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:99 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:1000 RX bytes:18762 (18.3 KB) TX bytes:8392 (8.1 KB)<br>
Interrupt:21 Base address:0xa000 Memory:c8006000-c8006fff <br><div class="im">
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0<br>
inet6 addr: ::1/128 Scope:Host<br>
UP LOOPBACK RUNNING MTU:16436 Metric:1<br></div>
RX packets:1879 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:1879 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:0 RX bytes:94956 (92.7 KB) TX bytes:94956 (92.7 KB<br>
<br>
The bridge looks ok:<br>
<br>
Code:<br>
<br>
jochus@Bacardi ~ $ sudo brctl show br0<br>
[sudo] password for jochus: bridge name bridge id STP enabled interfaces<br>
br0 8000.000ae4ae7e4c no eth0<br>
eth1<br>
<br>
My routing table looks like this:<br>
<br>
Code:<div class="im"><br>
<br>
Kernel IP routing table<br>
Destination Gateway Genmask Flags Metric Ref Use Iface<br></div>
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1<div class="im"><br>
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0<br></div>
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1<br>
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 br0<br>
<br>
But I'm not able to ping my router ...<br>
<br>
Code:<br>
<br>
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.<br>