From: "Wingtung.Leung" <s965817@uia.ua.ac.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTP prioritizing
Date: Tue, 29 May 2001 23:28:51 +0000 [thread overview]
Message-ID: <marc-lartc-99117910508697@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99115898308144@msgid-missing>
On Tue, 29 May 2001, Andy Pyles wrote:
> I'm in the process of configuring a linux box to be a traffic shaper.
> for RTP streams. Basically what I would like to accomplish is the
> following:
> incoming/outgoing RTP streams.
>
> From examining the HOW-TO, it appears that that you can scan the IP
> headers based on the
> U32 selector, and grep for specific identifiers. I'm sure I can figure
> this out for RTP. Please clarify that I'm going
> in the right direction with this. RTP doesn't really have a specific
> block of port numbers you can specify.. so I'm assuming the only
> way to handle this is to use this U32 mechanism.
I hardly know anything about RTP streams, but does it use UDP? If there
isn't much other UDP traffic, you might have a descent working
configuration if you just seperate UDP from TCP traffic.
> My question is, is it possible with the 2.4 kernel to setup a
> "borrowing" mechanism?
> let me explain. What I would like to do is to reserve lets say 75% of
> all available bandwidth.
> With the stipulation that if there are no rtp streams, that all other
> traffic can "borrow" from this reserved bandwidth.
Of course, just use unbounded classes for this. The rate of the class
speficies the minimum bandwidth, but it allows you the borrow bandwidth
from other, default non-isolated classes, if:
1 - you need more bandwidth AND
2 - the other class has excess bandwidth
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-05-29 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 17:50 [LARTC] RTP prioritizing Andy Pyles
2001-05-29 23:28 ` 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-99117910508697@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 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.