Icecast Streaming Media Server

[JohnM]

I've used authentication type="url" on mount's, but I don't see anything comparable for relays. Is there anything in the KH builds (perhaps undocumented) that allows user authentication on relays?

Thanks in advance.

[karlH]

relays are on mountpoints, always have been. just as say max-listeners applies to mounts whether they are from source clients or relays, authenticiation also applies to mounts in the same way.

karl.

[JohnM]

Thanks for your reply, Karl, but I'm not sure I understand your response. Maybe I'm missing something.

Seems reasonable (to me at least) that you might want to authenticate players connecting to <relay> points but I don't see anything in the documentation that allows for this. The authentication only seems to be a valid node within a <mount>.

For example, this is how I'd want/imagine my relay to look:

[karlH]

so you want the <relay> block without authentication and then

<mount>
<mount-name>/stream1</mount-name>
<authentication type="url">
<option name="listener_add" value="http://myauthserver.com/scripts/add_listener.php"/>
</authentication>
<mount>

as you can see, authentication for the mount belongs in the mount.

karl.

[JohnM]

Thanks Karl -- I'll try that. I didn't realize you could have a <relay> and a <mount> for the same stream on the same server.

[square_eyes]

I think a good way of explaining it is that mount settings are for defining additional config for connected (or potentially connected) sources, which include relays configured in the relay section, as well as traditional sources.

You actually don't have to define a mount for Icecast to host a source and you listen to it.

It's only when you introduce authentication, fallback or want to define things like meta data (stream title, bitrate etc) that you need to define a mount. Even then, your source is probably sending that meta data any way.