Bugzilla – Bug 3660
DHCP bridging does not work sometimes
Last modified: 2008-12-18 11:40:15 UTC
Went from firmware 30-somethinh to 55 to get WPA2 with AES to work. The SB2 now correctly gets connected to the access point and is assigned an IP-address, but stuff connected to the ethernet port doesn't get assigned an IP-address by DHCP. If I manually assign them an IP-address, everthing works.
Sorry for the delay. I can't seem to reproduce this currently. Are you still experiencing this problem with FW58?
Yes, unfortunatly even firmware 59 gives the same result.
What kind of router or access point are you using?
I'm using a firewall based on pfsense with a WLAN-card from Atheros. Quite a special setup I must say. When rnning with my old setup (a netgear AP with WPA1, connected to the same pfsense firewall) everything works fine.
I assume that you've checked that you're not doing anything silly like blocking the ports DHCP uses (67 tcp and udp and 68 tcp and udp) from that connection? :) Does the new setup work if you set it for no encryption, do you know? Since it's a special setup, I don't suppose you can monitor the DHCP traffic in some way to help us out here? :)
1) No blocking on any LAN-ports. Also see no 2. 2) Yes, without encryption everything works as expected. 3) Let me see. I havn't done it before, but I will google around and have a look...
It looks like there may be one or two other users having this problem, and they may all be using PCs with network cards rather than traditional wireless APs or routers. I don't usually test with that arrangement, so perhaps I should set up a pfsense (http://www.pfsense.com/) system to have a look. In the mean time, a log would be a valuable help. Oscar, just to verify, the behavior you are seeing is that when the SB3 says it's acquiring a DHCP address, the countdown timer just runs out, and it offers to self-assign an address? There's not any kind of error or unusual behavior that occurs?
Another customer of ours is seeing this bug. SB3 with firmware 55, Linksys WRT54G using WPA-PSK with DHCP disabled. He's running a Ubuntu server with DHCP. "Running ethereal on the dhcp server machine, I see the the DHCP requests and responses. It appears that the squeezebox just isn't receiving them anymore." TMID 7849.
Ross, so your user also doesn't have a normal access point, but is using a wireless card in a PC as their "wireless router"? Or does he have a wireless router, but its internal DHCP server is disabled and he's using the one on his Ubuntu box?
Chris, The latter is correct. He's using a Linksys WRT54G with DHCP disabled, and his Ubuntu server is acting as the DHCP server.
Is it possible you could get an ethereal log from him to attach to the bug?
Created attachment 1472 [details] DHCP successful, w/ bridging turned off.
Created attachment 1473 [details] failing, with bridging enabled.
Richard, were you able to see anything interesting in these ethereal logs?
that last inquiry was from me, while I was sitting at Ross's computer. Sorry for any confusion.
Sorry for not answering quicker. My @spymac address got cancelled. But now I am back! An answer to #7 below: The countdown runs down to zero with no IP-address being aquired.
Hi again! I don't really agree with the new headline for this bug. I get the DHCP to work with bridging turned on when NOT using WPA. SO some mention of WPA should be in the headline...
I disagree with the headline for this bug as well. I see the problem w/o a network-card-based access point. I'm using a Linksys WRT54G access point. (See comment #8)
Seems to mostly affect network-card-based access points. Does everyone agree it only happens on WPA? Or is that also a variable?
I have been looking at this today, and would like to clarify a couple of points. In the original comment I am correct it saying that DHCP on the Squeezebox works, but the it is DHCP on the bridged device that is failing. And is this correct for other people reporting this bug? I may have found a problem during setup where the bridging option is not correct set until the Squeezebox is re-booted. Can you please try configuration the Squeezebox with Bridging enabled and WPA until it connects to the Slimserver. Then power cycle the Squeezebox, allowing it to automatically connect to the Slimserver. Can the bridged device now use DHCP and work correctly? Richard
My configuration: SB3 with firmware 55 Linksys WRT54G using WPA-PSK with DHCP disabled DHCP server is an Ubuntu machine. My experience was that DHCP failed for both the squeezebox AND the devices on the wired side of the squeezebox. I'll try the reboot this evening.
My experience is that with firmware 55 both SB2 and bridged unit failed DHCP. With firmware 58 (59?) only the attached device failed. My installation is broken right now, but I'll try to reinstall ASAP and try the reboot.
Hm! I notice at least one person on the forums noting that firmware 60 (which is now in the nightlies) solved his DHCP problem which sounded like it might be similar to some of these.
It would be good to get some feedback if rebooting after completing setup helps this problem. I am planning to make a release candidate squeezebox2/3 firmware for 6.5 over the next couple of days and would like to get a fix in for this bug if possible. Richard
I'm using an SB2 (firmware 55) going over air to a Netscreen 5GT ADSL/wireless. WPA PSK is used and using private address space (DHCP by Netscreen). Works fine if Ethernet bridging is disabled. When Ethernet bridging is enabled it is able to connect to Netscreen and then times out trying to get an IP address. There is another device plugged into the Ethernet port (also trying DHCP which also fails). Using a cross-over cable to connect the two.
I'm not able to try anything until the debian package is fixed. I read that Dan is on vacation and it will be fixed when he gets back...
I have fixed a bug releated to bridging during setup, the fix will be in firwmare sb62/t13. If the squeezebox was already configured, and you changed only the bridging option during setup then the change would not have any effect until the squeezebox was rebooted. This seems to be the only bug I have been able to find with bridging, tested with Linksys WRT54GS router and laptop configured to use dhcp. Firmware sb62/t13 is currently undergoing internal testing. You will be notified again when it is made part of a nightly release. If after upgrading to the new firmware you are still having problems please re-open the bug.
Created attachment 1504 [details] Log from Ethereal with WPA2 turned on
Created attachment 1505 [details] Log from Ethereal without WPA2
I'm sorry to reopne the bug, but it still doesn't work for me. I have upgraded to firmware 62 and the bridged device still doesn't receive an IP address when WPA2 is turned on. I have attached Ethereal logs from both cases. I have also tried to powercycle the SB2. After the restart the SB2 refuses to receive an IP...
Oscar, I will look at the ethereal captures tomorrow. On what box did you perform the capture? I really need to be able to recreate this bug in order to work out what's going wrong here. Can you please let me know/confirm: - What device are you connecting to the bridge? - What access point are you using? - What is allocating the dhcp address? You also mentioned that it works when using a netgear AP, is it possible that your access point is preventing the dhcp address being allocated? Richard
My God, you ARE working day and night! ;-) 1. The device attached is my primary computer with an Abit motherboard with built in network i/f. This is connecyed to a Netgear gigabit switch which is connected to the SB2. 2. The access point is a PFsense firewall with a Wistron wifi-card (CM-9) 3. See 1, I think... Yes, it is working with the Netgear AP, but only when using WPA1. That access point is rather old and only capable of WPA1. The capturing was made with the primary computer. I havn't got any other computer capable of capturing the traffic. My Macbook Pro refuses to run Ethereal and I havn't been able to compile it for my Debian server...
So this is your network setup? -------- -------------- | PC | --- | Gig Switch | -------- -------------- | | -------------- ----------- | Squeezebox | --WLAN-- | PFsense | --- Internet -------------- ----------- If I understand correctly in your last reply you said the dhcp server is running on the PC, connected to the squeezebox on the ethernet port? Or do you mean the dhcp server is on the PFsense firmwall?
Yes, that is my setup (commenting the picture). No, the DHCP runs on the pfsense firewall.
I am not going to have time to fix this for 6.5, retargetting for 7.0.
*** Bug 4557 has been marked as a duplicate of this bug. ***
Further investigation shows that bridging does not work correctly when WPA or WPA2 encryption is used. An extra 4 bytes of data are added to each ethernet packet sent on the bridged interface. This can also cause some packets to be dropped if the exceed the MTU. This bug is fixed in firmware SB 71/TR 26. It is currently undergoing internal testing. You will be notified again when it is made part of a nightly release.
This bug fix will be available in tonight's nightly Slimserver release. The release will be available from: http://www.slimdevices.com/dev_nightly.html at around 1:30 AM (Pacific Daylight Time) tomorrow morning. (08:30 UTC). You'll need to install the new version of Slimserver, and then force your Squeezebox upgrade its firmware by holding down the "Brightness" button on the remote control until the firmware upgrade process begins. If you are still experiencing this problem after upgrading your affected players to the new firmware, please reopen the bug.