New Features/functions for Shoutcast Server 2

[iztari]

There are some features I would like to see in the next release of the Server software:

1) Possibillity to auto-ban/kick known ripper software.
2) A working kick/ban interface in the Admin interface (You can ban and kick, but the user is still connected with the SHOUTcast Server Version 0.2.0.0 0.0.7.0/posix).
3) Working Meta data information update sent to clients and YP directory.

[voodoohippie]

I think it should also have a "bad IP list" similar to Peer guardian but only dealing with companies who spam Shoutcast servers. Yesterday I have banned over 100 fake Winamp 5.0's. Everyone pretty much has at least 5.35 by now and the newest version is 5.8. I've seen where I'd kick off some false Winamp 5.0's and 5-10 more would come in and it took me a greater part of the day Yesterday to get them all blocked. Funny thing was almost all of these were German ip's according to utrace.de and http://ip-address-lookup-v4.com/ which I use to look up ip's with.

[Jkey]

The shoutcast 2 protocol allows you to use listener authentication.
You will be able to control who and what connects under those circumstances.

Its not the solution you are looking for,but it is a solution.

[pperkins1]

Every time this subject of "rippers" pops up around here there is someone who eventually comes on makes the "official" statement that Shoutcast/AOL will not discuss this due to liability issues.

P

[fc*uk]

Originally Posted by pperkins1

Every time this subject of "rippers" pops up around here there is someone who eventually comes on makes the "official" statement that Shoutcast/AOL will not discuss this due to liability issues.

P

We have no problems discussing rippers with respect to how to block people who are using them.

The point which we refuse to discuss is when someone posts "I wanna record my favorite song from my favorite internet radio station, can you plz help me!?!??!?!?!?111"

The above gets the reply about how we refuse to discuss the use of rippers on these boards.

[Jkey]

"I wanna record my favourite song from my favourite internet radio station, can you plz help
me!?"



Joking aside,As fc*uk says there is a clear difference.
There is no conspiracy,just common sense.


P.s fc*uk
if you are interested at all,
same url/pass as before, fixed version,just upped.

[MADxHAWK]

Originally Posted by voodoohippie

Funny thing was almost all of these were German ip's according to utrace.de and http://ip-address-lookup-v4.com/ which I use to look up ip's with.

Well i wont belive in ip lookup anymore cause it looks like there have been some changes in the IP pool.

Well im from germany, living nearl cologne and my current ip is 89.0.184.125

IP Lookup says:
Your IP: 89.0.184.125 Israel Near: Nahariyya, HaZafon, Israel

And i dont realy belive that my ISP uses DSL login server located in Israel

[Greg_E]

RIPE says you are in Cologne using NetCologne as the service provider.
http://www.db.ripe.net/whois?form_ty..._search=Search

I use Network Solutions whois, then RIPE whois, and sometimes Arin whois depending on where the IP points me to. Since I'm in the US most listeners are covered by Network solutions look up, RIPE handles most of Europe.
http://www.networksolutions.com/whois/index.jsp
http://www.db.ripe.net/whois
At the bottom of that RIPE page are links to a few other areas of the world like ARIN, LACNIC (latin america), etc.

[pperkins1]

I keep a page at http://www.ipchecking.com/ open all the time. So easy to quickly type in the IP address and verify exactly where the connection is from..
After watching your connection patterns you'll soon be able to tell legit listeners from the ripper robots. Keep in mind, you can ban 10,000 of them and they'll still connect using new IP addresses. The true solution is to be able to just stop their connection based on known fake media player type which should be a setting within the DNAS that the operator can add or delete types as he sees fit.

[voodoohippie]

That is why I say Ban anyone who uses say Winamp 5.0. Everyone has at least updated to 5.35 and a list of known updated clients should be enforced. I'll have to check out these other IP lookups cuz that may be easier than the one I use.

[fc*uk]

Will do my best to check that out jkey. Thanks!

[thinktink]

A couple of ideas for linux servers with iptables I haven't tried yet as I have like 5 other different projects going on at the same time at the moment:

1) Install and configure fail2ban to scan the SHOUTcast logs and then ban IPs with matching known ripper UAs. I haven't tried it myself yet but theoretically it's a sound idea.

2) Configure iptables to allow only one connection at a time for the same IP address on specific ports. I read somewhere some rippers like to have multiple simultaneous connections. It won't ban the first connection but it will prolly piss 'em off (you can do this on a DD-WRT modded router as well.)