From: "Tarek W." <ticallion@terra.net.lb>
To: lartc@vger.kernel.org
Subject: [Fwd: Re: [LARTC] QoS for real-time data on ADSL]
Date: Tue, 26 Nov 2002 07:30:17 +0000 [thread overview]
Message-ID: <marc-lartc-103829581701554@msgid-missing> (raw)
-----Forwarded Message-----
> From: Tarek W. <tarek@cyberia.net.lb>
> To: LARTC@mailman.ds9a.nl
> Subject: Re: [LARTC] QoS for real-time data on ADSL
> Date: 26 Nov 2002 09:12:15 -0200
>
>
> This is purely theoretical... VOIP afaik consumes a decent amount of
> bandwidth... I gather you will not be doing any nat. My advice to u is
> to drop sqf as it is fu when it comes to bandwidth... I'd set up a root
> qdisc pfifo (1:), default flowid 22 (or 1:22), with a child (1:1) class
> again a regular pfifo only. now cap that at around 90% of the "stated"
> available speed maybe even less since its adsl... now create two
> children of that class, the first (1:21) with prio 1, the second
> (1:22)with prio 2 (i am not talking about the prio qdisc here, if ur
> lost, consult the lartc howto), rate and ceil r irrelevant. create two
> children under (1:21), 1:31 with prio 1 and 1:32 with prio2. enqueue sfq
> under the 1:31 and TBF under 1:32. now attach filters to the root qdisc
> which dump VOIP traffic in 1:21, then attach filters to 1:21 which dump
> ACK packets in 1:31 and others with lower priority to dump everything
> else (effectively all other VOIP traffic) in 1:32. i think that's a
> fullproof solution...
>
> On Mon, 2002-11-25 at 06:38, Thomas Jalsovsky wrote:
> >
> > Hello,
> >
> > I have an ADSL connection to ISP. Our config at the moment is 64k
> > upstream and 384 downstream. I would like to set up the upstream QoS
> > polixy/shaping for allowing real-time protocols, in my case VoIP (RTP).
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-11-26 7:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-103829581701554@msgid-missing \
--to=ticallion@terra.net.lb \
--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.