AMule Project FAQ - User contributions [en]

IP Filter-de

2007-01-22T10:15:48Z

Jere: =IP-Filter-Seiten=

<center>[[IP_Filter|English]] | '''Deutsch'''</center>

== Bescheibung ==

Der [[IP]]-Filter blockiert den Datenverkehr unseres [[client-de|Client]]s von/zu [[IP]]s und [[IP]]-Bereichen. Das bedeutet, dass die geblockten [[IP]]s weder zu uns hoch-, noch von uns runterladen können.

Der Filter wird von [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] und ~/.aMule/ipfilter_static.dat gelesen. Der Inhalt dieser Dateien beschreibt, ob [[IP]]-Bereiche gültig sind, oder geblockt werden.

== Die Datei [[ipfilter.dat file|ipfilter.dat]] ==

Informationen und Einzelheiten über die [[ipfilter.dat file|ipfilter.dat]] können [[ipfilter.dat file|hier]] gefunden werden.

== Verwenden des [[IP]]-Filters im [[aMule-de|aMule]] ==

Der ''Zugriffslevel'' des [[IP]]-Filters wird in [[aMule-de|aMule]] bei den "Einstellungen" -> "Sicherheit" -> "IP Filtering" -> "Filter-Level" festgelegt. (Bei [[aMule-de|aMule]]versionen bis 2.0.0-rc8 unter "Server", statt "Sicherheit".)

'''HINWEIS:''' Die ''ipfilter.dat'' von [[aMule-de|aMule]] ist 100% kompatibel mit der von [[eMule]].

== Quellen für den [[IP]]-Filter ==

=== IP-Filter - URLs zum automatischen Aktualisieren beim Start ===

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

http://www.bluetack.co.uk/config/nipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetacks normale ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetacks paranoide ipfilter.dat])

=== IP-Filter-Seiten ===

