-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lets talk about KaZZa,E-Donkey,and IMESH. I have absolutely no idea about how they work, but i do split traffic with two classes, one fore interactive, and a second one for the rest acting as a default class. The problem is that when these programs start working, the interactive services do not have the bw granted. - -----Mensaje original----- De: lartc-admin@xxxxxxxxxxxxxxx [mailto:lartc-admin@xxxxxxxxxxxxxxx] En nombre de Stef Coene Enviado el: sábado, 19 de abril de 2003 14:01 Para: GoMi; lartc@xxxxxxxxxxxxxxx Asunto: Re: RV: [LARTC] Re: My 1st BW Manager On Saturday 19 April 2003 12:10, GoMi wrote: > Thats exactly the problem i have been trying to solve for the last 2 > months. Bandwith sharing works great, but when it comes to shape DAP > programs, by any reason it fails, not granting the bw to other > services. No idea why. > > Stef, if you are interested in working around this problem, maybe we > could meet in a chat room, and you can login to my box and see what > happens, interested? Yes, but not now. But I can check it out myself. How do this DAP works? Do they open parallel tcp sessions the same server? And if they do, how many? And the other services that suffers from these DAP streams, is that also download (bulk traffic) or interactive traffic (ssh, telnet, dns)? And I suppose the DAP traffic and the other traffic belongs to different classes. Stef - -- stef.coene@xxxxxxxxx "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 iQA/AwUBPqFU0n7diNnrrZKsEQK+TACg8uM01JeH3L5CfxuxUUSVWrwFDbcAn04a osen2KdAqW4jxfihFGjUa274 =Ew3f -----END PGP SIGNATURE-----
