http://wiki.amule.org/t/api.php?action=feedcontributions&user=Endolith&feedformat=atomAMule Project FAQ - User contributions [en]2024-03-28T18:03:48ZUser contributionsMediaWiki 1.23.3http://wiki.amule.org/t/index.php?title=IPFilterIPFilter2009-08-01T13:19:21Z<p>Endolith: Undo revision 27221 by Sturedman (Talk)</p>
<hr />
<div><center>'''English''' | [[IP_Filter-de|Deutsch]]</center><br />
<br />
== Description ==<br />
The [[IP address|IP]] Filter blocks traffic from/to IPs and ranges of [[IP address|IP]]s with our [[client]]. This means that those [[IP address|IP]]s which get blocked will not be able neither to upload to us nor to download from us.<br />
<br />
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 address|IP]] ranges.<br />
<br />
== [[ipfilter.dat file]] ==<br />
The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].<br />
<br />
== Using the [[IP address|IP]] Filter in [[aMule]] ==<br />
The ''Access level'' of the [[IP address|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").<br />
<br />
'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s.<br />
<br />
== Using an external [[ipfilter.dat file]] ==<br />
<br />
aMule by default uses ~/.aMule/ipfilter.dat for IP filtering. If you enable 'Use system-wide ipfilter.dat if available', it will look for a /usr/share/amule/ipfilter.dat file if loading the local ipfilter.dat fails. This system-wide ipfilter.dat can then be kept up-to-date by another method <!-- such as.... --> so that aMule doesn't have to download a large file every time it starts.<br />
<br />
The above paths assume a linux-like system.<br />
<br />
This option is located through "Preferences" -> "Security" and is disabled by default in the latest stable 2.2.2 build.<br />
<br />
== [[IP address|IP]] Filter sources ==<br />
=== IP Filter - URLs for Auto-update at startup ===<br />
Insert the URL under "Preferences" -> "Security" -> "IP filtering" -> "URL:"<br />
<br />
http://emulepawcio.sourceforge.net/ipfilter.dat (updated monthly) Unfortunately the header lines of this .dat file confuse aMule 2.2.3 (the newest aMule as I write this) so the header lines (starting with #) need to be removed before aMule will successfully load this file. To accomplish this let aMule download the file as normal, check the aMule log to see where aMule stored the file (it seems to stored it in ~/Library/Application Support/aMule/ipfilter.dat on a Mac), then open this file with a text editor and remove all the header lines starting with #'s, then press the 'Reload List' button in the aMule Security Preferences to get aMule to reload the file.<br />
<br />
http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's normal ipfilter.dat])<br />
<br />
http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's paranoid ipfilter.dat])<br />
<br />
=== IP Filter sites ===<br />
You can insert the lists from these sites either manually or with a script. Or you can use seperate [[IP address|IP]]-blocking software like Protowall from [http://bluetack.co.uk Bluetack], PeerGuardian from [http://phoenixlabs.org Phoenixlabs] or [http://moblock.berlios.de moblock].<br />
<br />
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.<br />
<br />
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!)<br />
<br />
http://emulepawcio.sourceforge.net/nieuwe_site/ipfilter_fake_list.html<br />
<br />
== Hard coded [[IP address|IP]] filter in [[aMule]] ==<br />
[[aMule]] has some ranges of [[IP address|IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. These ranges are:<br />
<br />
Address Block Present Use Reference<br />
----------------------------------------------------------------------<br />
"0.0.0.0/8", // "This" Network [RFC1700, page 4]<br />
"10.0.0.0/8", // Private-Use Networks [RFC1918]<br />
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]<br />
"24.0.0.0/8", // Cable Television Networks --<br />
"39.0.0.0/8", // Reserved but subject<br />
// to allocation [RFC1797]<br />
"127.0.0.0/8", // Loopback [RFC1700, page 5]<br />
"128.0.0.0/16", // Reserved but subject<br />
// to allocation --<br />
"169.254.0.0/16", // Link Local --<br />
"172.16.0.0/12", // Private-Use Networks [RFC1918]<br />
"191.255.0.0/16", // Reserved but subject<br />
// to allocation --<br />
"192.0.0.0/24", // Reserved but subject<br />
// to allocation --<br />
"192.0.2.0/24", // Test-Net<br />
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]<br />
"192.168.0.0/16", // Private-Use Networks [RFC1918]<br />
"198.18.0.0/15", // Network Interconnect<br />
// Device Benchmark Testing [RFC2544]<br />
"223.255.255.0/24",// Reserved but subject<br />
// to allocation --<br />
"224.0.0.0/4", // Multicast [RFC3171]<br />
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]<br />
<br />
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").</div>Endolithhttp://wiki.amule.org/t/index.php?title=User_talk:EndolithUser talk:Endolith2009-08-01T13:14:16Z<p>Endolith: </p>
<hr />
<div>Please ask questions in the forum, not in the wiki.<br />
<br />
[[User:Sturedman|Sturedman]] 12:57, 1 August 2009 (UTC)<br />
<br />
It's better to ask the question on the wiki where people reading about the topic will see it and then improve the wiki by answering it. [[User:Endolith|Endolith]] 13:14, 1 August 2009 (UTC)</div>Endolithhttp://wiki.amule.org/t/index.php?title=IPFilterIPFilter2009-08-01T02:22:39Z<p>Endolith: /* Using an external ipfilter.dat file */</p>
<hr />
<div><center>'''English''' | [[IP_Filter-de|Deutsch]]</center><br />
<br />
== Description ==<br />
The [[IP address|IP]] Filter blocks traffic from/to IPs and ranges of [[IP address|IP]]s with our [[client]]. This means that those [[IP address|IP]]s which get blocked will not be able neither to upload to us nor to download from us.<br />
<br />
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 address|IP]] ranges.<br />
<br />
== [[ipfilter.dat file]] ==<br />
The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].<br />
<br />
== Using the [[IP address|IP]] Filter in [[aMule]] ==<br />
The ''Access level'' of the [[IP address|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").<br />
<br />
'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s.<br />
<br />
== Using an external [[ipfilter.dat file]] ==<br />
<br />
aMule by default uses ~/.aMule/ipfilter.dat for IP filtering. If you enable 'Use system-wide ipfilter.dat if available', it will look for a /usr/share/amule/ipfilter.dat file if loading the local ipfilter.dat fails. (''Is there a script or package/repository to keep this updated so that aMule doesn't have to download a huge file every time it starts?'')<br />
<br />
The above paths assume a linux-like system.<br />
<br />
This option is located through "Preferences" -> "Security" and is disabled by default in the latest stable 2.2.2 build.<br />
<br />
== [[IP address|IP]] Filter sources ==<br />
=== IP Filter - URLs for Auto-update at startup ===<br />
Insert the URL under "Preferences" -> "Security" -> "IP filtering" -> "URL:"<br />
<br />
http://emulepawcio.sourceforge.net/ipfilter.dat (updated monthly) Unfortunately the header lines of this .dat file confuse aMule 2.2.3 (the newest aMule as I write this) so the header lines (starting with #) need to be removed before aMule will successfully load this file. To accomplish this let aMule download the file as normal, check the aMule log to see where aMule stored the file (it seems to stored it in ~/Library/Application Support/aMule/ipfilter.dat on a Mac), then open this file with a text editor and remove all the header lines starting with #'s, then press the 'Reload List' button in the aMule Security Preferences to get aMule to reload the file.<br />
<br />
http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's normal ipfilter.dat])<br />
<br />
http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's paranoid ipfilter.dat])<br />
<br />
=== IP Filter sites ===<br />
You can insert the lists from these sites either manually or with a script. Or you can use seperate [[IP address|IP]]-blocking software like Protowall from [http://bluetack.co.uk Bluetack], PeerGuardian from [http://phoenixlabs.org Phoenixlabs] or [http://moblock.berlios.de moblock].<br />
<br />
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.<br />
<br />
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!)<br />
<br />
http://emulepawcio.sourceforge.net/nieuwe_site/ipfilter_fake_list.html<br />
<br />
== Hard coded [[IP address|IP]] filter in [[aMule]] ==<br />
[[aMule]] has some ranges of [[IP address|IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. These ranges are:<br />
<br />
Address Block Present Use Reference<br />
----------------------------------------------------------------------<br />
"0.0.0.0/8", // "This" Network [RFC1700, page 4]<br />
"10.0.0.0/8", // Private-Use Networks [RFC1918]<br />
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]<br />
"24.0.0.0/8", // Cable Television Networks --<br />
"39.0.0.0/8", // Reserved but subject<br />
// to allocation [RFC1797]<br />
"127.0.0.0/8", // Loopback [RFC1700, page 5]<br />
"128.0.0.0/16", // Reserved but subject<br />
// to allocation --<br />
"169.254.0.0/16", // Link Local --<br />
"172.16.0.0/12", // Private-Use Networks [RFC1918]<br />
"191.255.0.0/16", // Reserved but subject<br />
// to allocation --<br />
"192.0.0.0/24", // Reserved but subject<br />
// to allocation --<br />
"192.0.2.0/24", // Test-Net<br />
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]<br />
"192.168.0.0/16", // Private-Use Networks [RFC1918]<br />
"198.18.0.0/15", // Network Interconnect<br />
// Device Benchmark Testing [RFC2544]<br />
"223.255.255.0/24",// Reserved but subject<br />
// to allocation --<br />
"224.0.0.0/4", // Multicast [RFC3171]<br />
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]<br />
<br />
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").</div>Endolithhttp://wiki.amule.org/t/index.php?title=AMuleWebAMuleWeb2009-07-31T23:49:58Z<p>Endolith: /* aMuled and aMuleWeb as services */</p>
<hr />
<div><center>'''English''' | [[AMuleWeb-de|Deutsch]] | [[AMuleWeb-it|Italiano]] </center><br />
<br />
'''aMuleWeb''' is a utility that allows you to control aMule by means of a web browser from any location. The web interface offers a subset of aMule functionality, including searching for files, initializing downloads, and viewing your download queue. It also displays status information and allows you to change certain options.<br />
<br />
aMule itself doesn't support [http://www.w3.org/MarkUp HTTP] connections; aMuleWeb, which does, therefore serves as an intermediary between aMule and a web browser. Once the link between aMuleWeb and a remote user is established, it connects to aMule via the [[External Connections]] interface.<br />
<br />
By default, aMuleWeb listens for HTTP connections at port 4711, but this can be changed in [[Usage Preferences|Preferences]]'.<br />
<br />
== Set a password ==<br />
<br />
To connect to the web server a password must be set, otherwise connection is refused. To set a password run aMuleWeb with --admin-pass=your_password.<br />
<br />
== Standard ports ==<br />
<br />
The ports can be set to anything, but by default aMule uses:<br />
<br />
*External Connections: 4712<br />
*amuleweb: 4711<br />
<br />
Make sure you do not confuse the two; in the default configuration, it looks like this: <br />
<br />
aMule --&gt; <nowiki>[</nowiki>4712<nowiki>]</nowiki> --&gt; aMuleWeb --&gt; <nowiki>[</nowiki>4711<nowiki>]</nowiki> --&gt; web browser<br />
<br />
== Template (skin) location ==<br />
<br />
aMuleWeb looks for its files in a number of places:<br />
<br />
*In your home directory: ''$HOME/.aMule/webserver/''<nowiki>[</nowiki>skin name<nowiki>]</nowiki>''/''<br />
<br />
*And at its install location, in this order (by default, ''/usr/local/share/amule/webserver'' if you compiled aMule, or ''/usr/share/amule/webserver'' if you installed it from a package).<br />
<br />
Default template name is 'default'.<br />
<br />
If, ''after installing'' aMule, aMuleWeb refuses to run because of not being able to load template:<br />
<br />
*Please report this situation to us, and then<br />
<br />
*Create the directories ''webserver/default'' in the ''.aMule'' subdirectory of your home directory, and copy the contents of the ''src/webserver'' directory there from the aMule tarball (ie, ''$HOME/.aMule/webserver/default'').<br />
<br />
== aMuled and aMuleWeb as services ==<br />
<br />
Although starting aMuleWeb by enabling it in aMule's preferences is the preferred method, you can also run aMuleWeb together with aMuled as as services by means of an init.d script. Here is an example:<br />
<br />
''/etc/init.d/amule''<br />
<br />
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin<br />
DAEMON=/usr/bin/amuled<br />
WEB=/usr/bin/amuleweb<br />
NAME=amuled<br />
DESC=amuled<br />
RUNAMULE=no<br />
USER=youramuleuser<br />
<br />
test -x $DAEMON || exit 0<br />
<br />
# Include amule defaults if available<br />
if <nowiki>[</nowiki> -f /etc/default/amule <nowiki>]</nowiki> ; then<br />
. /etc/default/amule<br />
fi<br />
<br />
if <nowiki>[</nowiki> "$RUNAMULE" != "yes" <nowiki>]</nowiki> ; then<br />
echo "Amule not to be started. Edit /etc/default/amule first."<br />
exit 1<br />
fi<br />
<br />
set -e<br />
<br />
case "$1" in<br />
start)<br />
echo -n "Starting $DESC: "<br />
su $USER -c "$DAEMON -f"<br />
while ! netstat -l -n -p -t | grep -q amuled ; do sleep 1 ; done<br />
su $USER -c "$WEB --quiet &amp;"<br />
echo "$NAME."<br />
;;<br />
stop)<br />
echo -n "Stopping $DESC: "<br />
killall --quiet --ignore-case $WEB<br />
killall --quiet --ignore-case $DAEMON<br />
echo "$NAME."<br />
;;<br />
restart|force-reload)<br />
echo -n "Restarting $DESC: "<br />
killall --quiet --ignore-case $WEB<br />
killall --quiet --ignore-case $DAEMON<br />
sleep 1<br />
su $USER -c "$DAEMON -f"<br />
while ! netstat -l -n -p -t | grep -q amuled ; do sleep 1 ; done<br />
su $USER -c "$WEB --quiet &amp;"<br />
echo "$NAME."<br />
;;<br />
*)<br />
N=/etc/init.d/$NAME<br />
echo "Usage: $N {start|stop|restart|force-reload}" &gt;&2<br />
exit 1<br />
;;<br />
esac<br />
<br />
exit 0<br />
<br />
<br />
<br />
Then just set that script to be run at start up. On [[Debian]] this would be done with the following command:<br />
<br />
update-rc.d amule defaults<br />
<br />
Then, for the daemons to start you just have to create a file ''/etc/default/amule'' which contains a single line:<br />
<br />
RUNAMULE=yes<br />
<br />
<br />
=== Ubuntu ===<br />
<br />
Ubuntu has a script in /etc/init.d already called amule-daemon<br />
<br />
You need to set the user by editing /etc/default/amule-daemon, and amuled will be started as that user.<br />
<br />
== Where to report problems and questions? ==<br />
<br />
For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]<br />
<br />
== Other sources of information ==<br />
<br />
Read the aMuleWeb man page, which is available in English, French, German, Hungarian and Spanish.<br />
<br />
For further information read the [[FAQ_webserver|aMuleWeb FAQ]].</div>Endolith