From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc hard problem
Date: Sat, 06 Jul 2002 14:08:59 +0000 [thread overview]
Message-ID: <marc-lartc-102596456208382@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102592292622661@msgid-missing>
On Sat, Jul 06, 2002 at 02:10:31PM +0200, bert hubert wrote:
> > Voice always come first, data can only use the bandwidth left.
>
> I've tried this and you can't get it perfect. The big thing with voice is
> that it really hates delays. I think you'll be able to do 3 calls and have
> data active at the same time.
Oh, by the way, you need to install rules at *both* ends! Otherwise you have
little control over downstream, except for dropping it and hoping tcp slows
down enough.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-06 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 2:45 [LARTC] tc hard problem Patrick Chan
2002-07-06 12:10 ` bert hubert
2002-07-06 14:08 ` bert hubert [this message]
2002-07-08 3:17 ` Patrick Chan
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-102596456208382@msgid-missing \
--to=ahu@ds9a.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox