Hi all (especially gonosztopi)
I have a question about the compatibility of aMule's ipfilter.dat and PeerGuardian blocklists.
On blocklist.org, where you can download PeerGuardian blocklists, there are 3 versions available. Is aMule's ipfilter.dat compatible to all versions? (The wiki is not clear about this, so please tell me and I will tell Jacobo221).
I'd like to use a Version1 list (PeerGuardian plain text) which I created from some blocklist.org-lists.
I've tested it on two computers (one Debian stable and one Debian testing) with different results:
PeerGuardian tells me, that my list contains 83990 ranges and 2344303895 IPs
aMule 2.0.3 (dude's Debian stable package) tells me about 83000
IPs are filtered.
aMule CVS (20050913) (vollstrecker's Debian package) tells me 83979
ranges are filtered (11 malformed lines were discarded, but I think that's not a problem).
So I think in aMule CVS everything is working as I expected but I'm unsure about the stable (2.0.3) version. Are the whole ranges blocked or just the first IP of each range? In the changelog I couldn't find something relevant.
One example line from my ipfilter_static.dat:
Bogon:0.0.0.1-2.255.255.255
While the wiki/index.php/Ipfilter.dat_file gives me:
IPs range values are described by an initial IP a dash and the ending IP of tha range (the dash must be separated from the IPs by a single space character).
000.000.000.000 - 000.255.255.255 , 000 , "This" Network [RFC1700, page 4]
Is the syntax from the wiki the only one that is accepted by ipfilter.dat? It seems to me that at least in the CVS-version other syntaxes are also working.
Thank you for your good work and your reply

jere