Icecast Streaming Media Server

[jmashore]

I'm trying to implement the <deny-ip> tag in the paths section using the following config :
<paths>
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<alias source="/console" dest="/index.html"/>
<alias source="/7.html" dest="/7.xsl"/>

<alias source="/" port="8199" dest="/High"/>
<alias source="/" port="8201" dest="/Low"/>

<alias source="/listen.pls" port="8199" dest="/listenhigh.pls"/>
<alias source="/listen.pls" port="8201" dest="/listenlow.pls"/>

<deny-ip>/path/to/MyApache/htdocs/BannedIP.txt</deny-ip>
</paths>

The file exists and has a IP in it. I then executed a reload from the web admin interface. Checking the logs, (Debug=4) I see no complaint, however, the client remains connected.

So I'm wondering, is the path in the deny-ip relative to an alternate root that I'm not catching ?


WIN 32 KH

[Jorgo]

From my limited understanding of how these things work, an existing connection will not be terminated, rather new connections from banned IPs will be prevented. So it may not be a path problem.

[jmashore]

I thought that might be the case too, but no such luck. I tried disconnecting my test client and reconnecting and had no problems reconnecting.

[karlH]

When a client connects, you should see an attempt at reloading the specified file when it has been modified (eg touch /path/to/MyApache/htdocs/BannedIP.txt).

karl.

[jmashore]

yeah..I'm not seeing that anywhere in the error.log and I have debug set to 4..that's why I thought I had boggled the path.