From: Waters <waters@inbox.lv>
To: lartc@vger.kernel.org
Subject: [LARTC] help :)
Date: Sun, 28 Apr 2002 01:08:55 +0000 [thread overview]
Message-ID: <marc-lartc-101995612326324@msgid-missing> (raw)
Hello lartc,
I have about 400Kbit/s link, and I need to divide it into 2 parts (for
2 computers). What I have done wrong? Correct please!
tc qdisc add dev eth0 root handle 10: cbq bandwidth 400Kbit avpkt 1000
tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 400Kbit rate \
400Kbit allot 1514 weight 40Kbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 400Kbit rate \
100Kbit allot 1514 weight 10Kbit prio 5 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 10:1 classid 10:200 cbq bandwidth 400Kbit rate \
300Kbit allot 1514 weight 30Kbit prio 5 maxburst 20 avpkt 1000 \
bounded
tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 15
tc qdisc add dev eth0 parent 10:200 sfq quantum 1514b perturb 15
tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip dst \
10.0.0.2 flowid 10:200
tc filter add dev eth0 parent 10:0 protocol ip prio 25 u32 match ip dst \
10.0.0.3 flowid 10:100
--
Best regards,
Waters mailto:waters@inbox.lv
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-04-28 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 1:08 Waters [this message]
2002-04-28 15:20 ` [LARTC] help :) Stef Coene
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 8:35 [LARTC] help!! Nampreet Sarao
2006-01-28 3:20 ` gypsy
2006-02-16 5:19 ` Nampreet Sarao
2005-04-25 7:20 [LARTC] Help! Grace Baldonasa
2005-04-25 8:18 ` Ow Mun Heng
2002-06-11 14:44 [LARTC] HELP!!! Siller Gonzalez Pico, Mario A
2001-07-13 21:24 [LARTC] help!!! Ivan Chavez
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-101995612326324@msgid-missing \
--to=waters@inbox.lv \
--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.