All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Examples from HTB home page...
Date: Fri, 06 Sep 2002 20:47:22 +0000	[thread overview]
Message-ID: <marc-lartc-103134533725904@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103131597924022@msgid-missing>

On Friday, 06 September 2002, at 15:39:16 +0300,
eth wrote:

> 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.
> 
Maybe your kernel configuration changed in the meantime, and with the
new version you didn't compile some necessary features. Have just tried
your exact configuration with a 2.4.20-pre1 kernel and it works OK.

It seems you missed "U32 classifier" support either compiled in or as a
module. My box show the following modules loaded after trying your config:
Module                  Size  Used by    Not tainted
cls_u32                 4484   1  (autoclean)
sch_htb                18016   1  (autoclean)
pcnet32                13120   1  (autoclean)
mii                     1104   0  (autoclean) [pcnet32]

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Woody (Linux 2.4.19-pre6aa1)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-09-06 20:47 UTC|newest]

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

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-103134533725904@msgid-missing \
    --to=lartc@24x7linux.com \
    --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.