aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Portage Problems are more than a heavy canoe....  (Read 2543 times)

Irritable_Chihuahua

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Portage Problems are more than a heavy canoe....
« on: July 16, 2007, 05:55:20 AM »

From the aMule Log:
Network configuration failed! You can't use the port which has the value of the main TCP port plus 3 for the UDP port.
This port has been reserved for the Server-UDP port. The port value has been changed to avoid conflict, see the preferences for the new value

External connections disabled in config file
MuleUDPSocket: Created Server UDP-Socket at port 4665
MuleUDPSocket: Created Client UDP-Socket at port 31566
Found 2 known shared files
AICH Thread: Syncronization thread started.
AICH Thread: Masterhashes of known files have been loaded.
AICH Thread: No new files found.
AICH Thread: Terminated.
Connecting
The URL to download can't be empty
No valid servers found in server list
Read 0 Kad contacts
webserver running on pid 411
Failed to download the server list from


What seems to be the problem?
-- I have to manually choose a server to connect - the 'connect' button in the corner doesn't work by itself, and it won't connect on startup.
-- I'm stuck with a Low-ID (no surprise there)
-- Downloads are 4x slower than uploads

What I've done:
I went into my sever web site and adjusted my port forwarding enabled TCP and UDP for ports 4662 thru 4665.  A lot of good that does if it keeps changing my UDP to big numbers (31000 range).  (the TCP testing link still shows blockage - do I have to log out and in again?)

Now the questions:
Is that why Kad never seems to connect properly?
Is this why my downloads are 4x slower than the uploads?
I'm still using auto-DHCP to configure my IPv4 address - should I go to a fixed DHCP address, or is there something about IPv6 that may be better?  I have my external IP address, my Gateway address, and damn near every other address needed to make this computer fly - I just don't know what to do next.
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Portage Problems are more than a heavy canoe....
« Reply #1 on: July 16, 2007, 08:28:29 AM »

Hi Irritable_Chihuahua,

Quote
A lot of good that does if it keeps changing my UDP to big numbers (31000 range).

Read the first sentence of your aMule log. Please, read it and tell me if it is any hard to understand. I already changed the message once, because users didn't seem to understand, have you any idea how to improve the wording?
Quote
Network configuration failed! You can't use the port which has the value of the main TCP port plus 3 for the UDP port.
This port has been reserved for the Server-UDP port. The port value has been changed to avoid conflict, see the preferences for the new value

You mustn't use IPv6 (ed2k doesn't work with IPv6) and you need a fixed IP(v4) address in order to forward the necessary ports successfully.

About the server: The log states that you have no servers in your list, is this correct?
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Portage Problems are more than a heavy canoe....
« Reply #2 on: July 16, 2007, 08:30:40 AM »

You need to forward these ports:
- TCP port
- TCP + 3 port
- UDP port
- aMuleweb port (if you use it)

After changing ports in aMule, you should restart it. And it's normal that at the beginning downloads are slow. With time and many sources, they start gaining speed.

Regards.
Logged

Irritable_Chihuahua

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: Portage Problems are more than a heavy canoe....
« Reply #3 on: July 16, 2007, 05:17:58 PM »

Read the first sentence of your aMule log. Please, read it and tell me if it is any hard to understand. I already changed the message once, because users didn't seem to understand, have you any idea how to improve the wording?

I think it may be hard to understand that the SERVER UDP port and YOUR own UDP port are the same thing, or different?  I've got a publishing degree and believe me, there is NOTHING out there that can be "Idiot-Proofed"

Should I just set UDP port forwarding for huge numbers (31000 to 35000), or set is low, like 4666?

You need to forward these ports: - TCP port - TCP + 3 port - UDP port - aMuleweb port (if you use it)
My ISP does not have a port forward setting for "TCP+3", just "TCP" and "UDP"  - is there another name for it?  Do I need to be careful to NOT set TCP port forwarding above "4664" to avoid conflicts?

About the server: The log states that you have no servers in your list, is this correct?
I have a server list in prefs (the one 'recommended' when you upload the program).  It keeps the list from the last startup, and it will add more servers (if I enable it), but it will not automatically log in - I have to manually click a server to get it started.

Can someone translate  AICH quick so I don't have to look it up?
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Portage Problems are more than a heavy canoe....
« Reply #4 on: July 16, 2007, 05:31:52 PM »

It doesn't matter which ports you use as long as they are not reserved for another application. Feel free to use 1027, 12032 or 63982 as you please.

TCP+3 is the additional UDP port mentioned in the error message. There are three ports: TCP and UDP can be set by the user and the second UDP port has always the value of TCP+3.

AICH: advanced intelligent corruption handler -> http://www.amule.org/wiki/index.php/AICH
Logged

Irritable_Chihuahua

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: Portage Problems are more than a heavy canoe....
« Reply #5 on: July 16, 2007, 07:31:59 PM »

Another note about the automatic Login -

This problem did not occur the first time I loaded the program - it  logged on a picked a server automatically.  I don't know what the heck I changed in Preferences to mess it up.  Any ideas?
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Portage Problems are more than a heavy canoe....
« Reply #6 on: July 17, 2007, 01:55:05 AM »

There is an option to autoconnect only to static servers, maybe you checked it but you have no static servers, so it will not autoconnect. Or maybe you disabled the option to autoconnect at all. Anyway, check your preferences.

Regards.
Logged