Icecast Streaming Media Server

[Anonymous]

Hiya

I'm running Icecast 2.3.2 on a Windows 2003 Box as a service.

I've tried to create passwords for individual mount-points and it doesn't seem to work. I've googled alot and other people experience the same problem.
Do the password feature work for windows, or not?

If it does work, can some1 please provide me with an example config?

Here is mine:

[karlH]

I've not heard of reports of issues with per-mount passwords not working. The only cases that have been mentioned were down to a configuration error typically caused by the mount section being commented out in the xml. There's no reason for windows to not have this feature. The snippet you posted looks ok but obviously I only see a small fragment.

There's no /admin mechanism to dynamically add IPs to the ban/accept files. You can of course use a web server script to do that if you wish, icecast will automatically re-read them.

karl.

[Anonymous]

Hiya Karl!

Thanks for the rapid responce!

Please find below our full config, with obvious passwords and ports masked:

[karlH]

wow mp3pro, didn't know anyone still used that. Either way, it will pass through just like mp3 does.

The xml looks valid, obviously you have to check the error log to be sure of the exact reason for rejection, it could be down to a low clients setting.

karl.

[Anonymous]

yup mp3pro suites use better than ogg as that crashes winamp and still isnt very stable.

ok i've put the max clients and source both to 100 from 5, and still i get the error:

[karlH]

I know winamp is not that great but I haven't heard much of ogg in winamp crashing, but then I don't use windows.

The mountpoint from the log snippet indicates that you'll be matching the global source password (/tomtaylor != /tommy) so the username is source and the password needs to be whatever you set in source-password.

Yes 2.3.2 has banning ip support.

karl.

[Anonymous]

how should the mount-points be setup in the xml so each one can have its own password??

how can the global source-password be disabled?

i've not changed anythin since i posted my config above, so use that to make any changes

if i wanted to ban an ip on the win32 version, how would i?

thanks again

[karlH]

Each broadcaster/DJ would have their own mountpoint with each mount having it's own username/password combination.

You don't disable the global source password, you just don't give it out. I don't intend to make changes to the xml as it looks fine, the connection is just being rejected because the passwords (whatever they are) don't match.

As mentioned in docs

<paths>
...
<deny-ip>/location/of/file/with/IPs</deny-ip>


karl.

[Anonymous]

thanks for the ban ip support, ill check that out

with regards to the passwords for each individual mountpoint, there must be a bug then as the passwords are the same, i shouldnt be getting a 401 error on both the source and the icecast server??

i've noticed alot of people have problems with this, it possibl you can test it out, as im sure it doesnt work - if you say my config is correct?

thanks again

[karlH]

I can only say general comments based on what little information you are giving me. What other reports of source auth failure are you referring to?

Your xml is correct but you have blanked out the passwords and I have no idea what your source client is trying to authenticate as. You may of changed the xml without restarting icecast. There's just too many missing factors that prevent me giving something more precise.

karl.

[Anonymous]

hiya karl

lol not every1 on this forum asking for help is thick haha every time i've made a change to the config xml, i always restart it

right i've managed to fix it and make it work, job done

last question i have is, is it possible to force icecast to reload the latest config xml, without restarting the service in windows??

thanks again

[karlH]

Can you post what the problem was, for other people.

The 2.3 code on windows doesn't have the hook for reloading the xml yet, you can in my branch by selecting a link on the admin page. It doesn't seem to have an issue so that could be merged without issue.

karl.

[Anonymous]

Hiya

I restarted the box, added another mountpoint and reformatted the mount-point and it seemed to work ok then

How do i get a copy of your windows version so i can try it out?
Will it be merged into the 2.3.2 build, as i can see on your website its only on 2.3.1???

Thanks again

[karlH]

2.3.1-kh34a is my latest, it has everything 2.3.2 has, I'll be renumbering the next release now that 2.3.2 is out.

karl.

[Anonymous]

ok great stuff!

what new features can we look forward to in the next version?