From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sequence and Default port
Date: Tue, 23 Sep 2003 19:46:09 +0000 [thread overview]
Message-ID: <marc-lartc-106434652114447@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106423050719876@msgid-missing>
On Tuesday 23 September 2003 07:56, Raghuveer wrote:
> Here are the rules Iam applying to control outgoing traffic at WAN(eth0)
> interface for public hosted services.
> Here actual Isp rate = 512Kbit, rate taken = 97% of 512Kbit, eth0 ip is
> 192.168.1.2
>
> tc qdisc add dev eth0 root handle 1: cbq bandwidth 100Mbit avpkt 1000 cell
> 8 tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 100Mbit rate
> 497Kbit weight 49Kbit prio 3 allot 1514 cell 8 maxburst 10 avpkt 1000
> bounded
> /* Hosted http server bandwidth = 64Kbit */
> tc class add dev eth0 parent 1:1 classid 1:2 cbq bandwidth 100Mbit rate
> 64Kbit weight 6Kbit prio 3 allot 1514 cell 8 maxburst 10 avpkt 1000
> tc filter add dev eth0 parent 1:1 protocol ip prio 3 u32 match ip src
> 192.168.1.2 match ip sport 80 0xffff classid 1:2
>
> /* Hosted ftp server bandwidth = 64Kbit */
> tc class add dev eth0 parent 1:1 classid 1:3 cbq bandwidth 100Mbit rate
> 64Kbit weight 6Kbit prio 3 allot 1514 cell 8 maxburst 10 avpkt 1000
> tc filter add dev eth0 parent 1:1 protocol ip prio 3 u32 match ip src
> 192.168.1.2 match ip sport 21 0xffff classid 1:3
>
> /* Default : Rest/Other traffic */
> tc class add dev eth0 parent 1:1 classid 1:4 cbq bandwidth 100Mbit rate
> 369Kbit weight 40Kbit prio 3 allot 1514 cell 8 maxburst 10 avpkt 1000
> /* Here I want replace the below rule with a simple rule based only on
> port i.e by using some default port other than 80, 21 as sport, which
> according to your last mail is not possible, hence pls check whether the
> below rule will do for remaining traffic */
> tc filter add dev eth0 parent 1:1 protocol ip prio 3 u32 match ip src
> 0/0 match ip dst 0/0 classid 1:4
>
> Pls let me know whether the above rules are framed correctly or can be
> done in a better way.
I can't do it better then you did :)
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-23 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 11:37 [LARTC] Sequence and Default port Raghuveer
2003-09-22 18:25 ` Stef Coene
2003-09-23 6:08 ` Raghuveer
2003-09-23 19:46 ` Stef Coene [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-106434652114447@msgid-missing \
--to=stef.coene@docum.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.