> The following posted to unite the cows by Admin gbread49
> If anyone blocks these ranges and receives connection requests I
> would be interested to know.
>
> These are the "dangerous" IP ranges that I know of so far. They
> monitor p2p networks in an attempt to harvest IP's/upload files from
> file-sharers and then report the user to their ISP.
>
> RANGERINC:
>
> 216.122.215.13
> 216.122.0.0 - 216.122.255.255
> 216.122.204.0 - 216.122.223.255
>
> (Block with: 216.122.*.*) (rangerinc uses a broad range of IP's)
>
> MEDIA FORCE:
>
> 65.217.219.192 - 65.217.219.223
> 4.43.96.0 - 4.43.96.255
>
> (Block with: 65.217.219.* and 4.43.96.*)
>
> CYVEILLANCE:
>
> 65.118.41.192 - 65.118.41.223
> 63.148.99.224 - 63.148.99.255
> 63.64.0.0
> 63.127.255.255
>
> (Block with: 65.118.41.* and 63.148.99.* and 63.64.0.* and
> 63.127.255.*)
>
> AOL/WARNER MUSIC GROUP:
>
> 216.52.242.0 - 216.52.242.255
>
> (Block with: 216.52.242.*)
>
> ADDED: For those that don't know, the asterik (*) denotes a wildcard,
> and tells the application to block all numbers within that range.
>
> ADDED: If a p2p client also gives the option to add a "Netmask" with
> the IP range, use the following: (Shareaza for one does this)
>
> 255.255.0.0 or 255.255.*.*
>
> (Added: I don't take any credit for coming up with these IP's, they
> were collected from other fine folks posting on several other forums,
> I just compiled them here for all you fine cows... )
>
> ________________________________
>
> DANGEROUS IP UPDATES: (3 August 2002)
> (Quite a few, thanks to oscinis..
>
> The following IP's are an update/addition to the above listing. They
> were compiled from sources in other forums. NOTE: Several of the
> below ranges might cover a wider range than necessary, (its hard to
> narrow some of them down) however, personally I would rather
> inadvertantly block a few innocent IP's than to miss any of the bad
> ones. Use your own discretion....
>
> RANGERINC:
>
> 204.92.244.208
> 204.92.244.223
>
> (Block with: 204.92.244.*)
>
>
> MEDIA FORCE:
>
> 65.192.0.0
> 65.223.255.255
>
> (Block with: 65.192.0.* and 65.223.255.*)
>
>
> BayTSP:
>
> 209.204.128.0
> 209.204.191.255
>
> (Block with: 209.204.128.* and 209.204.191.*)
>
>
> VIDIUS:
>
> 207.155.128.0
> 207.155.255.255
>
> (Block with: 207.155.128.* and 207.155.255.*)
>
>
> OVERPEER:
>
> 65.160.0.0
> 65.174.255.255
> 65.160.127.0 - 65.160.127.255
>
> (Block with: 65.160.0.* and 65.174.255.* and 65.160.127.*)
>
>
> * Below are some of the "Spoofers/Spoilers" that have been
> identified: (Ones that have been known to flood the networks with
> fake files and may also be harvesting IP's)
>
> NetPD:
>
> 207.155.128.0
> 207.155.255.255
> 128.241.0.0
> 128.241.255.255
>
> (Block with: 207.155.128.* and 207.155.255.* and 128.241.0.* and
> 128.241.255.*)
>
>
> MediaDefender:
>
> 64.225.202.40
> 66.79.0.0
> 66.79.95.255
> 66.79.10.0 - 66.79.10.255
>
> (Block with: 64.225.202.* and 66.79.0.* and 66.79.95.* and 66.79.10.*)
>
>
> MPAA:
>
> 63.199.57.120
> 63.199.57.127
> 64.166.187.144
> 64.166.187.151
> 198.70.114.0 - 198.70.114.255
> 209.67.0.0 - 209.67.255.255
>
> Block with: 63.199.57.* and 64.166.187.* and 198.70.114.* and
> 209.67.0.* and 209.67.255.*)
>
>
> RIAA:
>
> 208.192.0.0
> 208.255.255.255
> 208.225.90.0 - 208.225.90.255
> 12.150.191.0 - 12.150.191.255
>
> (Block with: 208.192.0.* and 208.255.255.* and 208.225.90.* and
> 12.150.191.*)
Interesting post :o) How do I block ranges? Do I have to upgrade to ZA Pro
if I'm currently using the free version? It appears the only option I have
is to allow certain IPs and not to block them.
Mark
"Death_By_Courier" <markon...@hotmail.com> wrote in message
news:ak3i2d$1fippk$1...@ID-138495.news.dfncis.de...
> Yeah Mark send me a mail (USENETUSER in the subject field) and I'll
> send you a keygen if ya want.
Thank you :o)
Email sent.
"Death_By_Courier" <markon...@hotmail.com> wrote in message
news:ak3k74$1fbbdl$1...@ID-138495.news.dfncis.de...
Got a question. How do I stop the nagging bubble that says elements of the
webpage have been blocked? Looked in all the categories and can find no way
of turning the darn thing off.
Cheers
"Death_By_Courier" <markon...@hotmail.com> wrote in message
news:ak5s6t$1fubti$1...@ID-138495.news.dfncis.de...
"Death_By_Courier" <markon...@hotmail.com> wrote in message
news:ak5s6t$1fubti$1...@ID-138495.news.dfncis.de...
> Ooops hit the button too soon ....
> When you get the Privacy > Main menu on screen just click the _custom_
> button to disable _privacy advisor_
Ahh, the custom button. Just what I needed. Thank you :o)
I should mention, if you're using Shareaza, you can download a security.dat
file here:
http://members.lycos.co.uk/dave2030/Shareaza_Security_Update_v1.6_22-Aug-2002.zip
just put the security.dat file in your Shareaza directory, and you're ready
to go. It blocks the usual suspects: RIAA, RangerInc, Cyveillance, Media Force,
etc. Read the whole thread in Shareaza forums on this topic for more info: