Stream Rippers, already banned the ip on stream and website but they are back on the same ip

So I own a net radio (details in signature) and use centova, I noticed that there is an IP which i identified as a stream ripper (stealing the content (music) by ripping it from the stream), there is no option to ban on centova but there is on shoutcast which I have done, the ip is definitely listed as banned but yet they have somehow managed to get back on.

Add to this that their IP was also blocked from the website too on CPanel.

Anyone able to explain this and how to get rid of them bar block the whole country which i don't particularly wanna do.
It's the same IP they haven't returned on a different IP address

try blocking the user agent for just that ip, ive had simular issue with a bot or rogue user taking up multiple listener slots i banned the ip but the came back somehow, so blocked the user agent for that ip & solved it without affecting other ips using the same user agent, u can always unblock it if it doesnt solve it for you...

MoveDaHouse said:

try blocking the user agent for just that ip, ive had simular issue with a bot or rogue user taking up multiple listener slots i banned the ip but the came back somehow, so blocked the user agent for that ip & solved it without affecting other ips using the same user agent, u can always unblock it if it doesnt solve it for you...

Click to expand...

That's just it, I thought I got his user agent but I couldn't have as he is still ripping the stream.
How do I get the user gaent as I said he or she is using vox so i have blocked that domain, agent etc which is tied to the ip

Ok - I know - this is an old discussion from last year, but I think, BBMac is not the only one with a stream-ripper-problem.

I can give you a better solution, instead dayly blocking the newest stream-ripper-IP.

1.) How do stream-ripper-programs work?

They read out the title-Information. If a new title comes, an audio-file will be created with this name and the ripping begins. On next-title arrive, the file will be stored, and a new rip begins with the new title.

But this can only work, if next song and and next-title coming together exactly at the same time !!!

2.) What can I do?

Don´t send the actual title-information INSIDE the stream any more!
Send it DIRECTLY to the server, using the URL-Title-Update:

ht tp://serveraddress:8000/admin.cgi?pass=mypassword&mode=updinfo&song=title
ht tp://myradio-stream.com:8000/admin.cgi?pass=abc123&mode=updinfo&song=Skunk - Kiss Me!

3.) What will happen?

The next-title-update arrives now, before the song ends.
So EVERY song the ripper-software stores, is INCOMPLETE TRASH !

After the ripper notices this - the ripping comes to its end - guaranteed


By the way - the perfect stream-ripper confusion looks like this: