aMule Forum
English => en_Bugs => Topic started by: KyroMaster on October 20, 2005, 06:21:41 PM
-
I´m using aMule behind a firewall, so I get a LowID. I´ve disabled the eMule extended port too because of that.
I´m one one of the biggest servers. When I start searching for popular music I get files with over 1500 sources, but when I start them I get only 4 sources. Even with a LowID this number seems a bit too low to me. And in general a seach on another server when you have a lowid doesn´t make sense IMHO, since you can´t download from that clients anyway. Why is this done though?
-
Forget it, I was wrong here. But the problem is still there :(
-
As I mentioned in another thread, you may want to enable the eMule extended UDP port, depending on the features of your firewall.
Are you doing a local search or a global search? Do a local search to see how many sources are available from your connected server. If it's a small number but a global search reveals there are many out there, try connecting to a different server.
-
I did a global search.
I noticed that aMule finds many sources for the files, but when it tries to connect to them almost all of them time out, so only a fraction remains. Is this normal with a LowID?
-
yes it is normal.
"global" search finds ALL sources on the ed2k net, but with lowID you can only connect to the one on YOUR server, so a LOCAL search would give you much more information on how many sources you end up with...
-
Ok, I think i´ll use local searches.
Why can´t I download from clients not on my server. I thought if they can´t connect to me because I´ve a lowid it doesn´t mean I can´t connect to them if they have a highID. Where am I wrong here?
-
the connection is in both ways, you cant connect to them and they cant connect to you...so with lowID your basically screwed
so server has todo it all for ya
with highID connection works both ways....
-
Originally posted by stefanero
[...] with lowID you can only connect to the one on YOUR server [...]
stefanero, this is just plain wrong.
When you are LowID, you can connect to any HighID client, regardless of what server they are connected to. And, you can't connect to any LowID client, even if they are on the same server as you.
KyroMaster, first you need to understand the difference between searches and finding sources. When you do a search, the server (or servers, for a global search) tells you the count of sources, but do not provide the actual sources to you. When you start a download, you get your initial set of sources only from your connected server. As you connect to those sources, you may learn about other sources from them via source exchange. Also, aMule will gradually poll the other servers in your server list (via UDP) for sources for the files you are trying to download.
The type of search you did to find the file has no effect on how you receive sources, or on which set of sources you receive.
After you learn about a source, you will try to connect to it. This may fail for a number of reasons. If you are LowID and a particular source is LowID, then you will never be able to connect to it. However, for precisely this reason, neither your server, other servers, or other clients should tell you about LowID sources. So, that isn't the explanation for a high initial source count which gets reduced as you attempt the connections. More likely is just general network failure, ipfilter, ISP blocking, etc.
-
ok well
from offical emule-project:
-Two clients on low ID cannot connect to each other, as it is not possible to route messages over two different servers. This will lead to less sources for the downloads
^^ but 2 lowID clients on the same server can connect to each other...
-Important: Since .23a low ID sources are dropped by eMule to keep load on servers to a minimum. Only low ID sources connected to the same server your client is connected to and low ID sources who want to download a file from you are accepted. Also low ID sources are not traded via Client to Client Source Exchange.
^^so a highID cleint will only except lowID clients, which are on the same server....thats what I wrote ken....
oh btw the url: http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=103
-
Originally posted by stefanero
-Two clients on low ID cannot connect to each other, as it is not possible to route messages over two different servers. This will lead to less sources for the downloads
^^ but 2 lowID clients on the same server can connect to each other...
That's an inferrence you draw, but it is incorrect. The first half of that statement ("Two clients on low ID cannot connect to each other") is not dependent on the second half as it seems. It is absolute. Even if it were possible for two LowID clients to trade protocol packets by passing it through the server, they can't trade file data. File data is never forwarded through the servers, only through a direct client-to-client connection which can't be established between two LowID clients.
-Important: Since .23a low ID sources are dropped by eMule to keep load on servers to a minimum. Only low ID sources connected to the same server your client is connected to and low ID sources who want to download a file from you are accepted. Also low ID sources are not traded via Client to Client Source Exchange.
^^so a highID cleint will only except lowID clients, which are on the same server....thats what I wrote ken....
Again, you're reading more into this than is there. Or less, depending on how you think of it. ;)
The part which reads "and low ID sources who want to download a file from you" is crucial.
I'm stuck at LowID and am intimately familiar with the limitations, but also the capabilities of that situation. :P I connect to and download from HighID clients on other servers all the time. And, so long as I'm on their queue waiting to download a file from them, the HighID clients can also download from me, too. Of course, they have to wait for me to open the connection to them when they reach the top of my queue, but it works just fine.