Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Wingtung.Leung" <s965817@uia.ua.ac.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Priotizing Bandwith but without Shaping the Bandwith
Date: Thu, 28 Jun 2001 20:09:07 +0000	[thread overview]
Message-ID: <marc-lartc-99375902020263@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99367664430871@msgid-missing>

On Thu, 28 Jun 2001, Alexandra Alvarado wrote:

> Well, as i say before, a i need that all traffic udp has priority over
> tcp traffic, because i have to improve the voice quility over internet,
> well now i'm upgrading to Red Hat 7.1 (kernel 2.4) to use TOS field, but
> my question is if this sentence:
>
> iptables -t mangle -A PREROUTING -p udp -j TOS --set-tos
> Maximize-Throughput
>
> works or not, and how can i verify it?

I'm not sure, but I *think* this does *not* work.

> Until know i use CBQ, but with cbq i only asign specific bandwith to my
> clients using ip address, but i don't know how to prioritize traffic udp
> over tcp but without limiting the bandwith using CBQ.

A simple solution: attach 2 unbounded (!) classes to your interface, both
with a rather low transfer rate like 20kbit/s and give one a high
priority and the other one low priority. There is a priority parameter
when you create a class.

Now find a method to redirect both UDP and TCP traffic to the correct
class. An easy and lazy way is to mark the packets with iptables in the
mangle table. For example, mark UDP packets with 1 and TCP packets with 2.
Look at the iptables manpage for info about using it.

Use tc and install the fw filters which redirect the marked packets into
the correct classes. Redirect the packets marked with 1 to the low hi prio
class, and marked with 2 to the low prio class.

That should to it.

The low transfer rate is the minimum garantued rate for that class, all
bandwidth which is not allocated to a class, will be delivered to the
class with the highest priority.

I described a similar setup a few weeks/months ago, maybe reading the
archives gives you more hints.

Succes.


(Good that you type beneath the quote, the second step is cut irrelevant
parts from the quoted text. Signatures for example. And this small note
too. :-)

-- 
GnuPG public key: http://www.keyserver.net
fingerprint = A3C4 DE50 712D 4FA8 C564  4D96 5E06 C9CC ECFA 19C5



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

      parent reply	other threads:[~2001-06-28 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 16:21 [LARTC] Priotizing Bandwith but without Shaping the Bandwith Alexandra Alvarado
2001-06-28  9:07 ` Alexandra Alvarado
2001-06-28 14:55 ` Alexandra Alvarado
2001-06-28 19:17 ` Wingtung.Leung
2001-06-28 20:09 ` Wingtung.Leung [this message]

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-99375902020263@msgid-missing \
    --to=s965817@uia.ua.ac.be \
    --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