Icecast Streaming Media Server

ardya · Joined: 22 Mar 2009 Posts: 20

Hi folks, having just resolved a directory listing issue, I'm confused about the bind-address statement in the config.

On server machines with more than one IP, bind-address can be used to bind to a specific IP. In a tcpdump I saw YP requests going out on a different IP than what was set with bind-address.

1. MUST the hostname statement match the IP set in bind-address?

2. Does bind-address have any effect on what src IP is used to make the YP updates?

Thanks

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

The bind-address is really for listening sockets not outgoing ones

1. No, icecast cannot assume that the local address to bind to is the actual address listeners will use, consider if you were behind a NAT and the bind-address was 192.168.1.100

2. no, it's only to handle the incoming requests received by icecast.

There is an argument to allow a bind address for directory connections which would probably be specified in the <directory> blocks but there's been no need for it so far.

karl.

ardya · Joined: 22 Mar 2009 Posts: 20

Thanks for the reply Karl...

Here's another question.

I have an IPv6 only server, it acts as a relay to an IPv4 only icecast server, to serve the station stream over IPv6.

This IPv6 server is public, but doesn't show in directory listings.

Is this because there's no IPv6 support at dir.xiph.org?

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

I suspect that is the case although I'm not sure. While you can have a hostname that maps to either, if it was just an IPv6 then probably not. I would probably advise against using an IPv6 only setting for now as listeners would get confused. I suspect the issue on the YP server end is just the network routing for verification.

karl.