Peerguardian blocklist not updating

The original Peer Guardian (1.0) was programmed in Visual Basic and quickly became popular among P2P users despite blocking only the common TCP protocol and being known for high RAM and CPU usage when connected to P2P networks.

By December 2003, it had been downloaded 1 million times. After 7 months of development, in February 2005 Version 2 of Peer Guardian was released as a beta.

Searching the threads and forums suggest disabling it, allowing http, updating, re-enabling etc... Anyone out there aware of this issue and advise a solution or has a new URL to direct the P2P list at?

And the best thing about PG2 is that it isn't just a text file updater for P2P apps like BLM, it's a network tool that I can keep running even after shutting down my P2P app, which depending on your lists, can save you valuable bandwidth and protection from bad sites when browsing the web. PG2 blocked whirlpool about 5 years ago because of an over-zealous blocklist, as did Protowall (from the same people who brought you BLM) because they were using the same list produced by Bluetack.

The aim of its use was to block peers on the same torrent download from any visibility of your own peer connection using IP lists.

The system is also capable of blocking custom ranges, depending upon user preferences.

Even worse - especially since so many people have been downloading Peer Block this weekend - this means that Peer Block may not be able to download any lists when you first install it! Many people on the PG2 forums have been using i Blocklist lists for quite awhile now, and everybody seems extremely pleased with them.

Normally this traffic is whitelisted automatically as long as you keep the default setting WHITE_LOCAL="1".If BLM was around back then, then depending on the list it used, it would've blocked WP too.As they say, PG2 (or BLM for that matter) is only as good as the lists it uses.Peer Guardian is a free and open source program developed by Phoenix Labs.It is capable of blocking incoming and outgoing connections based on IP blacklists.