Bugzilla – Bug 11149
r3993 Controller Update Breaks SC/SN Communication
Last modified: 2009-05-07 16:53:07 UTC
After the r3993 controller update, communication between the controller squeezecenter and squeezenetworks constantly broken. When selecting a music source from either a local squeezecenter or the squeezenetwork you can see in the transparent background the wifi icon going from blue to white sever times and then after a timeout period you the communication failed, try again prompt is displayed. I upgraded from the firmware sent down from the Squeezenetwork if that makes any difference on if that is different from the latest squeezecenter binaries. A hard reset was done on the controller and a force forget player was done on the local squeezecenter. I attempted to reconnect to the local squeezecenter and all attempts have been unsucsessful. My controller is is connected to the access point via ethernet, and the controller via wifi. I'm am connected to my wireless access point successfully as well. It is a Linksys WRT310N. Signal Quality of 48% -56 Signal,-84 Noise,28 Signal to Noise Ratio.
Do you have static or dynamic IP address set in your router?
*What version of SqueezeCenter are you running, please include the Build Number. Go to Settings > Status. Cut and Paste the SqueezeCenter and Player Information sections to this bug *What is the brand of your Network Router *What is the Model number *What is the firmware revision in the router *What type of encryption (if any) is enabled *Is the SSID Hidden or Broadcast *Is Static or Dynamic IP address assignment used *Are your SB Receivers connecting to the network Wireless or are they Wired to your Router (or a hub then to the router) *What other devices do you have attaching to your network *What is the system hardware you have SqueezeCenter running on. Make, Model, CPU, Memory, Operating system, as much info as you can give me *When you saw this error, were you connected to SqueezeCenter or SqueezeNetwork
Static ip for the server running squeezecenter *What version of SqueezeCenter are you running, please include the Build Number. Go to Settings > Status. Cut and Paste the SqueezeCenter and Player Information sections to this bug Version: 7.3.2 - 24695 @ Mon Jan 19 16:57:28 PST 2009 **NOTE THE IP ADDRESS FOR THE CONTROLLER IS THE IP ADDRESS OF MY WIRELESS ROUTER** Player Model: controller Player IP Address: 192.168.2.1 Player MAC Address: 00:04:20:1a:13:ce Player Model: receiver Firmware: 58 Player IP Address: 192.168.2.146 Player MAC Address: 00:04:20:16:13:e2 *What is the brand of your Network Router Linksys, Airlink 101 *What is the Model number WRT310N, AR690W *What is the firmware revision in the router V1.0,V1.0 *What type of encryption (if any) is enabled WPA/WPA2 PSK/TKIP *Is the SSID Hidden or Broadcast Broadcast *Is Static or Dynamic IP address assignment used Static to the server dynamic to to everything else *Are your SB Receivers connecting to the network Wireless or are they Wired to your Router (or a hub then to the router) Receiver is wired. Controller Wireless *What other devices do you have attaching to your network 5 Desktops, HP Wireless Printer, 1 Laptop, Netflix Media Player, Silicon Dust HDHomerun, Wifi Cam, Cisco Voip Adapter, Grandstream Voip Adapter, Tmobile G1, *What is the system hardware you have SqueezeCenter running on. Make, Model, CPU, Memory, Operating system, as much info as you can give me Server IP Address: 192.168.2.5 Server HTTP Port Number: 9000 Operating system: Red Hat - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.10.0 - i386-linux-thread-multi MySQL Version: 5.0.67 Total Players Recognized: 2 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Fedora 10 2.6.27.12-170.2.5.fc10.i686 2GB of RAM *When you saw this error, were you connected to SqueezeCenter or SqueezeNetwork Error is seen when connecting to both the squeezenetwork and squeezecenter.
On the note.. that is not something that I did. That is reporting back from the controller. I've forcibly forgotten the player and it still reports back with the ip address of my router.
(In reply to comment #3) > > **NOTE THE IP ADDRESS FOR THE CONTROLLER IS THE IP ADDRESS OF MY WIRELESS > ROUTER** > > Player Model: controller > > Player IP Address: 192.168.2.1 > > Player MAC Address: 00:04:20:1a:13:ce > This may be the problem you are seeing, please do a Factory Reset on both the SBC and the SBR. Then walk through the setup again. Verify that the SBC does NOT get an IP address that is the same as your router
After a reset of the controller and the receiver It works in this configuration connecting thru the receiver wirelessly. Player Model: controller Player IP Address: 192.168.2.191 Player MAC Address: 00:04:20:1a:13:ce Player Model: receiver Firmware: 58 Player IP Address: 192.168.2.146 Player MAC Address: 00:04:20:16:13:e2 It partially works when connecting via the wireless access point. It tries to connect to my squeezecenter as a music source every 8 - 10 seconds. Player Model: controller Player IP Address: 192.168.2.1 Player MAC Address: 00:04:20:1a:13:ce Player Model: receiver Firmware: 58 Player IP Address: 192.168.2.146 Player MAC Address: 00:04:20:16:13:e2 I setup a tcpdump (tcpdump host 192.168.2.146 or host 192.168.2.191) and I can see a heartbeat check every few seconds or so from the controller
(In reply to comment #6) > After a reset of the controller and the receiver > > It works in this configuration connecting thru the receiver wirelessly. > in this mode, the Receiver is wired to your router and the Controller is wireless to the Receiver During setup of the SBC, at the Wireless Connection menu, you selected 'Connect using Squeezebox' -- Correct? > > > It partially works when connecting via the wireless access point. It tries to > connect to my squeezecenter as a music source every 8 - 10 seconds. > in this mode, the Receiver is wired to your router? or did you remove the Ethernet cable, factory reset and connect wireless? and the Controller is wireless to the router During setup of the SBC, at the Wireless Connection menu, you selected ?? -------------- I find it very strange that in 'wireless' mode the SBC would get the address assigned to your router. Lets try a 'static' address for the controller next, to see if that changes the behavior. Select a number outside the range of your other equipment, but still in the range of your routers assigned range.
>in this mode, the Receiver is wired to your router >and >the Controller is wireless to the Receiver >During setup of the SBC, at the Wireless Connection menu, you selected 'Connect >using Squeezebox' -- Correct? Correct. >in this mode, the Receiver is wired to your router? or did you remove the >Ethernet cable, factory reset and connect wireless? >and >the Controller is wireless to the router >During setup of the SBC, at the Wireless Connection menu, you selected ?? Correct. I selected my wireless access point. >-------------- >I find it very strange that in 'wireless' mode the SBC would get the address >assigned to your router. >Lets try a 'static' address for the controller next, to see if that changes the >behavior. Select a number outside the range of your other equipment, but still >in the range of your routers assigned range. I tried static 192.168.2.250 and I'm still having the problems I got a Squeezebox Boom (connected wired it works, wireless similiar problems as the controller) this evening and it also has problems connecting back to the Squeezecenter. It detected the ip of the server as 192.168.2.1 instead of the actual ip. I had to manually configure the ip of the servers for it to connect. Below are it's settings from the squeezecenter for the boom. Player Model: boom Firmware: 43 Player IP Address: 192.168.2.1 Player MAC Address: 00:04:20:1e:c9:22 Wireless Signal Strength: 84% So what I'm thinking is there is a problem with the squeezecenter in it's latest incarnation with connections to and from wireless. The squeezecenter detects wireless players as the router ip.. and wireless players detect the squeezecenter as the wireless routers ip.
Ross: I didn't see the WRT310 on http://wiki.slimdevices.com/index.php/RouterStatus Have we tested that version yet? Do you know of anything that would cause the type of behavior Noah is seeing?
We do not have the WRT310N, this could be a router specific issue. Noah do you have DHCP disabled? I'm not sure Linksys has this option, but are you using any sort of reserved IP addresses?
Created attachment 4869 [details] tcpdump
I lost my post trying to upload the attachment. It a nutshell. I installed ddwrt on the router after the problems started. This existed on 7.3.1 on 3 routers with the controller. I will put my Airlink101 AR690W in the mix tomorrow. I installed Squeezeplay on my laptop via wifi it get's the ip address of the router according to the squeezecenter. I will attach the tcpdump from that in a few minutes.
Created attachment 4870 [details] tcpdump2
Squeezeplay info Player Model: squeezeplay Player IP Address: 192.168.2.1 Player MAC Address: 00:14:a4:6b:76:8f
You can list this as closed now. The latest router firmware corrects the funky routing/vlan problem. No more 192.168.2.1 address for wifi devices Player Model: controller Player IP Address: 192.168.2.191 Player MAC Address: 00:04:20:1a:13:ce Player Model: receiver Firmware: 58 Player IP Address: 192.168.2.146 Player MAC Address: 00:04:20:16:13:e2 Player Model: boom Firmware: 43 Player IP Address: 192.168.2.120 Player MAC Address: 00:04:20:1e:c9:22 Wireless Signal Strength: 89%
(In reply to comment #15) > You can list this as closed now. The latest router firmware corrects the funky > routing/vlan problem. Awesome!