Die Listen von diesen Seiten können entweder von Hand oder mit einem Skript eingefügt werden. Oder man benutzt gesonderte Software zum Blocken von [[IP]]s wie Protowall von [http://bluetack.co.uk Bluetack], PeerGuardian von [http://phoenixlabs.org Phoenixlabs] oder [http://moblock.berlios.de moblock].

Die [http://test.blocklist.org Listen] von [http://phoenixlabs.org Phoenixlabs] (früher als Methlabs bekannt) werden noch entwickelt. Stattdessen benützen sie die Listen von [http://bluetack.co.uk Bluetack].

http://bluetack.co.uk/config/sources.txt (Wenn du diesem Link folgst, dann lade die Listen als *.gz oder *.zip statt *.txt runter, um Bluetacks Datenverkehr zu schonen!)

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

http://www.openmedia.info/p27.html (Letztes Update: 6. Januar 2007)

== Fest einprogrammierte [[IP]]-Filter im [[aMule-de|aMule]] ==

[[aMule-de|aMule]] filtert standardmäßig entsprechend des [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330]-Dokuments verschiedene [[IP]]-Bereiche. Diese sind:

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

Allerdings kann man die Filterung dieser [http://www.faqs.org/rfcs/rfc791.html IP]-Bereiche unter
"Einstellungen"->"Sicherheit"->"IP-Filter"->"Filtere LAN-IP-Adressen automatisch" auch deaktivieren. (Bei [[aMule-de|aMule]]versionen bis 2.0.0-rc8 unter "Einstellungen"->"Server"->"Filtere LAN-IP-Adressen automatisch").

IP Filter-de

2007-01-22T10:13:11Z

Jere: updated translation

<center>[[IP_Filter|English]] | '''Deutsch'''</center>

== Bescheibung ==

Der [[IP]]-Filter blockiert den Datenverkehr unseres [[client-de|Client]]s von/zu [[IP]]s und [[IP]]-Bereichen. Das bedeutet, dass die geblockten [[IP]]s weder zu uns hoch-, noch von uns runterladen können.

Der Filter wird von [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] und ~/.aMule/ipfilter_static.dat gelesen. Der Inhalt dieser Dateien beschreibt, ob [[IP]]-Bereiche gültig sind, oder geblockt werden.

== Die Datei [[ipfilter.dat file|ipfilter.dat]] ==

Informationen und Einzelheiten über die [[ipfilter.dat file|ipfilter.dat]] können [[ipfilter.dat file|hier]] gefunden werden.

== Verwenden des [[IP]]-Filters im [[aMule-de|aMule]] ==

Der ''Zugriffslevel'' des [[IP]]-Filters wird in [[aMule-de|aMule]] bei den "Einstellungen" -> "Sicherheit" -> "IP Filtering" -> "Filter-Level" festgelegt. (Bei [[aMule-de|aMule]]versionen bis 2.0.0-rc8 unter "Server", statt "Sicherheit".)

'''HINWEIS:''' Die ''ipfilter.dat'' von [[aMule-de|aMule]] ist 100% kompatibel mit der von [[eMule]].

== Quellen für den [[IP]]-Filter ==

=== IP-Filter - URLs zum automatischen Aktualisieren beim Start ===

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

http://www.bluetack.co.uk/config/nipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetacks normale ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetacks paranoide ipfilter.dat])

=== IP-Filter-Seiten ===

Die Listen von diesen Seiten können entweder von Hand oder mit einem Skript eingefügt werden. Oder man benutzt gesonderte Software zum Blocken von [[IP]]s wie Protowall von [http://bluetack.co.uk Bluetack], PeerGuardian von [http://phoenixlabs.org Phoenixlabs] oder [http://moblock.berlios.de moblock].

Die [http://test.blocklist.org Listen] von [http://phoenixlabs.org Phoenixlabs] (früher als Methlabs bekannt) werden noch entwickelt. Stattdessen benützen sie noch die Listen von [http://bluetack.co.uk Bluetack].

http://bluetack.co.uk/config/sources.txt (Wenn du diesem Link folgst, dann lade die Listen als *.gz oder *.zip statt *.txt runter, um Bluetacks Datenverkehr zu schonen!)

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

http://www.openmedia.info/p27.html (Letztes Update: 6. Januar 2007)

== Fest einprogrammierte [[IP]]-Filter im [[aMule-de|aMule]] ==

[[aMule-de|aMule]] filtert standardmäßig entsprechend des [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330]-Dokuments verschiedene [[IP]]-Bereiche. Diese sind:

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

Allerdings kann man die Filterung dieser [http://www.faqs.org/rfcs/rfc791.html IP]-Bereiche unter
"Einstellungen"->"Sicherheit"->"IP-Filter"->"Filtere LAN-IP-Adressen automatisch" auch deaktivieren. (Bei [[aMule-de|aMule]]versionen bis 2.0.0-rc8 unter "Einstellungen"->"Server"->"Filtere LAN-IP-Adressen automatisch").

IPFilter

2007-01-22T10:07:39Z

Jere:

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

== 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'']] 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 [[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.

== [[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 ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack´s normal ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ 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 [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.

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 [[IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. These 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 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").

IPFilter

2007-01-22T01:04:58Z

Jere: removed invalid link

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

== 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'']] 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 [[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.

== [[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 ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack´s normal ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ 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 [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.

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

Fake

2007-01-22T00:59:40Z

Jere: typo

<center>'''English''' | [[Fake-de|German]]</center>

Fake files are those which are intended to look like a file, but are in fact something else or just nothing at all.

Sadly, fakes are hard to detect and the [[FAQ_ed2k|ed2k]] network provides little (in some aspects it is even correct to say ''none'') protection against fakes.

Anyway, [[aMule]] provides two ways to detect these fake files:
#By taking a look at the [[comment]]s submitted by other [[client]]s.
#By using one of the following resources (right-click on the download -> FakeCheck):
*http://donkeyfakes.gambri.net (closed October 2005)
*http://www.jugle.net

As a tip, it is commonly useful to take a look at the download's details (right-click on the download -> Show file details) and see if someone has set some filename which refers to some different content. If such is the case, you might suspect if the real content is what you assume it is, what that other [[client]] has set as it's filename or none of those.

Tip 2, you can check the history of a file on *http://stats.razorback2.com/ed2khistory to see if the file release date is feasible or if file names are correct or consistent.

Do not confuse ''fake'' with ''[[corrupt]]''.

IPFilter

2007-01-22T00:30:45Z

Jere: also reference ~/.aMule/ipfilter_static.dat

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

== 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'']] 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 [[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.

== [[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.autistici.org/smokingmath/ipfilter.dat (Only filters [[fake]] [[server]]s. Last update: 8 August 2005)

http://www.bluetack.co.uk/config/nipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack´s normal ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ 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 [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.

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

IPFilter

2007-01-22T00:20:20Z

Jere: added explanation and added paranoid list and link to bluetack´s list FAQ

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

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

== [[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.autistici.org/smokingmath/ipfilter.dat (Only filters [[fake]] [[server]]s. Last update: 8 August 2005)

http://www.bluetack.co.uk/config/nipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack´s normal ipfilter.dat])

http://www.bluetack.co.uk/config/pipfilter.dat.gz ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ 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 [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.

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

IPFilter

2007-01-22T00:09:27Z

Jere: Updated and rewrote section. I hope I don´t advertize the other IP-blocking software too much.

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

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

== [[IP]] Filter sources ==

=== IP Filter - URLs for Auto-update at startup ===

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

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

http://www.bluetack.co.uk/config/nipfilter.dat.gz

=== 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].

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.

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

Usage Statusbar

2006-03-12T14:12:06Z

Jere: typo

[[Usage aMule|Back to Index]]

== Description ==

The status bar allows to easily view general useful information about the current aMule session.

It is placed at the bottom of the main window and looks like this:

http://www.amule.org/dev-up/window_statusbar1.jpg

== Usage ==

The status bar is divided into several sections:

=== Log ===

You can see the last line printed into the log at the left most part of the statusbar:

http://www.amule.org/dev-up/window_statusbar2.jpg

The line might be only partially shown if it is larger than the space left in the statusbar. In this case it comes very useful to click in the information button by the text.

http://www.amule.org/dev-up/window_statusbar3.jpg

When clicked, a window will popup displaying the complete line.

http://www.amule.org/dev-up/window_statusbar13.jpg

=== Users ===

aMule tries to calculate the amount of users currently connected to the networks it is connected to.

The first number in the '''Users''' field corresponds to the estimated amount of users currently connected to the ed2k network.

http://www.amule.org/dev-up/window_statusbar4.jpg

The second number in that field corresponds to the estimated amount of users connected to the Kademlia network.

http://www.amule.org/dev-up/window_statusbar5.jpg

In both ed2k and Kad numbers the following letters are used to specify the multiplying factor:
{|
| '''''Letter''''' || '''Multiplying factor'''
|-
| ''k'' || 1000
|-
| ''M'' || 1000x1000
|-
| ''G'' || 1000x1000x1000
|-
| ''T'' || 1000x1000x1000x1000
|}

=== Files ===

aMule also tries to calculate the amount of currently available files on the networks it is connected to.

Again, the first number in the '''Files''' field corresponds to the estimated amount of files currently available in the ed2k network.

http://www.amule.org/dev-up/window_statusbar6.jpg

And again, the second number in this field corresponds to the estimated amount of files currently available in the Kademlia network.

http://www.amule.org/dev-up/window_statusbar7.jpg

As with the [[Usage_Statusbar#Users||Users]] field, the last letter indicates the multiplying factor (see above which letter corresponds to which multiplying factor).

=== Speed ===

The statusbar provides a handy way to know the bandwidth aMule is effectively taking.

First it has a graphic which displays two arrows surrounding a globe provides a brief summary of the connection status. The downwards arrow will be green when aMule is downloading and red when it isn't. The upwards arrow will be green when aMule is uploading and red when it isn't.

http://www.amule.org/dev-up/window_statusbar33.jpg

This are the possible graphics:
{|
| '''Graphic''' || '''''Description'''''
|-
| http://www.amule.org/dev-up/window_statusbar29.jpg || ''aMule isn't downloading nor uploading''
|-
| http://www.amule.org/dev-up/window_statusbar30.jpg || ''aMule is downloading but isn't uploading''
|-
| http://www.amule.org/dev-up/window_statusbar31.jpg || ''aMule isn't downloading but is uploading''
|-
| http://www.amule.org/dev-up/window_statusbar32.jpg || ''aMule both downloading and uploading''
|}

Right by the connections status icon the upload and download speeds are displayed.

In the '''Up''' field you can see the upload speed it is performing.

http://www.amule.org/dev-up/window_statusbar8.jpg

In the '''Down''' field you can see at what speed aMule is downloading.

http://www.amule.org/dev-up/window_statusbar9.jpg

If you have enabled "Show overhead bandwidth" in Preferences, then a number in brackets will appear both by the upload and download speed numbers. This numbers show the bandwidth that the overhead traffic (connections, pings, control traffic, ...) are taking for the uploads and downloads respectively.

http://www.amule.org/dev-up/window_statusbar28.jpg

=== Networks ===

The last field shows information about the networks status.

If you are connected to the ed2k network, you will be able to see the name (or IP if it has no known name) of the ed2k server you are connected to.

http://www.amule.org/dev-up/window_statusbar11.jpg

If you are not connected to the ed2k network, they you will see '''Not connected''' or '''Connecting''' if you are trying to connect.

Now about the Kademlia network, you should see its status by the '''Kad''' text.

http://www.amule.org/dev-up/window_statusbar12.jpg

Possible values are:
{|
| '''Text''' || '''''Meaning'''''
|-
| ''ok'' || Connected
|-
|''firewalled'' || Firewalled
|-
| ''off'' || Not connected, offline
|}

A very special icon in the statusbar is the earth icon:

http://www.amule.org/dev-up/window_statusbar10.jpg

The arrows in this globe change their colour depending on the connection status of aMule.

The lower-left arrow refers to the ed2k network:

http://www.amule.org/dev-up/window_statusbar23.jpg

The upper-right arrow refers to the Kademlia network:

http://www.amule.org/dev-up/window_statusbar24.jpg

This are the coulour's meanings:
{|
| '''Colour''' || '''''Meaning'''''
|-
| Red || ''Offline, not connected''
|-
| Orange || ''Connecting''
|-
| Yellow || ''Connected but firewalled''
|-
| Green || ''Connected''
|}

Here is the list of all possible globe icons and their meanings:

{|
| http://www.amule.org/dev-up/window_statusbar16.jpg || Both ed2k and kademlia networks are offline
|-
| http://www.amule.org/dev-up/window_statusbar17.jpg || The ed2k network is offline, but Kad is connected though firewalled
|-
| http://www.amule.org/dev-up/window_statusbar15.jpg || The ed2k network is offline, but Kad is connected
|-
| http://www.amule.org/dev-up/window_statusbar19.jpg || The ed2k network is being connected, while the kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar18.jpg || The ed2k network is being connected, while the Kad network is connected though firewalled
|-
| http://www.amule.org/dev-up/window_statusbar14.jpg || The ed2k network is being connected, while the Kad network is connected
|-
| http://www.amule.org/dev-up/window_statusbar26.jpg || The ed2k network is connected with LowID (firewalled), while the Kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar25.jpg || Both the ed2k and Kad networks are connected but firewalled
|-
| http://www.amule.org/dev-up/window_statusbar21.jpg || The ed2k network is connected, while the Kad network is offline
|-
| http://www.amule.org/dev-up/window_statusbar20.jpg || Both the ed2k and Kad networks are connected, but the Kad network is firewalled
|-
| http://www.amule.org/dev-up/window_statusbar22.jpg || Both the ed2k and Kad networks are connected
|}

'''Note:''' It should never happen that ed2k arrow iw yellow and the Kad arrow is green, so it is not listed int he above table.

== Overview ==

http://www.amule.org/dev-up/window_statusbar27.jpg

{|
|+ Quick Reference
| '''Number''' || '''''Description'''''
|-
| 1 || ''Popup complete last log line''
|-
| 2 || ''Last log line (just what fits in window)''
|-
| 3 || ''Estimated online ed2k users''
|-
| 4 || ''Estimated online Kadmelia users''
|-
| 5 || ''Estimated available ed2k files''
|-
| 6 || ''Estimated available Kademlia files''
|-
| 7 || ''Uploading speed''
|-
| 8 || ''Uploading overhead speed''
|-
| 9 || ''Downloading speed''
|-
| 10 || ''Downloading overhead speed''
|-
| 11 || ''ED2k and Kademlia status graphical summary''
|-
| 12 || ''ED2k connected server name or ed2k status''
|-
| 13 || ''Kademlia status''
|-
| 14 || ''Connection status graphical summary''
|}

<center>[[Usage aMule|Back to Index]]</center>

IPFilter

2005-09-29T09:41:43Z

Jere: End of hijacking

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

== [[IP]] Filter sources ==

=== IP Filter - URLs for Auto-update at startup ===

http://emulepawcio.sourceforge.net/nieuwe_site/Ipfilter_fakes/ipfilter.dat (Last update: 28 August 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.bluetack.co.uk/config/ipfilter.dat

=== IP Filter sites - Insert these lists manually or with a script===

<font color="red">'''methlabs.org and blocklist.org were hijacked until September 27th, 2005. Now they belong to the original developers again, they can be found [http://phoenixlabs.org here]. The blocklists are not online yet again, use those from bluetack</font>

http://bluetack.co.uk/config/sources.txt (Replacement for ''methlabs.org'' and ''blocklist.org'')

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

http://www.openmedia.info/p27.html (Last update: 12 September 2005)

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