From: Andrea Rossato <mailing_list@istitutocolli.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to limit bandwidth by port?
Date: Fri, 13 Dec 2002 14:57:29 +0000 [thread overview]
Message-ID: <marc-lartc-103979154610988@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103972758027709@msgid-missing>
DOWNLINK"0
UPLINK\x125
DEV=ppp0
tc qdisc add dev $DEV root handle 1: htb default 10
tc class add dev $DEV parent 1: classid 1:1 htb rate ${UPLINK}kbit burst 6
tc class add dev $DEV parent 1:1 classid 1:10 htb rate ${UPLINK}kbit \
ceil $[UPLINK}kbit burst 6k prio 1
tc class add dev $DEV parent 1:1 classid 1:20 htb rate $[3*$UPLINK/10]kbit\
ceil $[9*$UPLINK/10]kbit burst 6k prio 2
tc qdisc add dev $DEV parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev $DEV parent 1:20 handle 20: sfq perturb 10
tc filter add dev $DEV parent 1:0 protocol ip prio 10 u32 \
match ip dport 8080 0xffff flowid 1:20
traffic to dport 80 will get 3/10 of bandwith (with possibility to
borrow up to 9/10)
andrea
David Coello wrote:
> Hi again
>
> I am making all the test and probes i cann´t imagine but i begin to
> think it´s imposible to limit bandwidth by port. Anybody could put me a
> code example that makes this please?
>
> Thanks and regards
> David Coello
>
>
>
> _______________________________________________
> 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:[~2002-12-13 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 21:11 [LARTC] How to limit bandwidth by port? David Coello
2002-12-13 14:57 ` Andrea Rossato [this message]
2003-01-03 6:51 ` mdew
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-103979154610988@msgid-missing \
--to=mailing_list@istitutocolli.org \
--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.