The software was obviously written with the assumption that the network information it gathers from the interfaces available is what the outside world can reach it under. While this *does* work for running on dedicated hardware or with --net host, it doesn't work in more elaborate environments e.g. Kubernetes.
Yes, correct: LMS started development a long time before everybody thought they'd need datacenter technology on their 35USD Raspberry Pi :-).
Joking aside, let's try to understand what the actual issue is here.
I took care of managing traffic going in correctly, though the information lms reports to the player device isn't what it's supposed to report. tcpdump confirms that my SqueezeBox Radio tries to establish contact to lms via the 10.0.0.0/8 internal cluster ip the container was assigned.
Is Kubernetes NATing the traffic?
So is there a possibility to force lms to report a specific IP address to the player devices?
I don't think the IP address is the problem here, but rather the port mapping. Maybe you should start by providing actual information about your setup before you jump to conclusions.
(and no, no tcpdump required, just configuration details) -- Michael _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
