fpo wrote: > SO_KEEPALIVE is optional under Windows. I can't see that squeezelite has > SO_KEEPALIVE enabled on the socket. It seems LMS will just reset the > socket after some default timespan, at least I see a "TCP Reset" frame > from the host.
Except that 10053 points to either the client or some network component closing the socket. If LMS closed the connection you would have seen a 10054. Should also note that retransmit requests are not done by the receiver (i.e. the peer waiting for some response) but the sender. Since the socket is created as "non blocking", not receiving an ACK from the server likely causes the app to go into a loop until finally giving up (and generating the 10053), which explains the 100% CPU you're seeing. Is your switch capable of port mirroring? If so you could bind your Pi to receive the same data as the windows machine and use tcpdump to verify what wireshark is telling you on the Windows machine. This would allow you to see whether it is the outgoing traffic being blocked, or the incoming. ------------------------------------------------------------------------ gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=113554 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
