In my case I found one mistake, but it does not fix the problem.
Part of the change from CentOS with a working 7.9.0 LMS to Debian was that I implemented IPv6 and rewrote all my firewall rules using nftables. It seems that the reply to a UDP broadcast does not fall under the "established/related" check. Now that I have fixed that, the SB1 still cannot find the server. Tried: - 7.9.4 (same result); - 7.7.7 fails to connect to any network ports, so I gave up quickly on that; - 8.0.1 (same) Using packet capture on the server, I can see the port 3843 discovery reply going back to the SB1, but it ignores it and tries again with the broadcast discovery request. Network traffic is OK to/from the SB1, as I can see the DHCP and the ARP packets flowing as expected. Wireshark dissection of the reply disagrees with the actual message content. The reply packet: first byte: 0x44 payload remainder is the text "files" followed by 12 nulls padding , which is the server hostname, minus any domains. The Wireshark dissector thinks the packet should contain the IPv4 address followed by port number, but it certainly does not. The server itself is running on a VM, has multiple (virtual) ethernet ports as well as interfaces for vpn endpoints. I think the CentOS structure was similar in this regard. ------------------------------------------------------------------------ CameronD's Profile: http://forums.slimdevices.com/member.php?userid=65245 View this thread: http://forums.slimdevices.com/showthread.php?t=113533 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
