Bugzilla – Bug 11664
Won't set up with Microsoft MN-700 router
Last modified: 2009-09-08 09:25:39 UTC
Same issues as with bug 8984 as with Fab4. Seen by CAT tester, who confirms that it's a Microsoft MN-700 router. Here's the info from the user's diagnostic screen: version: 7.4r4875 player id: 00:04:20:22:01:40 Wireless network: MSHOME Wireless encryption: WEP Wireless signal: 43 SNR Ethernet: not connected IP info: nothing listed by any Mysqueezebox.com: DNS failed Ping: can't ping TCP ports: all list can't connect or not connected User is attempting to connect wirelessly. CAT problem report PR-011.
Created attachment 5062 [details] packet capture Packet capture under Richards test. MN-700 LAN port connected to LAN port of Belkin router. Belkin router connected to wireshark PC via LAN connection, belkin router's DHCP disabled. Hope this has something useful; if not please suggest what you'd like logged next.
Created attachment 5069 [details] packet capture showing Ubuntu machine with long host name DHCP request At least I hope it shows what Richard wants to see. I noticed on the admin page for the MS router it showed a connected client SqueezeboxContro as well as SqueezeboxController, they were different controllers, both appeared to not be connected. The admin page showed one of them as having a valid IP address. I'll keep digging. Richard if you have any more specific tests in mind please let me know.
192.168.2.187 SqueezeboxController 00-04-20-1A-2E-CB 192.168.2.3 slim-desktop 00-0C-29-58-45-2D 192.168.2.120 SqueezeboxContrl 00-04-20-22-01-56
It appears that the Microsoft router does not like hostnames greater than 16 characters in length. The DHCP Discover/DHCP Offer are fine, but the DHCP Request fails and the router responds with a DHCP NACK. If the client hostname is <= 16 characters then it works fine. A recent change made the hostname "SqueezeboxTouch" for fab4, so actually recent fab4 firmware should work fine with this router. But "SqueezeboxController" for the controller will fail. A possible fix is checked in fab4 r5242. If this works ok, then I'll back port this to 7.3 and 7.4 for bug 8984. Felix - can you review this patch. Ross - can you install the latest fab4 firmware and check it works with this router. Then let me know, and I'll set a longer hostname and verify it still works ok (you'll need to make a packet capture while I do this).
Created attachment 5075 [details] packet capture, long host name test with fab4 r5250 Packet capture with fab4 hostname set to SqueezeboxAReallyLongSillyHostname, firmware r5250 connecting to MN-700 with no encryption. It worked!
Confirmed as fixed. Well be back ported to 7.3.3 and 7.4 soon.
(In reply to comment #6) > Confirmed as fixed. Well be back ported to 7.3.3 and 7.4 soon. Verified in r5316.