Re: [SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-28 Thread Slim
Code: --playeraddr 192.168.9.12 --cliaddr 192.168.9.12 --streamaddr 192.168.9.12 --httpaddr 192.168.9.12 Yes, this works. Thanks a lot to everybody. Is there any unforeseen consequence of the server not listening on 127.0.0.1? Slim -- Slim

Re: [SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-26 Thread JJZolx
pfarrell;410123 Wrote: > Look in your server.perf for the line: > bindAddress: 127.0.0.1 > > change to suit. > > Its usually in /var/lib/squeezecenter/prefs/ Comments in /server/Slim/Utils/Prefs.pm indicate that this is a MySQL Setting. To designate the server's IP address, add the following

Re: [SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-25 Thread Pat Farrell
Slim wrote: > question: I have Squeezecenter 7.3.2 running on Debian box with two NICs Look in your server.perf for the line: bindAddress: 127.0.0.1 change to suit. Its usually in /var/lib/squeezecenter/prefs/ -- Pat Farrell http://www.pfarrell.com/ ___

Re: [SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-25 Thread Slim
I vaguely remember from pre-Sueezecenter days the old Slimserver config file had something to specify an IP address. Default was 127.0.0.1 so to make it work over the network I had to type in the actual IP. -- Slim Slim's

Re: [SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-25 Thread SuperQ
I'm not sure there is an easy UI for changing it. Your best bet is to add a firewall rule to reject/drop requests on interfaces you don't want to be on. You want to cover these ports: * Port number: 3483 (TCP) - Name: SlimServer Control * Port number: 3483 (UDP) - Name: SlimDiscovery * Port Numb

[SlimDevices: Unix] Squeezecenter on Linux with multiple NIC's

2009-03-25 Thread Slim
Hi all, I hope I didn't miss the answer somewhere in the manuals. To my question: I have Squeezecenter 7.3.2 running on Debian box with two network interfaces connected to two different subnets. It looks like the Squeezecenter by default attaches itself to any interface it finds and listens/broa