My server has multiple NICs and LMS inevitably considers the one with a
public IP [no, the internet does not have access to the LMS services] to
be the "local" network, leading to the CLI interface not working from
the actual LAN:
[21-02-06 14:54:53.8613] Slim::Plugin::CLI::Plugin::cli_socket_accept
(250) Access to CLI is restricted to the local network or localhost:
192.168.1.43
I have attempted a few different fixes without success:
- Set bindAddress to the LAN IP in server.prefs. Doesn't seem to make
any difference, service still listens on * rather than the specified
IP.
- Set allowedHosts to the LAN subnet in server.prefs. Doesn't make
any difference to CLI.
- Add SLIMOPTIONS="--httpaddr 192.168.1.3" to
/etc/default/logitechmediaserver
The only thing I've found so far that works is to down the NIC that it
assumes is local, restart LMS, then up the NIC. Once the NIC is back up,
the Server IP Address reported on the status page goes back to the
public IP [but the CLI interface still works].
Seems like the logic here:
https://github.com/Logitech/slimserver/blob/public/8.2/Slim/Utils/IPDetect.pm
prefers the interface with the public IP rather than the private,
because the one with the public IP has the default route on it.
How can I hard-code the local network, or at least hint to LMS what I
want it to do?
------------------------------------------------------------------------
troffasky's Profile: http://forums.slimdevices.com/member.php?userid=70248
View this thread: http://forums.slimdevices.com/showthread.php?t=113868
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
