Thanks Dan for the details. Thanks James for ordering the router, should be here next week. 

Dan is this failing to connect at all, or DHCP issue similar to what we saw with the Microsoft router? I'm wondering if there is any work around we can suggest (bridged maybe) as a work around until we can make some progress on this bug. 

Ross-- he is currently connected via Bridged mode successfully, to SC.  

His Controller just fails with an error message when trying to connect.  He does not get an option for "Self assigned" or somesuch.  So I suspect it's not connecting at all and never reaching DHCP.  

This is nearly identical to what we're seeing with that Microsoft router. (bug 8984) 

Please note as I discussed with you:  I don't think the customer failing to connect to the MS router was reaching the DHCP stage either.  "Self Assign" never appeared as an option there.

(recent addendum from customer)

I have tried to troubleshoot my SB issue while waiting for a resolution. (will not connect wirelessly with router)
I started at square one by setting up the SB in the hybrid mode with out any security. It would not connect with my D-Link DIR-655 wireless router. I then changed my SSID and tried again with no security. I continued with WEP 64, WEP 128, and finally WPA Personal. In each case, the SB would not connect with the router.  Also, each of my four other wireless clients connected immediately.
(HP laptop with Vista, Dell laptop with XP, HP Deskjet, and HP Photosmart printers. 
Please keep in mind that the SB Duet performed superbly with this router since the day I purchased it. It has been set up  in the hybrid mode since the beginning.  The problem started after I upgraded from 7.01 to 7.1.  What concerns me is even after I down-graded to 7.01 (since our last conversation)
I still could not get a connection. Meanwhile, my four other wireless clients connected no matter what changes I made to security procedures.  Should I try going back to 7.0? I believe that was the version in use when I originally set up the SB Duet.
I am continuing to listen to music through my pc, but I am limited by controller range and the album art does not show up on the controller display.

Thanks for your continuing support...

So far I'm not able to reproduce. I managed to connect Duet r2873 without issue, DIR-655 using firmware 1.11. 

Works with r2722, firmware 1.11. 
Works with r2722, firmware 1.20.
Works with r2873, firmware 1.20.

Based on Comment #3 I'm thinking this is a networking issue, not Duet firmware related. Dan could you please ask for more networking information? I want router version number (I'm using A3) router firmware version, and all other wireless networking info that he can share. Are there any other wireless access points? What wireless channel? He has several wireless PCs and its clear he knows a thing or two about networking, I'd suggest having him use netstumbler to take a look for potential channel congestion. 

(from customer)

Hi Daniel,

Well, good news... I have the SB Duet back working properly in the hybrid connection, with the SBD controller connecting wirelessly with my D-Link DIR-655 router and the SB receiver hard wired to my network, just the way it  worked before my connection problems.  I can tell you what I did, but not why it worked or what was wrong.  

I do believe that the 7.1 upgrade had nothing to do with the problem.  The problem may have had more to do with how the DIR-655 assigned IP addresses to it's clients.  I'll try to explain.  When I first connected the DIR-655, I noticed that it tended to assign IP addresses to the upper numbers (192.168.0.140 and above, with only a few assigned to the lower numbers (between 192.168.0.2 and 192.168.0.10).  I have 15 devices in my home-office network... 4 computers, 2 NAS storage units, 1 Windows Home Server, and 8 audio and video devices.  11 of the 15 devices were assigned IP's consectutively at the upper end.  I did upgrade to 7.2, but still had the problem. I decides to do a major overhaul to my IP addresses.


My four pc's still are assigned IP's by the router, but all of my printers, storage, and audio-video devices now have a static IP reservations in the DIR-655.  I also made sure that each unit was spaced at least 5 numbers away from adjacent units.  For example, the SB controller is at 192.168.0.130 while the SB receiver is at 192.168.0.125.  Again, I can't explain it, but this network shake-up solved the problem.  When I turned the SB controller on, it connected immediately to the router wirelessly and gave me the ethernet option, which I selected.  Next came the music source option, I selected Squeeze Network and it immediately connected.

After all of this downtime, there was some positive things that occurred:
1. I learned more about the SB Duet and what a great product it is
2. How valuable it is to have a product whose support people really care
3. I also learned more about my current router and all of it's internal options
I don't know how much all of this will help others who may have similar problems, but if someone has many devices on their network, shaking it up may be a viable option to eliminate certain problems.
I am currently at SqueezeCenter Ver. 7.2 and using WPA Personal.
I did all this yesterday, and have turned the SB Duet on and off several times and everything is working well.  Thanks again for your support!

Closing this as it appears to be not a reproducible bug, please feel free to re-open with more information. 

Created attachment 4622 [details]
controller log

This seems to be a problem again, DHCP issues with this router. Consistently reproducible for me with 7.3 r3698. I can reproduce this with WPA encryption or with encryption disabled. 

Nov 15 04:35:49 SqueezeboxController local0.err udhcpc[392]: bogus packet, option fields too long 
Nov 15 04:35:49 SqueezeboxController user.info jive: (Wireless.lua:666) - REPLY:bssid=00:1e:58:f2:0b:f3 ssid=dir655 id=0 pairwise_cipher=NONE group_cipher=NONE key_mgmt=NONE wpa_state=COMPLETED 
Nov 15 04:35:49 SqueezeboxController user.warn jive: (SetupWirelessApplet.lua:671) - wpa_state=COMPLETED
Nov 15 04:35:49 SqueezeboxController user.warn jive: (SetupWirelessApplet.lua:672) - ip_address=nil
Nov 15 04:35:49 SqueezeboxController local0.err udhcpc[392]: bogus packet, option fields too long

I have another customer who is having terrible connections issue with this router, where it was working fine previously, then he upgraded to r3476 and now it's very unreliable.  The Controller drops off his network, reconnects, works for a time, drops off, reconnects, etc.

RN# 081226-002729

Dan please follow up when you hear more from the customer. Do you think he might be able to provide us with a Controller log?

I'm now able to connect to this router without issue today, using 7.3 r3476. I suspect some sort of "Mountain View bug" type of issue yesterday, and I'm looking into it. 

After discussing this in further detail with Ross I don't think this new customer is suffering from this bug.  The more likely cause is some networking issue with his set up.  

I'll investigate further and open a separate bug if needed.

Anyone having this issue, please verify that WISH and QOS (traffic shaping) are turned off.

If they are not, turn them off, reboot the router and Squeezebox devices.  Retest if you still have issues.  Please post comments in this bug.

I believe this is satisfactory since 7.3.3, if anyone objects please feel free to re-open.