Bugzilla – Bug 16654
Malformed Discovery response: SB3 and Duet Receiver don't reconnect automatically
Last modified: 2011-11-06 23:24:23 UTC
Created attachment 7027 [details] pcap of suspeced malformed discovery protocol. I am trying to debug the phenomenon that some of my players disconnect once in a while , and don't reconnect automatically. I put a trace (wireshark) on the server, filtering on the mac address of a disconnected SB3. First suspect is the discovery protocol. The attached pcap file shows repeated discovery requests and responses. BUT, the server responds with the library name "Savoray Music". Shouldn't this be the IP address? so it says here: http://wiki.slimdevices.com/index.php/SLIMP3_client_protocol Server version: 7.6.0 - r31469 @ Tue Oct 26 02:06:26 PDT 2010 Player version: 134 (?)
Created attachment 7028 [details] packets of successful manual reconnect
Created attachment 7035 [details] duet is diconnected, and can't reconnect
I can confirm similar behavior for my SB Receiver (Duet versions) - whenever SBS 7.6 is restarted, I have to manually restart the Receivers in order to be discovered by SBS. This behavior is around since I test 7.6 - I have not faced this in 7.5.x (I did not use 7.5.4) My Touch works without any such problem, also the DUET Remote works. Current Server version: 7.6.0 - r32390 @ Sun May 8 03:03:59 MDT 2011 Player versions: FW 71
oh - and sorry: platform is Operating system: Linux - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.10.0 - i686-linux-thread-multi Database Version: DBD::SQLite 1.31 (sqlite 3.7.2) running on a QNAP TS-439 Pro, SSOTS 4.12R3
Same here with an Ubuntu 32 bit serv with squeezeboxserver and the Squeezebox Receiver. Any chance to initiate a reboot of the receiver per network? Because powering it off and on again is a poor workaround.
*** This bug has been confirmed by popular vote. ***
Unassigned bugs cannot have a priority.