From: "Atahualpa Jones" <atahualpa@gmx.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] any errors in this script?
Date: Thu, 07 Aug 2003 12:30:36 +0000 [thread overview]
Message-ID: <marc-lartc-106025950804818@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106025825203449@msgid-missing>
Hi,
I would suggest adding an sfq qdic to class 1:10, 1:11 and 1:12:
tc qdisc add dev ppp0 handle 2:0 parent 1:10 sfq perturb 10
tc qdisc add dev ppp0 handle 3:0 parent 1:11 sfq perturb 10
tc qdisc add dev ppp0 handle 4:0 parent 1:12 sfq perturb 10
nothing else would have to be changed, sfq makes sure that when your upload
is maxed no connection can dominate over others and everyone gets a fair
amount of the bandwidth.
For more info on sfq read chapter 9.2.3 of the LARTC howto.
Regards,
Ata
----- Original Message -----
From: "Tom Verbeek" <tom@designobjekt.de>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, August 07, 2003 2:08 PM
Subject: [LARTC] any errors in this script?
> Hi,
>
> ok, I dropped the idea of using Wondershaper without having background
> knowledge and are now trying to set up my own script :)
>
> Can anyone please take a look at the following script and point me to
> any errors? Thanks!
>
> my max. upload bandwidth is 192 Kbit/s and my goal is to ensure smooth
> gameplay (udp) while allowing other protocols to use up the remaining
> bandwidth. Mail is supposed to be treated with the least priority.
>
> Cheers,
> Tom.
>
> #-----------------------------------------------------
> # clean existing down- and uplink qdiscs, hide errors
> tc qdisc del dev ppp0 root 2> /dev/null > /dev/null
> tc qdisc del dev ppp0 ingress 2> /dev/null > /dev/null
>
> #root htb with non-classified data to 1:11
> tc qdisc add dev ppp0 root handle 1: htb default 11
>
> #max uplink class
> tc class add dev ppp0 parent 1: classid 1:1 htb rate 180kbit ceil 180kbit
burst 2k
>
> #interactice class
> tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 130kbit ceil
180kbit burst 2k prio 0
>
> #default class
> tc class add dev ppp0 parent 1:1 classid 1:11 htb rate 40kbit ceil 180kbit
burst 2k prio 1
>
> #slow class
> tc class add dev ppp0 parent 1:1 classid 1:12 htb rate 10kbit ceil 70kbit
burst 2k prio 2
>
> #put udp into interactive class
> tc filter add dev ppp0 parent 1:0 protocol ip prio 0 u32 \
> match ip protocol 17 0xff \
> flowid 1:10
>
> #put mail into slow class
> tc filter add dev ppp0 parent 1:0 protocol ip prio 2 u32 \
> match ip sport 25 0xffff \
> flowid 1:12
>
> tc filter add dev ppp0 parent 1:0 protocol ip prio 2 u32 \
> match ip dport 25 0xffff \
> flowid 1:12
>
> tc filter add dev ppp0 parent 1:0 protocol ip prio 2 u32 \
> match ip sport 110 0xffff \
> flowid 1:12
>
> tc filter add dev ppp0 parent 1:0 protocol ip prio 2 u32 \
> match ip dport 110 0xffff \
> flowid 1:12
> #-----------------------------------------------------
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-08-07 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 12:08 [LARTC] any errors in this script? Tom Verbeek
2003-08-07 12:30 ` Atahualpa Jones [this message]
2003-08-07 17:01 ` Stef Coene
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-106025950804818@msgid-missing \
--to=atahualpa@gmx.at \
--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.