| View previous topic :: View next topic |
| Author |
Message |
square_eyes
Joined: 18 Oct 2011 Posts: 83
|
Posted: Wed Feb 27, 2013 1:00 am Post subject: Combatting Rippers |
|
|
I checked my Centova Panel today and had 10 listening clients from various IPs (US, Germany, Brazil) all connected for a similar period of time.
User Agent: Fmod Sound System 3.75
Agent Type: Ripper
I don't mind if my stream is ripped, but if they are reselling it's taking the piss a bit.
I couldn't find anything on here so I thought I'd open a discussion on how one might go about dealing with these people. I see it as a problem because...
1. I have a cap on listeners.
2. I program this station, and our DJs work hard on content. It's rough if the ripper ends up profiting off our work, leeching our bandwidth and potentially re-streaming our station as their own.
What experiences have you had? What tools does Icecast have to address this?
Last edited by square_eyes on Wed Feb 27, 2013 1:13 am; edited 1 time in total |
|
| Back to top |
|
 |
square_eyes
Joined: 18 Oct 2011 Posts: 83
|
Posted: Wed Feb 27, 2013 1:03 am Post subject: |
|
|
When I try to kick the listener through the Icecast Admin Panel I get the below and the listener remains...
Response
Message : Client 0 not found
Return Code: 0
Also...
There's some good info here. But not all relevant to Icecast.
http://forums.streamsolutions.co.uk/archive/index.php/t-2758.html |
|
| Back to top |
|
 |
square_eyes
Joined: 18 Oct 2011 Posts: 83
|
Posted: Thu May 09, 2013 7:43 am Post subject: |
|
|
| I'm still unable to kick listener clients. Is this a common problem? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu May 09, 2013 11:56 am Post subject: |
|
|
the client id is unique, so you should get different numbers for each listener.
karl. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun May 12, 2013 12:07 pm Post subject: |
|
|
If the issue is that the id value is missing then on the kick url on centova or similar set ups then it is probably down to a mismatch on the xsl pages between 2.3.2 and KH. I've committed a fix to allow that to work.
karl. |
|
| Back to top |
|
 |
|