I have done the "definitive test" in my adsl line, using a real computer:
* Without incoming traffic management, my dns can take about 30s or more
to resolve a domain (when it resolve, sometimes it doesn't) when my adsl
line is saturated.
So the queue of my ISP doesn't give preference to the dns (at the
reverse, is it seems penalyzed),
But doing 3 paralell ftps (and some other p2p massive loadings at the same
time), with my line saturated, I see that the traffic of the 3 ftps is
well distributed, the hash indicator are moving, its rare to have a
connection with the hash stopped more than 5s.
* With ingress police for everything except for the dns packets, I have
the following:
The resolving is faster, about 5s to 10s.
But the ftps are not sharing the bandwidth very well. A ftp session can be
waiting 30s to move the hash indicator. The "turns" are much longer than
in the precedent case, I suppose this is a related with dropping packets.
I suppose also that the more are the tcp sessions, the more are the delay
between the turns.
--=20
__o
_ \<_
(_)/(_)
Saludos de Juli=E1n
EA4ACL
-.-
Foro Wireless Madrid
http://opennetworks.rg3.net
