Bugzilla – Bug 9094
Controller does not work with Linksys WRT54GS v2 and after-market firmware
Last modified: 2008-10-22 13:34:44 UTC
It seems impossible for the Controller (7.1r2722 and below) to communicate reliably with a 7.1 SqueezeCenter on Win2K3 when the WiFi access point is a Linksys WRT54GS v2 (also possibly G/GL) that is using after-market firmware such as Sveasoft Alchemy/Talisman or Tomato. The Controller has no difficulty connecting to the after-market WiFi (11g with router in b/g mode, WPA+TKIP), but it does have difficulty communicating with the SqueezeCenter. Requests are received by SC from the Controller, but the Controller rarely gets an acceptable response, often showing no players, although it has been known to connect after a very long time or when the Controller is rebooted. I am attaching Controller and SqueezeCenter logs (the latter with Cometd debugging enabled) where it is apparent that the Controller and SqueezeCenter loop rapidly attempting to establish communication which never happens. A WTR54GS running original Linksys firmware has no problem connecting to the SqueezeCenter. In my network the after-market router is a gateway on 192.168.0.2, the SqueezeCenter is on a Win2K3 server 192.168.0.9 and the Controller is 192.168.0.22. DHCP and DNS are running on the Win2K3 server (called nm-server). I have reproduced this problem with Sveasoft Talisman 1.3.1, Tomato 1.19 and Tomato 1.21 firmware. I can provide configuration backups if requested. Note that this is with a Linksys WRT54GS v2. I will be happy to provide additional Controller/SqueezeCenter logs if requested.
Created attachment 3767 [details] Controller log Log content is from just after a fresh boot, showing communication attempts with SC 7.1 on a WRT54GS v2/Sveasoft Talisman 1.3.1 router.
Created attachment 3768 [details] SqueezeCenter server log cometd debugging covering the approximate period corresponding to the previously attached log of Controller activity.
Note that "squeezebox2" is my wired Squeezebox (SB3 mkI) player, which I had powered off while capturing logs to avoid polluting the Server cometd log with extraneous information.
Ross to try to reproduce for 7.3
Note several employees are running this FW, so it is possible. However there are a very large number of configurable options.
(In reply to comment #5) > Note several employees are running this FW, so it is possible. > Hi Christopher - has this been confirmed on a WRT54GS v2? I'm not talking about a WRT54G, or a WRT54GL (which is essentially a WRT54G v4) - the specific model may be important due to difference in the hardware. (In reply to comment #5) > However there are a very large number of configurable options. > Would a backup of my config be of any use to you?
Firmware Version: Talisman/Basic V1.3.1 Hardware: Linksys WRT54G/GS Works for me. This is a WRT54GS v1. Neil, care to factory default and then try to reproduce?
(In reply to comment #7) > Firmware Version: Talisman/Basic V1.3.1 > Hardware: Linksys WRT54G/GS > > Works for me. This is a WRT54GS v1. > > Neil, care to factory default and then try to reproduce? > Hi Ross - I did a factory reset of Talisman Basic v1.3.1 and began to reconfigure the router, all seemed to be going well until I tweaked a few of the settings on the Admin page (specifically disabling HTTPS, enabling NTP, enabling RW Parition, enabling Syslogd). After I saved the settings and rebooted the router, and then rebooted the Controller I started seeing the occassional blue WiFi icon, and then the Controller would periodically search for "nm-server" (which is the name of the server running SC 7.1). I'm going to have to start from scratch and begin changing admin settings one at a time - this may take me a few days to track down! :) It's also possible that the Administration changes are not the cause, and that I should have left more time to check over the Controller after I made the Basic Setup and Wireless config changes. As soon as I have more info I'll post again.
RN = 080810-001522
Neil have you had time to try to track down the offending setting?
Please feel free to re-open with new data, this does not appear to be a bug.