Icecast Streaming Media Server

[Anonymous]

Two things kHarl:

1. On master-slave relay configuration the slave server should not connect as a “simple” listener to the mountpoints to relay*
or
please provide a function to reserve the IP address for the relay server IP to ensure that the relay server gets anytime a slot also when master mountpoint is full. (-> see Shoutcast RIP)

2. Relaying as “Master-Slave” the client should be automatically forwarded to the relay MP when the MP on the master is full. (-> see Shoutcast)

At the moment a playlist (tune-in link file) must be provided which includes not only the first but all icecast servers in the cluster.

Why do you plan in your branch version an further auth procedere for that fallback to slave MP? Master-Slave Relay requires already an authorization by the relay-user and relay-pass.

* What happens on the Easter event:
Master Icecast with listener time of max. 3 hours is full with 500 slots anytime. 3 other ICEcast Servers with further 500 slots do a Master-Slave Relay (but just one MP on master).
After 3 hours the first relay server was kicked by the master because the configured max. duration connection time was reached and then relay server was not able to connect back fast enough because master slots were full. Tow minutes later the second relay was kicked   Lost a lot of listeners

…
[2007-04-09 11:19:41] EROR slave/start_relay_stream Error from relay request: max listeners reached
[2007-04-09 11:20:42] EROR slave/start_relay_stream Error from relay request: max listeners reached
[2007-04-09 11:21:44] EROR slave/start_relay_stream Error from relay request: max listeners reached

[karlH]

1. If no authentication is passed then relays will be treated as just ordinary listeners. In -kh, the slave can pass the master-user/pass and the master can bypass the max-listeners check. yes I know, this needs expanding on so that relays can have individual user/pass.

2. If the slave (with the auth mentioned above) is also configured to pass details (master-redirect) to the master then the master will take the slave as registered for new listener redirection.

I'm not sure what you are getting at with the "further auth procedure". It's not possible to fallback to another server as that requires the player to create a new connection.

karl.