Icecast Streaming Media Server

[Anonymous]

Hi everyone,

I try to setup a streaming server with icecast using relays. I defined master server like this:

<icecast>
<limits>
<!--<clients>100</clients>
<sources>2</sources>-->
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>

<authentication>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
<relay-user>relay</relay-user>
<relay-password>hackmerelay</relay-password>
</authentication>

<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>

<mount>
<max-listeners>20</max-listeners>
<mount-name>/produitlive.ogg</mount-name>
<username>superlogin</username>
<password>superpassword</password>
<authentication type="url">
<option name="mount_add" value="http://liveauth.viewsurf.com/"/>
<option name="mount_remove" value="http://liveauth.viewsurf.com/"/>
<option name="listener_add" value="http://liveauth.viewsurf.com/"/>
<option name="listener_remove" value="http://liveauth.viewsurf.com/"/>
</authentication>
</mount>


.....
...


The slave is defined like this:
<icecast>
<limits>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>65535</burst-size>
</limits>

<authentication>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>

<master-server>192.168.10.51</master-server>
<master-server-port>8000</master-server-port>
<master-update-interval>10</master-update-interval>
<master-username>prout</master-username>
<master-password>hackmerelay</master-password>

<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions here.
The default is 0 -->
<relays-on-demand>0</relays-on-demand>

<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>



The mointpoints defined on the master are correctly relayed on the slave. But the authentication options seems not to be forwarded to slave.

mplayer http://master:8000/produitlive.ogg => failure , username/passwd required
mplayer http://slave:8000/produitlive.ogg => stream is played

Does someone know how to make authentication options defined per mount on the master available on the slave ?

Regards

[karlH]

The mount settings are not passed via the slave mechanism because invariably they differ between master and slave. If you want the same auth mechanism on the slave then define the same mount auth for the mountpoint on the slave.

karl.

[Anonymous]

Do you have a master and slave configuration file example ? I made many tests to apply auth settings per mount on the slaves unsuccessfully.

Regards

[karlH]

Just copy+paste the mount section from the master xml to the slave xml.

karl.