Difference between revisions of "IPFilter"

Revision as of 07:32, 12 November 2004

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 which is a file which's contents describes the valid and blocked IP ranges.

ipfilter.dat format

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

IPs range , Access level , Description

Access level values lower than 127 are blocked IPs and values over 127 are permitted IPs.

IPs range values are described by an initial IP a slash and the ending IP of tha range (the slash must be separated from the IPs by a single space character).

Using the IP Filter in aMule

The Access level of the IP filter is selected in aMule through Preferences -> Security -> IP Filtering -> Filtering level.

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).

IP Filter sources

http://ciberia.ya.com/Mc4TuTi/ipfilter.dat
http://ciberia.ya.com/Mc4TuTi/2/ipfilter.dat

Hard coded IP filter in aMule

aMule has a range of IPs which it filters by default following the RFC 3330 document. This 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 this range of IPs by unchecking "Preferences"->"Security"->"IP-filtering"->"Always filter bad IPs" (on aMule versions previous to 2.0.0-rc8, this option can be found in "Preferences"->"Server"->"Always filter bad IPs").