AMule Project FAQ - User contributions [en]

Ipfilter.dat file

2005-09-16T12:20:59Z

85.74.46.121:

== File ==

'''Name:''' ''ipfilter.dat''

'''Location:''' ''~/.aMule/''

== Description ==

The usefullness of this file is described in the [[IPFilter|IP Filter article]].

== Format ==

The format of the ''ipfilter.dat'' file is as follows:

'''[[IP]]s range , Access level , Description'''

''Access level'' values '''lower than 127''' are ''blocked [[IP]]s''' and values '''over 127''' are '''allowed [[IP]]s'''.

''[[IP]]s range'' values are described by an initial [[IP]] a dash and the ending [[IP]] of the range.

== Example ==

''000.000.000.000 - 000.255.255.255 , 000 , "This" Network [RFC1700, page 4]'' 
''169.254.0.0 - 169.254.0.255 , 000 , Link local'' 
''192.168.0.0 , 192.168.255.255 , Optionally block my LAN'' 
''127.0.0.0 , 127.255.255.255 , Optionally block localhost (Loopback)''

Talk:IPFilter

2005-09-16T12:12:13Z

85.74.46.121:

'''1)The Peerguardian antip2p filter (http://www.methlabs.org/sync/) 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 [http://forum.amule.org 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.

Greetings!

----

Well, aMule supports the PeerGuardian lists (only version 1).
So I added their source (blocklist.org) 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 blocklist.org) or also web-addresses that have lists that you can manually insert (you can do this with blocklist.org). 
See also [http://forum.amule.org/thread.php?threadid=7389&sid= 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)

IPFilter

2005-09-16T11:51:22Z

85.74.46.121: PeerGuardian/Blocklist.org Version 1 lists are supported

== Description ==

The [[IP]] Filter blocks traffic from/to IPs and ranges of [[IP]]s with our [[client]]. This means that those [[IP]]s which get blocked will not be able neither to upload to us nor to download from us.

This filter is read from [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] which is a file which's contents describes the valid and blocked [[IP]] ranges.

== [[ipfilter.dat file]] ==

The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].

== Using the [[IP]] Filter in [[aMule]] ==

The ''Access level'' of the [[IP]] filter is selected in [[aMule]] through "Preferences" -> "Security" -> "IP Filtering" -> "Filtering level" (in [[aMule]] versions up to 2.0.0-rc8 it is under "Server", instead of "Security").

'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s ([[eMule]]'s [http://www.methlabs.org/methlabs.htm PeerGuardian] format (Version 1), which is the most popular. The ''antip2p.txt'' format isn't yet supported).

== [[IP]] Filter sources ==

http://emulepawcio.sourceforge.net/nieuwe_site/Ipfilter_fakes/ipfilter.dat (Last update: 28 August 2005)

http://www.openmedia.info/p27.html (Last update: 30 April 2005)

http://www.emulext.net/seguridad/Mc4TuTi/ipfilter.dat (Last update: February 2005)

http://www.autistici.org/smokingmath/ipfilter.dat (Only filters [[fake]] [[server]]s. Last update: 8 August 2005)

http://www.blocklist.org/lists.php (Different lists. Daily updates)
== Hard coded [[IP]] filter in [[aMule]] ==

[[aMule]] has a range of [[IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. This ranges are:

<pre>
Address Block Present Use Reference
----------------------------------------------------------------------
"0.0.0.0/8", // "This" Network [RFC1700, page 4]
"10.0.0.0/8", // Private-Use Networks [RFC1918]
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]
"24.0.0.0/8", // Cable Television Networks --
"39.0.0.0/8", // Reserved but subject
// to allocation [RFC1797]
"127.0.0.0/8", // Loopback [RFC1700, page 5]
"128.0.0.0/16", // Reserved but subject
// to allocation --
"169.254.0.0/16", // Link Local --
"172.16.0.0/12", // Private-Use Networks [RFC1918]
"191.255.0.0/16", // Reserved but subject
// to allocation --
"192.0.0.0/24", // Reserved but subject
// to allocation --
"192.0.2.0/24", // Test-Net
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]
"192.168.0.0/16", // Private-Use Networks [RFC1918]
"198.18.0.0/15", // Network Interconnect
// Device Benchmark Testing [RFC2544]
"223.255.255.0/24",// Reserved but subject
// to allocation --
"224.0.0.0/4", // Multicast [RFC3171]
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]
</pre>

However, you can un-filter this range of [http://www.faqs.org/rfcs/rfc791.html IP]s by unchecking "Preferences"->"Security"->"IP-filtering"->"Always filter bad IPs" (on [[aMule]] versions up to 2.0.0-rc8, this option can be found in "Preferences"->"Server"->"Always filter bad IPs").