Print

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

[matkam]

Sometimes a server can be stupid and assign a low ID even if a firewall is properly configured. There should be an option so that aMule will automatically try another server when assigned a low ID

[phoenix]

matkam,

This is a little nonsense to me. Why would the server do that? Lowids are bad for the servers too.

What DOES happen is a server give a high id, when it should have given a lowid. Some servers misbehave like that some months ago.

So, I think your request is not ok, how many times should we retry connection? Forever or until we meet another misbehaving server? If one server gives you lowid, it means that anyone else from the outside will not be able to reach you. If a server gives you a false high id, you will get a high id but you become a leecher.

Check your firewall configuration, it is most surely not properly set.

Cheers!

[Supersnail]

matkam is right according to the wiki: http://www.amule.org/wiki/index.php/FAQ_ed2k#What_is_LowID_and_HighID?

There's still an exception. Sometimes badly configured or very busy servers give LowID to some clients although the 4662 TCP port is opened. This are rare exceptions, but it might happen sometime.

Although I don't think that such an option is necessary. If a server gives you a low id while you actually should have a high id, it's very easy to disconnect and reconnect manually.

Besides, such an option will result in problems if someone really has a low id. aMule would then try to find a server where it gets a high id while every server will give it a low id.

[lfroen]

matkam: it doesn't work like this. You can't assign id to yourself. Whatever ID server assigns to you - that's what you have, High or Low.

Supersnail: matkam have no idea what is he/she talking about. You can't fix "badly configured server" by assigning id to yourself; go and blame server owner.

[Supersnail]

lfroen: as far as I read matkam isn't talking about assigning an ID to yourself, but disconnecting and reconnecting

[phoenix]

Originally posted by Supersnail
matkam is right according to the wiki: http://www.amule.org/wiki/index.php/FAQ_ed2k#What_is_LowID_and_HighID?

There's still an exception. Sometimes badly configured or very busy servers give LowID to some clients although the 4662 TCP port is opened. This are rare exceptions, but it might happen sometime.

Hum, could anyone confirm that information? What is the source of this wiki?

matkam, do you confirm that a good server gives you a low id? Notice that there are bad servers that give you a high id when they should not. I personally have a lowid machine that has NO port forwarding at all, and there were a couple of servers that used to give me a high id. This is no bullshit. So it is important to be sure about this information. SauGeileGirls and Porno-Flatrate are examples of servers that gave me high id when they should not. But I don't know if this still happens.

In my opinion, a server giving a low id because it is busy or bad configured is a brain damage symptom. This will only make the server more busy than it was before, because lowids mean overhead for the server. There is an explicit option in server configuration to limit lowid clients. AFAIK, a server only gives you a lowid if it does not receive an answer from your TCP port.

Cheers!

[GonoszTopi]

I can confirm, that good servers (e.g. Razorback2 or DonkeyServer No.1) can give you a LowID even when you have port 4662 (or whatever) opened. I don't know whether this is because of high server load or a congested network, but it happens to me from time to time. After some retries I always get a HighID.

[Ateo]

I can also confirm that Razorback gives out LowIDs when a HighID is in order. Same with other servers...