All of lore.kernel.org
 help / color / mirror / Atom feed
From: eth <eth@finsiel.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] Examples from HTB home page...
Date: Fri, 06 Sep 2002 12:39:16 +0000	[thread overview]
Message-ID: <marc-lartc-103131597924022@msgid-missing> (raw)


... do not work anymore. Anybody with a hint? I've got a fully 
functional HTB setup and just wanted to replace the kernel from 2.4.17 
to 2.4.19. In the end the modified tc binary doesn't recognize "tc 
filter add" (yet it does accept qdisc show and recognizes htb...)

    I've downloaded the 2.4.19 from kernel.org, iproute2 (2.4.7), 
 installed the patches (to kern and iproute) and ended with a  kernel / 
tc combo that at the following example (taken from from HTB page):

tc qdisc add dev eth0 root handle 1:0 htb default 12
tc class add dev eth0 parent 1:0 classid 1:1 htb rate 100kbps ceil 100kbps
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 30kbps ceil 100kbps
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 10kbps ceil 100kbps
tc class add dev eth0 parent 1:1 classid 1:12 htb rate 60kbps ceil 100kbps

tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip src 
1.2.3.4 match ip dport 80 0xffff flowid 1:10  
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip src 
1.2.3.4 flowid 1:11

... chokes at the "tc filter add " with:

RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument

As far as I can tell this *should* work, it did 6 months ago on a 2.4.17.

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

             reply	other threads:[~2002-09-06 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 12:39 eth [this message]
2002-09-06 20:47 ` [LARTC] Examples from HTB home page Jose Luis Domingo Lopez

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-103131597924022@msgid-missing \
    --to=eth@finsiel.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.