From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SEPARATING VOIP AND SURFING
Date: Thu, 18 Nov 2004 00:44:01 +0000 [thread overview]
Message-ID: <419BF051.5050106@dsl.pipex.com> (raw)
In-Reply-To: <20041109175203.11372.qmail@web41524.mail.yahoo.com>
Ricardo Soria wrote:
> 1. So, starting at 80% of total 512kbit bandwidth
> (410kbit), there would be a waste of 102kbit. Is this
> completely necessary?? I think this is to ensure I
> have the queue on my side, and the queue is not on the
> side of the ISP. But, I fell tempted to think that
> 102kbit is too much for this purpose, considering that
> I really have 512kbit all time. What would you
> finally recommend ??
It depends how much you care about latency & what the people on your LAN
do/use.
I don't know what's acceptable latency and jitter for VOIP.
> 2. Could you please tell me a secure and trustworthy
> way to know if I am having queued packets under this
> class??
Again how much you have to do depends on the usage of your network. You
can explicitly mark each type of interavtive you want to priorotise.
If you have 20 hackers using P2P 24/7 then life is going to be harder -
if they just browse and email It's probably not worth trying too hard.
>
> 3. I am creating 2 different htb classes, one for
> interactive, and another for bulk, and also, 2
> different sfq inferior classes, one for each service.
> What else can I do to avoid sending a "mix of traffic"
> ??
If you have one queue for bulk it would need to be esfq if you want per
IP fairness. If you'd rather not patch then your origional queue for
each user is OK - but you should change SFQ's queue length.
>
> 4. If you still have a copy of my script, you can see
> I am giving "prio 0" to interactive classes, and "prio
> 1" to bulk classes. I also tested giving prio 0 and
> prio 1 at filters setup (and also, prio 1 to
> everybody, I am not so sure what worked better). What
> else can I do to emphasize interactive traffic
> priority??
>
The prio is most important, other things I do are - make sure
interactive has large burst and bulk none. Rather than mess with r2q I
set quantum to my MTU for HTB and SFQ. HTB can be tweaked to be more
accurate - but you may not need to bother. I also set a rate for my
interactive larger than I ever expect to be used, this is probably
unneccesary, but then I count game traffic a top prio - and I was using
upto 20K bytes/sec incoming while on a 64 player enemy territory server
recently.
> Sorry for the annoyances, very thanks in advance.
That's OK - It would help to know what the users do and how many are
active at once etc.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-18 0:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 17:52 [LARTC] SEPARATING VOIP AND SURFING Ricardo Soria
2004-11-15 12:42 ` Andy Furniss
2004-11-16 1:06 ` Ricardo Soria
2004-11-16 1:33 ` Jason Boxman
2004-11-16 14:53 ` Andy Furniss
2004-11-16 17:08 ` Jason Boxman
2004-11-17 1:15 ` Andy Furniss
2004-11-17 22:36 ` Ricardo Soria
2004-11-18 0:44 ` Andy Furniss [this message]
2004-11-18 1:08 ` Rick Marshall
2004-11-23 15:57 ` Ricardo Soria
2004-11-24 19:08 ` Ricardo Soria
2004-11-24 22:19 ` Ricardo Soria
2004-11-24 22:42 ` Rick Marshall
2004-11-25 10:48 ` Andy Furniss
2004-11-25 15:55 ` Andy Furniss
2004-11-28 23:50 ` Ricardo Soria
2004-11-29 21:53 ` Andy Furniss
2004-11-30 2:07 ` Ricardo Soria
2004-11-30 2:39 ` Andy Furniss
2004-11-30 12:23 ` Andy Furniss
2004-12-01 15:16 ` Ricardo Soria
2004-12-01 21:57 ` Andy Furniss
2004-12-06 22:54 ` Ricardo Soria
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=419BF051.5050106@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.