OK, mystery solved! Basically, I used tcpdump at the server and discovered that discovery requests were not arriving. The command is:
>tcpdump -i eth0 -n port 3483 I unplugged all squeeze devices from the network and then ran this command in a shell at the server. You can clearly see the req/ack packets happen when a device is plugged in. (Aside : oddly, one of the two controllers of the two Duets chats back and fore with the server regularly - the other doesn't. No idea why.) But when I did the same with my laptop and squeezeplay - I found nothing was getting there. I used to use VMWare on this laptop, and because of that there were various virtual interfaces defined. I wondered if these were confusing Squeezeplay, so I uninstalled VMWare (as I don't use it). bingo, it started working just fine. I guess Squeezeplay auto-selected the wrong interface. So anyone with more than one interface might have an issue, I would guess. (By the way - it took me a while to discover that the old slimp3 UDP protocol is not used anymore. Perhaps someone should mark it OBSOLETE in the wiki in big red letters and link to http://wiki.slimdevices.com/index.php/SlimProtoTCPProtocol ? Wireshark/tshark have a definition for this protocol, not the current one, also - tends to make you think it is current ;-) ) thanks for the help all! ------------------------------------------------------------------------ danmcb's Profile: http://forums.slimdevices.com/member.php?userid=36694 View this thread: http://forums.slimdevices.com/showthread.php?t=106510 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
