All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petre Daniel <dani@cyber.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] problem limiting a subnet !
Date: Wed, 20 Aug 2003 14:12:32 +0000	[thread overview]
Message-ID: <marc-lartc-106138979118991@msgid-missing> (raw)


i have this problem limiting a subnet.

i run a 2.4.22-rc2 router with htb tc binary and htb.init

i got an eth1 pn this router which is linked to a 1.2.3.4/28 subnet of 
some clients and i wanted to limit their download via:

tc class add dev eth1 parent 1: classid 1:2 htb rate 100Mbit ceil 100Mbit

tc class add dev eth1 parent 1:11 classid 1:2 htb rate 32Kbit prio 6
tc qdisc add dev eth1 parent 1:2 handle 2 sfq perturb 10
tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst 1.2.3.4/28 classid 1:2

still,i am able to download at 7 MB/sec via 1.2.3.5 ip from that class..

anyone can guide me to repair some error ?

thanks.

-- 
Petre Daniel,System & Network Administrator.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-08-20 14:12 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-106138979118991@msgid-missing \
    --to=dani@cyber.ro \
    --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.