Steps to replicate:

1. Download p2p.p2b from blocklist.org
2. run 'peerguardnf -n p2p.p2b'
3. run 'peerguardnf -m -h p2p.p2b'

Result:

"""
Reading blocklist
detected ASCII blocklist
Blocking 1 ranges (4294967250 IP addresses)
"""

All network communication is then blocked (including
localhost!). This also happens when peerguardnf is run
as a daemon.

This is probably either a bug in p2p reading or p2b
conversion. This bug deserves attention, because it
effectively prevents the user from running peerguardnf
with more than one blockfile (eg. 'cat p2p.p2b.p2p >>
guarding.p2p; cat gov.p2b.p2p >> guarding.p2p' etc.)

Incidently, peerguardnf works fine with p2b files.

Specs:
ubuntu linux (ppc)
pglinux CVS as of Aug 6, 05.

In an effort to make this tracker usable again, this report is closed.

If this report relates to the PeerGuardian Windows application, you
may try PeerBlock instead: http://www.peerblock.com.

If this report relates to an IP that is blocked or not blocked: The
blocklists are maintained by http://www.bluetack.co.uk and
http://tbg.iblocklist.com.

If this report is about failed blocklist downloads. Check out
http://iblocklist.com, this site offers reliable downloads of all
blocklists.

In an effort to make this tracker usable again, this report is closed.

If this report relates to the PeerGuardian Windows application, you
may try PeerBlock instead: http://www.peerblock.com.

If this report relates to an IP that is blocked or not blocked: The
blocklists are maintained by http://www.bluetack.co.uk and
http://tbg.iblocklist.com.

If this report is about failed blocklist downloads. Check out
http://iblocklist.com, this site offers reliable downloads of all
blocklists.