aMule Bug Tracker - aMule
View Issue Details
0001352aMuleFeature Requestpublic2008-07-03 19:122008-08-30 11:59
Kremmen 
 
normalminoralways
closedopen 
2.1.3 
 
Any
0001352: Port setup should be easier
eMule only requires 1 TCP and 1 UDP port, except in unusual circumstances. (See http://www.emule-project.net/home/perl/help.cgi?l=1&topic_id=122&rm=show_topic: [^] "In very rare cases there might be another port to open: If your router / firewall does not supports stateful UDP connections (which means that it will accept answers to UDP packets you send), you will have to open a port for the UDP answer packets from servers. This is not needed in most cases because nearly all routers and firewall do support UDP answerpackets ...")

aMule should likewise not require the extra port. Worse, it's really messily implemented and just likely to break various users' setups. eg. Let's say your firewall is set up to provide a set of ports 5000-5010 (TCP) and 6000-6010 (UDP) to one PC on your internet network, 5011-5020/6011-6020 to the next PC, and so on. The requirement for an extra UPD port and that it be related (N+3) to the existing TCP port means having to totally reconfigure your whole network firewall. All for a port which shouldn't be needed at all in most cases. At the very least, its number should be individually configured if necessary. A better default would be an offset from the existing UDP port.
eMule docs say that in that package, the extra port can be explicitly configured with "ServerUDPPort=[YourPort]". I haven't found any docs here at all to say whether that directive (or any equivalent) is understood by aMule.
No tags attached.
Issue History
2008-07-03 19:12KremmenNew Issue
2008-07-03 19:12KremmenOperating System => Any
2008-08-30 11:59WuischkeStatusnew => closed
2008-08-30 11:59WuischkeNote Added: 0002932

Notes
(0002932)
Wuischke   
2008-08-30 11:59   
The port number is fixed (always TCP + 3) and there are currently no plans to change this.