aMule Forum
English => en_Bugs => Topic started by: ryoohki on November 15, 2008, 05:40:55 AM
-
when i set UDP port of extended server and restart amule ,the amule will set UDP port of extended server automatically and that port is not TCP port +3
-
when i set UDP port of extended server [...]
How did you do that? aMule doesn't provide any means to set that port manually, because it is by definition TCP+3
-
If he uses a selfcompiled aMule, He just could change the sources to get another port.
-
If he uses a selfcompiled aMule, He just could change the sources to get another port.
... which wouldn't work until he uses a self-compiled server with the same modifications.
-
at begin my definition TCP is 5142 and UDP is 5152 , and amule told me "UDP port for extended server requests (TCP+3):5142" ,when i change UDP to 5142 and restart amule ,the amule has changed UDP to other one ,is not amule told that 5142
-
There are TWO UDP ports aMule uses:
- one is for extended server requests, and is by definition TCP+3. So if you had set your TCP port to 5142, this UDP port will be 5145.
- And one is for extended client protocol, which you can set freely to any number except the one above.