How Does The "block Bad Ip Ranges Work" ?

[The_Guru]

Now we have all heard about RIAA...Does it prevent them auctually displaying fake MP3's? or just stop them connecting to your machine?

Because what happens if it only stops them connecting to your machine? BEcause if you download a MP3 from them your busted arn't you?

please help (a bit worried)

[MUSLEMAN]

riaa has different ways of geting you. the ipblocker will not stop them.

first of all there is no way to find and block all the ip ranges for the riaa

second even if we did find them they can easily change their ip and ranges.

the ipblocker just blockes the ranges we know of, that riaa uses and its mainly for blocking bs sources for the files so you have a less chance of getting a bs file

if you want to make it very hard for the riaa to get you then use a socks5 proxy,

you can get good ones here

[Switeck]

Originally posted by MUSLEMAN@1 February 2004 - 05:33
the ipblocker just blockes the ranges we know of, that riaa uses and its mainly for blocking bs sources for the files so you have a less chance of getting a bs file

if you want to make it very hard for the riaa to get you then use a socks5 proxy,

Even if the block ranges are ineffective against all the RIAA scanning, they ARE pretty effective at blocking accidental download off one of the very well-known MP3 fake servers that RIAA has set up.

I have made posts in other threads saying basically that the RIAA blocklist in KL++ is good but not great. It IS however more effective than using the SAME blocklist in Peer Guardian while running Kazaa/KL++.

A socks5 proxy may not be effective enough on Kazaa/KL++ because Kazaa/KL++ reports a computer's local ip in its datapacket headers. This is why I had a world of troubles with the 192.168.x.x Kazaa "DDoS attack" because of my router. The socks5 proxy may hide your connection ROUTE but not your ip address, so they may know your ip but be unable to connect directly to your ip. Or maybe not -- it depends on how 'firewalled' your system is to unsolicited outside access outside of the socks5 proxy connection.