Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alexandra Alvarado <aaaa@telconet.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Priotizing Bandwith but without Shaping the Bandwith
Date: Thu, 28 Jun 2001 14:55:26 +0000	[thread overview]
Message-ID: <marc-lartc-99375795513363@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99367664430871@msgid-missing>

"Wingtung.Leung" wrote:
> 
> On Thu, 28 Jun 2001, Alexandra Alvarado wrote:
> 
> > I have Red Hat 7.0 with kernel 2.2.16-22, and it doesn't support
> > "mangle" options, how can i do the same "Priotizing udp traffic over tcp
> > but without Shaping the Bandwith" with ipchains and cbq or only cbq?
> >
> > "Marek L. Kozak" wrote:
> > >
> > > Try this:
> > > iptables -t mangle -A PREROUTING -t udp -j TOS --set-tos
> > > Maximize-Throughput
> 
> (Please quote correctly, and type your own text *beneath* the quoted text.
> It makes the message much more readable.)
> 
> First of all, I don't think setting TOS field will change behaviour of the
> network queue, most routers just ignore that field. And even if it is used
> on the local Linux router, I don't think Alexandra wanted a high
> throughput for UDP traffic, but rather a low delay situation.
> 
> Please try to describe in detail what you mean with "giving priority to
> UDP traffic over TCP traffic", and what you want to achieve.
> 
> The HOWTO gives an example for splitting bandwith with unbounded classes,
> it might be good enough for your situation. Please try it first, and if it
> is not what you wanted, give the problems with that setup.
> 
> I'm not sure, but I don't think ipchains (kernel 2.2) supports setting the
> TOS field. It doesn't matter, you don't really need a firewall marker, you
> can also redirect the traffic using the general u32 filter.
> 
> --
> 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/


Hi, I'm Alexandra

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?

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.


Thanks

A.A.A.A.B.

_______________________________________________
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 14:55 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 [this message]
2001-06-28 19:17 ` Wingtung.Leung
2001-06-28 20:09 ` Wingtung.Leung

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-99375795513363@msgid-missing \
    --to=aaaa@telconet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox