Notes |
|
(0001689)
|
fulgas
|
2005-12-16 16:16
|
|
The server could always be busy or have a limit to high id so it's given you an lowid
edited on: 12-16-05 16:16 |
|
|
|
I tried about 15 or 20 different servers over several hours. All gave me a lowID. I tried to the "port-is-reachable"-tool and it said everything was fine.
Then I reset my internet connection, got a different ip (without a 0), and got a highID. |
|
|
|
IIRC, this is a design issue with the ed2k network. Besides, it's not aMule that decides your ID, that's up to the server. |
|
|
(0001692)
|
Kry
|
2005-12-17 11:09
|
|
Read some docs on ed2k protocol. 0-ended ips get ALWAYS a lowid, and you can blame edonkey for doing it that way in the first place.
Kad network fixes that issue, and you would have a proper id there. But it can't be fixed on ed2k.
If you send your id ended in .1, you will never get any packet - it's not your ip |
|