Difference between revisions of "IPFilter"

From AMule Project FAQ
Jump to: navigation, search
(removed invalid link)
m
Line 31: Line 31:
 
=== IP Filter sites ===
 
=== IP Filter sites ===
  
You can insert the lists from these sites either manually or with a script. Or you can use seperate IP-blocking software like Protowall from [http://bluetack.co.uk Bluetack], PeerGuardian from [http://phoenixlabs.org Phoenixlabs] or [http://moblock.berlios.de moblock].
+
You can insert the lists from these sites either manually or with a script. Or you can use seperate [[IP]]-blocking software like Protowall from [http://bluetack.co.uk Bluetack], PeerGuardian from [http://phoenixlabs.org Phoenixlabs] or [http://moblock.berlios.de moblock].
  
 
The [http://test.blocklist.org lists] from [http://phoenixlabs.org Phoenixlabs] (formerly known as Methlabs) are still under development. They use the lists from [http://bluetack.co.uk Bluetack] instead.
 
The [http://test.blocklist.org lists] from [http://phoenixlabs.org Phoenixlabs] (formerly known as Methlabs) are still under development. They use the lists from [http://bluetack.co.uk Bluetack] instead.
Line 43: Line 43:
 
== Hard coded [[IP]] filter in [[aMule]] ==
 
== 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:
+
[[aMule]] has some ranges of [[IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. These ranges are:
  
 
<pre>
 
<pre>
Line 74: Line 74:
 
</pre>
 
</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").
+
However, you can un-filter these ranges 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").

Revision as of 11:07, 22 January 2007

English | Deutsch

Description

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

This filter is read from ~/.aMule/ipfilter.dat and ~/.aMule/ipfilter_static.dat. The content of these files describes the valid and blocked IP ranges.

ipfilter.dat file

The information and details about the ipfilter.dat file can be found 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.

IP Filter sources

IP Filter - URLs for Auto-update at startup

Insert the URL under "Preferences" -> "Security" -> "IP filtering" -> "URL:"

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

http://www.bluetack.co.uk/config/nipfilter.dat.gz (Bluetack´s normal ipfilter.dat)

http://www.bluetack.co.uk/config/pipfilter.dat.gz (Bluetack´s paranoid ipfilter.dat)

IP Filter sites

You can insert the lists from these sites either manually or with a script. Or you can use seperate IP-blocking software like Protowall from Bluetack, PeerGuardian from Phoenixlabs or moblock.

The lists from Phoenixlabs (formerly known as Methlabs) are still under development. They use the lists from Bluetack instead.

http://bluetack.co.uk/config/sources.txt (If you follow this link then download the lists as *.gz or *.zip instead of *.txt in order to save Bluetack´s bandwith!)

http://emulepawcio.sourceforge.net/nieuwe_site/ipfilter_fake_list.html

http://www.openmedia.info/p27.html (Last update: 6 January 2007)

Hard coded IP filter in aMule

aMule has some ranges of IPs which it filters by default following the RFC 3330 document. These ranges are:

        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]

However, you can un-filter these ranges of IPs 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").