Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mandrake]

First of all: AMULE is a GEM !

Now a couple of questions.

1) What is UDP port+3 used for I currently have that filtered and AMULE looks in perfect shape (connects happily with an high ID) ?

2) What can I use as an URL to auto update the ipfilter.dat list ? And related to this how can I be absolutely sure that I have the banned IPs loaded ? Looked for a number in the statistic and everywhere else but could not find it. Also, once loaded do the ipfilter.dat data loaded every time I start amule This is very important since in my country some idiotic law is enabling police to seize all of your equipment just because you are sharing something with P2P protocols (and after MANY years if you did not do anything illegal they will return your hardware wich will be totally obsolete)  X( X( X(

Thank you,
Sammy

[Supersnail]

1) The ports used be eMule (and aMule) can be found at http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=122
UDP +3 seems to be this one:

6)     Local Port:     any
     Remote Port:    4665
     Protocol:    UDP
     Direction:    outgoing
     Purpose:    Source asking on servers
     Note:    

Servers using the default port 4661 TCP (see #5) automatically set their port for source asking to 4665 UDP. If a server uses a different port in #5 the corresponding UDP port is set to [Connection Port + 4]. For firewalls the remote port here is any.

2) I always download my ipfilter.dat from http://www2.openmedia.info:8080/p27.html . They updated it regularly (about once a week), but the server is pretty slow and you first have to unzip the file. So, I don't use the auto-update feature.
The ipfilter is loaded everytime aMule starts. It can be found on the 'aMule log' tab in the 'Servers' tab.

Loaded ipfilter with 41461 new IP addresses.

[Kry]

Don't get confused: TCP+3 is the UDP socket on aMule, TCP+4 is on the server. So communication is from aMule's TCP+3  to server's TCP+4

[mandrake]

Thank you !

so given that my firewall grants any outbound connection, for the incoming connections I just have to open the TCP and UDP ports which I explicitely declare in aMule config (in my case 63572 for both).

Correct ?

Take care,
Sammy

[Kry]

no, you need to open TCP+3 also (UDP)

[mandrake]

Please be patient sinc eEnglish is anhostile language for me

In your earlier append you said the communication goes from amule+3 to server+4.

This would be already granted since I permit any OUTBOUND packet to happen and any related response (for TCP).

I should build a rule to accept new packets on port+3 only if they are new packets coming from the server with source whatever and dest my machine amule-port+3.

Is this what you mean ?

I am asking since amule seems working very well without this port open.

Take care and happy new year.