Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alexander Brill <kiowa@project23.no>
To: lartc@vger.kernel.org
Subject: [LARTC] multiple ingresses
Date: Fri, 24 May 2002 13:43:58 +0000	[thread overview]
Message-ID: <marc-lartc-102224787530454@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Is it possible to have multiple filters around an ingress so that you
can police your downloads more specific. What I'm trying to achieve is
to have all my ftp-traffic limited to 1024kbit on downloads. I included
some commands below so that you might better understand my thoughts on
the matter.

tc qdisc add dev eth0 root handle 1: htb default 2
tc class add dev eth0 parent 1: classid 1:1 htb rate 2048kbit ceil
2048kbit prio 1
tc class add dev eth0 parent 1:1 classid 1:2 htb prio 2 rate 1kbit ceil
2048kbit
tc qdisc add dev eth0 handle ffff: ingress
tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 2048kbit burst 47.0kb drop flowid 1:
tc class add dev eth0 parent 1:1 classid 1:3 htb rate 1024kbit ceil
1024kbit prio 1
tc qdisc add dev eth0 parent 1:3 handle 3 sfq perturb 10
tc filter add dev eth0 parent 1:3 protocol ip u32 match ip dport 21
0xffff flowid 1:3
tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 1024kbit burst 23.5kb drop flowid 1:3


-- 
Alexander Brill <kiowa@project23.no>
http://www.project23.no
PGP-key: http://alexb.egil.org/key.pub

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

                 reply	other threads:[~2002-05-24 13:43 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-102224787530454@msgid-missing \
    --to=kiowa@project23.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox