Bugzilla – Bug 7304
Ray doesn't always reconnect
Last modified: 2008-08-12 11:11:56 UTC
As reported by gharris on the forum: Ok, I went ahead and tested this now anyway. With the SBR setup via UDAP, if I shutdown the stand-alone server, the SBR led goes blue. When I start the server up again, the SBR led stays blue and the SC7 web interface reports that "your player was not found." Power cycling the SBR fixes this. With the SBR setup via the SBC (SBR connected to stand-alone server via an isolated hub, SBC set up via "connect using squeezebox" option): powering down the server results in a blue led on the SBR. After powering the server back up, the SBR still doesn't "see" the SC service and the led remains blue. Power-cycling the SBR causes it to reconnect, but only if the SBC is on too, oddly enough. If the SBC is off, the SBR led glows bright-white and it never seems to find the SC service.
From the forum thread I am wondering if the issue gharris reported is related to the wrong ethernet magnetics in his SBR. Anyway, I just tried this and SBR reconnected just fine. - Setup SBC and SBR in bridged mode using DHCP -> SBR led dark white - Stopping SC7 -> SBR led turns blue - Starting SC7 -> SBR led turns dark white - Power off SBC -> SBR led stays dark white, SBR still listed in SC7 webinterface - Stopping SC7 -> SBR led turns blue - Starting SC7 -> SBR led turns dark white - Power up SBC -> SBR led stays dark white, SBR listed on SBC and controllable
Felix will follow up with gharris, qa to also try to reproduce.
I actually asked gharris to do some tests because I had seen similar issues. Here are my detailed findings: SC is 192.168.1.50, running on wired 192.168.1.0/24 network. Wireless network has SSID "3Com" and IP range 192.168.3.0/24 - wireless hub is connected to 192.168.1.0/24 network Configure from SBC ================== 1. Reset SBR (press and hold until button flashes fast red) 2. Configure SBR from SBC to connect wirelessly to 3Com and connect to SC. 3. Set music playing. - light is bright white 4. Stop SC - music eventually stops (buffer!) - light turns blue 5. Start SC - SBR reconnects - light is dim white - plays OK when I cue up a tune Repeat steps 4 & 5 with SBC turned off. - same result, works fine Configure using my perl module ============================== 1. Reset SBR (press and hold until button flashes fast red) 2. Configure SBR from SBC to connect wirelessly to 3Com and connect to SC. 3. Set music playing (from SC web page). - light is bright white 4. Stop SC - music eventually stops - light remains bright white 5. Start SC - light remains bright white and is not seen by Squeezecenter 6. Power-cycle SBR - SBR restarts and connects to SC - light is dim white - plays OK when I cue up a tune. So, it seems there's still something a bit off with how my perl code works.
I tried about 10 times (both playing music and stopped) killing SC and restarting it, and making sure Ray reconnected each time. Do you think it has something to do with the kind of music that's being played, or the amount of time Ray sits without being connected?
Ok, this is confusing. Let's ignore the setup where Robin's plugin is doing the configuring (we'll get back to that later) and focus on the SBR configured with SBC gharris' test was with bridging and failed. Felix tested with bridging on, and it appeared to work ok. Robin's test was without bridging (right, robin?) appeared to work ok. Chris' test also was ok (what was the network configuration, Chris, was this bridged?)
Yes bridged.
Feedback from gharris: I'll try to test the AP setup for you tomorrow afternoon. By "restarting server" I mean power cycling the actual pc hardware. The SC7 was installed from the "squeezecenter-branch" repo and is running on Fedora 8. I'll confirm the fw version when I test with the AP setup tomorrow.
I simulated the PC restart by stopping SC7 in my SuSE Linux VMWare, changing the static ip address and restarting SC7. And again SBR did find SC7 just fine and turned dark white again. I did the same with a SC7 running on an iBook. Stopped SC7, changed the ip address and restarted SC7 and SBR reconnected fine. BTW: SBR was in bridged mode with fw 22.
Yes, my test was without bridging. The SBR was connected (wired) to the same subnet (192.168.1.0/24) as the server. it was setup wirelessly from SBC.
Some more testing by gharris: OK after factory resets of both SBR & SBC and after initial setup of SBR using SBC both connecting to wireless AP (which provides dhcp for the wireless & wired net): PC running SB7: 192.168.0.222 (static) SBR: (via SC7 Settings->Players) The IP address for this player is 192.168.0.224:25286 The ethernet MAC address for this player is 00:04:20:16:01:ba Player Firmware Version: 22 Wireless Signal Strength: 83% SBC: Version 7.0 r2013, Feb 24 etc. MAC Address: 00:04:20:1A:02:3C IP Address: 192.168.0.223 After a "service squeezecenter stop": SBR LED goes blue. SBC wifi icon at bottom of home page is also blue. After "service squeezecenter start": SBR reconnects, led goes from blue to dim-white. SBC also indicates that it is connected. So, no problems here with just stopping and starting SC service in terms of getting the SBR to reconnect. ============================================== After powering down SBR & SBC and pc: Restarting PC, confirmed that SC service is running, it reports "player not found" as expected, the SBR isn't powered up yet. Powering up SBR: led sequence: RED->WHITE->GREEN->dim white. SC web interface now shows the SBR connected and Settings->Players now shows the SBR at: The IP address for this player is 192.168.0.224:28275 The ethernet MAC address for this player is 00:04:20:16:01:ba Player Firmware Version: 22 Wireless Signal Strength: 85% ...so, same IP, just a different port. Powering up the SBC: It's back on 192.168.0.223...no change there either.
So, if he uses a standard wireless setup, it seems to work ok, either stopping and restarting SC7 or powering down everything and restarting everything. BTW: I believe the sequence he is reporting is: RED->YELLOW->GREEN->dim white in reality. I asked for clarification.
If ray does turn out to behave differently using Robin's script, I wonder if gharris was just putting ray in setup mode as opposed to factory resetting during initial tests. Is it possible that this could cause different results?
I just did a number of simple tests, each time I started with a ray in factory reset mode connected via Ethernet to my network for simplicity. Using jive to configure ray, ray playing music, ray bright white: Removing the Ethernet cable ray will turn yellow, replacing cable ray will turn dim white. Stopping the server ray will turn blue, starting the server ray will turn dim white. Using Net-UDAP to configure ray, ray playing music, ray bright white: Removing the Ethernet cable ray will stay bright white and remain bright white when cable replaced. Stopping the server ray will stay bright white and remain bright white when server is restarted. I beginning to think that this bug is specific to Net-UDAP configured rays. Perhaps the title should be changed as well as the target or even resolved as works for me. Dean, what do you think?
Thank you Steven. Some more input from gharris: Yes, the SC7 pc has a dhcp service running and the SBC reports that the SBR's IP is in the range that that dhcp service hands out. Testing again: If I power-down the SC7 pc and power it back up, the SBR led remains blue and the SBC home screen lists "Settings; Extras; Choose Player". Going to Settings->Music Source and manually entering the IP of the SC7 pc doesn't seem to help. When I select the IP, the SBC and the SBR do nothing. This time, I had to power cycle the SBR and the SBC a couple of times in order to get them to reconnect. Reply With Quote
So bridged mode seem still to fail for him. At least it's consistent. But I guess this is also still with his broken SBR. What I got from his statement however is that he is running a DHCP server on the same PC running SC7. So I asked him to try again a standard wireless setup but this time he should stop the DHCP server on his AP and let the PC running a DHCP service give out the ip addresses. I am wondering if the combination of the bad ethernet jack and the DHCP service on his PC (I think he is running Fedora 8) might cause SBR not getting a proper ip address sometimes so it uses a self assigned one, which would lead to what he is seeing? BTW: I had a SBR (standard wireless) running over night where I stopped SC7 it was connecting to, forcing a blue led. The AP its connected to has a 10 minutes lease time. And this morning I restarted SC7 and SBR reconnected immediately (dim white).
Felix, I see the same behaviour as gharris, i.e. all seems to work OK when configured from the SBC, but when configured from Net::UDAP, if I shutdown the server when the SBR is playing the light remains bright white and doesn't reconnect when the server is restarted. It looks to me like some difference between how SBC / Net::UDAP setup the SBR. Any idea what that might be? R.
This appears to be an issue using Robin's tool. Felix will work with Robin to fix the issue in his software.
Marking resolved bugs as closed. Please reopen if the issue has not been addressed fully.