From AMule Project FAQ
Jump to: navigation, search

1)The Peerguardian antip2p filter ( is much bigger than the given ipfilter.dat (almost 7000 lines bigger).
Which one is the most uptodate? (I can actually guess that!) Up to date? hard to know. probably both are more or less the same. But loafing a large ipfilter requieres quite some CPU/MEM usage and might not be really a good idea in some environments, depending on what it is actually filtering.

2)Two filtering levels are defined, one in the ipfilter.dat file and another in preferences->security->ip-filter-filtering level.
Which one applies?
No idea, sorry. Ask Phoenix at forums or at aMule's IRC channel.I guess the one at preferences is the one used unless the file already assiges one (AFAIK, there's no way to have a file to hard-set a security number, but if you say it does...).
Why are there so many filtering levels (0,1,...127,128,...)???
There are so many so that you can decide what to filter and what to not filter without having to re-edit the whole file. Just changing the security value in Preferences.


I have a question to this:

NOTE: aMule's ipfilter.dat file is 100% compatible with eMule's (eMule's PeerGuardian format, which is the most popular. The antip2p.txt format isn't yet supported).

Question: On, where you can download PeerGuardian blocklists, there are 3 versions available. Is aMule's ipfilter.dat compatible to all versions? I'd like to use a customized Version1 list (PeerGuardian plain text).

I have really no idea at all. Please test and report what you find out :)

Well, depends on the version (the original list contains 83990 ranges and 2344303895 IPs):
2.0.3 (dude's Debian stable package) tells me about 83000 IPs are filtered
CVS (20050913) (vollstrecker's Debian package) tells me 83979 ranges are filtered (11 malformed lines were discarded).
So i'm unsure just about the stable (2.0.3) version. Are the whole ranges blocked or just the first IP of each range?
One example line from my ipfilter_static.dat:
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 , "This" Network [RFC1700, page 4]

Non valid IPs are discarded. Also, if a line discribes a range in a nonvalid way, not only the first IP will be discarded, but the whole range, since aMule won't be able to understand its meaning.

I'm not sure if I understood what you were saying, but I hope I did ;)

You could ask at if you wish, since gonosztopi is checking forums there and he's the one who wrote the IPFilter code. If you get to some conclusion... please report here :)


Well, aMule supports the PeerGuardian lists (only version 1). So I added their source ( to IP Filter sources. But I'm not sure what IP Filter sources is intended to list:
only web-addresses from which you can automatically update the ipfilter.dat (you can't do this with or also web-addresses that have lists that you can manually insert (you can do this with
See also this thread

Also see that the log message in 2.0.3 is slightly inaccurate, but the actual behavior is what you would want/expect. It is always ranges that are filtered, not individual IP addresses.

Greetings and Thanks
jere (I can't login for the wikis, but in the forum I can)

Thanks a lot for the update :)

The antip2p.txt format isn't yet supported.
Is this about the former bluetack antip2p.txt? This list is called level1.txt now and it works fine with me. So, if yes, just kick this sentence.

Sorry, I don't I understand what you mean. I'm not quite good at IP Filter ;)

I'm talking about this paragraph in the IPFilter-article:
NOTE: aMule's ipfilter.dat file is 100% compatible with eMule's (eMule's PeerGuardian format (Version 1), which is the most popular. The antip2p.txt format isn't yet supported).

Here on the bluetack homepage I found this:
There are no longer any default lists in the Blocklist Manager and the Anti-P2P list is now called the Level 1 list.
Here they say about the Level 1 list:
Description: The Antip2p list that is used by most p2p software Nuff Said

So I think antip2p.txt was a bluetack-list. As I can see PeerGuardian/methlabs/ and bluetack have the same list-format. It's not exactly the same as described in the Ipfilter.dat but very similar and when I tested these lists, they all worked fine.

I propose to change the paragraph in the IPFilter-article to this:
NOTE: aMule's ipfilter.dat file is 100% compatible with eMule's (eMule's PeerGuardian format (Version 1), which is the most popular.

Or perhaps to:
NOTE: aMule's ipfilter.dat file is 100% compatible with eMule's.


Of coruse, feel free to modify IPFilter and ipfilter.dat file articles to suit what actually happens on aMule. You definitely know much more than I do about this ;)

Thanks a lot for your research!