From: Craig Main <craig@themains.net>
To: lartc@vger.kernel.org
Subject: [LARTC] QoS for VoIP
Date: Fri, 28 Nov 2003 08:12:56 +0000 [thread overview]
Message-ID: <marc-lartc-107000832316611@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi all,
I would like to prioritise all VoIP traffic on a linux router. I am new
to QoS, tc and TOS, to please be gentle.
My logic works like this:
1) identify the VoIP packets
2) mark packets using iptables (with TOS?)
3) use tc to prioritise the marked packets.
Is this logic correct? If not, where is it flawed?
I understand that VoIP used the udp protocol and has packet sized less
than 250 bytes. Is simply reducing the MTU on the interfaces good enough
to give better thoughput, without the lag of larger packets trying to
pass though?
Are there any good HOWTOS?
TIA
Regards
Craig
--
Craig Main
RHCE
ST Solutions
Cell: 082-323-4670
Home Tel: 011-760-1900
AIM: SATuxman; ICQ: 75815570
http://www.stsolutions.co.za
http://www.linuxsa.com
____________________________
I WILL NEVER WIN AN EMMY I WILL NEVER WIN AN EMMY I WILL NEVER WIN AN
EMMY I WILL NEVER WIN AN EMMY Bart Simpson on chalkboard in episode 9F21
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-11-28 8:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 8:12 Craig Main [this message]
2003-11-28 18:05 ` [LARTC] QoS for VoIP Kilian Krause
2007-09-27 2:31 ` Ming-Ching Tiew
2007-09-27 16:05 ` Santiago
2007-09-28 1:09 ` Ming-Ching Tiew
2007-09-28 2:45 ` Santiago
2007-09-28 14:07 ` Santiago
2007-10-01 1:00 ` Ming-Ching Tiew
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 15:19 [LARTC] QoS for Voip Alessandro Ren
2004-07-16 15:53 ` Andreas Klauer
2004-07-16 16:54 ` Jason Boxman
2004-07-16 17:51 ` ibro tj
2004-07-16 18:38 ` Andreas Klauer
2004-07-19 12:45 ` Alessandro Ren
2004-07-19 13:19 ` Andreas Klauer
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-107000832316611@msgid-missing \
--to=craig@themains.net \
--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.