From: "GoMi" <gomiuk@hotmail.com>
To: lartc@vger.kernel.org
Subject: RE: RV: [LARTC] Re: My 1st BW Manager
Date: Sat, 19 Apr 2003 13:53:23 +0000 [thread overview]
Message-ID: <marc-lartc-105076049031862@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105074710025619@msgid-missing>
-----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@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] En nombre de Stef Coene
Enviado el: sábado, 19 de abril de 2003 14:01
Para: GoMi; lartc@mailman.ds9a.nl
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@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl 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-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-19 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 10:10 RV: [LARTC] Re: My 1st BW Manager GoMi
2003-04-19 12:01 ` Stef Coene
2003-04-19 13:53 ` GoMi [this message]
2003-04-19 14:36 ` Stef Coene
2003-04-19 15:19 ` rio
2003-04-20 21:51 ` Stef Coene
2003-04-21 1:59 ` rio
2003-04-21 2:30 ` Martin A. Brown
2003-04-21 3:12 ` rio
2003-04-21 9:12 ` Stef Coene
2003-04-21 9:15 ` Stef Coene
2003-04-21 9:24 ` rio
2003-04-21 9:28 ` Stef Coene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105076049031862@msgid-missing \
--to=gomiuk@hotmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.