All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Robinson" <paul.robinson@eserv.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ,... RTNETLINK: Invalid Argument
Date: Thu, 15 Mar 2001 13:52:24 +0000	[thread overview]
Message-ID: <marc-lartc-98466437723589@msgid-missing> (raw)

Hi all,

I've got a problem i cant seem to find a way around... i've read the
Advanced Routing HOWTO, and im trying to setup (what i thought) would be a
simple bandwidth management scenario to limit trafic to a machine (1.2.3.4)
on the local lan to about 3K.

however... heres what im trying to do (follows the howto fairly closely)

-----
tc qdisc add dev eth0 root handle 1: cbq bandwidth 100Mbit avpkt 1000

tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 100Mbit rate
100Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000

tc class add dev eth0 parent 1:1 classid 1:2 cbq bandwidth 100Mbit rate
3Kbit allot 1514 weight 1Kbit prio 5 maxburst 20 avpkt 1000 bounded

tc qdisc add dev eth0 parent 1:2 sfq quantum 1514b perturb 15

tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip dst
1.2.3.4 flowid 1:2
-----

All works fine until the last statement;
# tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip dst
1.2.3.4 flowid 1:2
RTNETLINK answers: Invalid argument
#

Have i missed something obvious? or is something missing from my kernel??

Im running with kernel 2.4.0.

Regards, Paul


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-03-15 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 13:52 Paul Robinson [this message]
2001-03-17 23:08 ` [LARTC] CBQ,... RTNETLINK: Invalid Argument bert hubert

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-98466437723589@msgid-missing \
    --to=paul.robinson@eserv.com.au \
    --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.