PDA

View Full Version : Problem finding server with multiple IPaddresses



Michael Carland
2005-08-04, 13:14
Howdy.

I have 3 Squeezeboxen that have worked well for quite some time now. Of
course I had to go and mess with them.

I am running SlimServer 6.0.1 on Linux. I have looked at the changelogs
for the newer versions, and do not see my issues in the lists.

It started on a bored evening. I'm running SlimServer on my fileserver,
which is already running apache on port 80. Instead of using the url
http://fileserver:9000/ I was going to set up http://slimserver/. I added
an additional IP address to the server, brought it up, and configured
Apache to only bind to the original IP. I then tried to get SlimServer to
use the new IP and port 80 for the HTTP interface.

Here are the two problems.

First off, I start SlimServer as root, with a "--user slimp3d" option.
SlimServer changes to the slimp3d user before it binds to port 80, so of
course this fails, as only root can open ports below 1024. I know that
other applications (eg Apache) open the port first as root, and then
change their uid. I suppose I should just file this as a bug?

The second problem is that the players no longer find the server
automatically anymore. I didn't care if the server bound to both IP
addresses, but I tried "--playeraddr 192.168.78.182" and the players still
didn't automatically find the server. If I reset the players, and manually
set the server address, they work fine. Any ideas on how to get the
autodiscovery working again?

Thanks,

-Michael

max.spicer
2005-08-04, 14:34
Why do you need two IP addresses to get your server to be fileserver and slimserver? If you have a proper DNS server, you just need to add a cname of slimserver for the existing ip. If you're relying on hosts files, you can just add two entries for the ip. Or am I missing something? ;-)

Max


Howdy.

I have 3 Squeezeboxen that have worked well for quite some time now. Of
course I had to go and mess with them.

I am running SlimServer 6.0.1 on Linux. I have looked at the changelogs
for the newer versions, and do not see my issues in the lists.

It started on a bored evening. I'm running SlimServer on my fileserver,
which is already running apache on port 80. Instead of using the url
http://fileserver:9000/ I was going to set up http://slimserver/. I added
an additional IP address to the server, brought it up, and configured
Apache to only bind to the original IP. I then tried to get SlimServer to
use the new IP and port 80 for the HTTP interface.

Here are the two problems.

First off, I start SlimServer as root, with a "--user slimp3d" option.
SlimServer changes to the slimp3d user before it binds to port 80, so of
course this fails, as only root can open ports below 1024. I know that
other applications (eg Apache) open the port first as root, and then
change their uid. I suppose I should just file this as a bug?

The second problem is that the players no longer find the server
automatically anymore. I didn't care if the server bound to both IP
addresses, but I tried "--playeraddr 192.168.78.182" and the players still
didn't automatically find the server. If I reset the players, and manually
set the server address, they work fine. Any ideas on how to get the
autodiscovery working again?

Thanks,

-Michael