All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marton Sandor <sanyi@sigmasoft.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Mixing classifiers
Date: Wed, 13 Aug 2003 15:53:04 +0000	[thread overview]
Message-ID: <marc-lartc-106079009103516@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106074276227381@msgid-missing>


On Wed, 13 Aug 2003, Steffen Moser wrote:

> > I tried using under a htb qdisc u32 filter for 1 class , and fw 
> > classifier for another but i get "RTNETLINK answers: Invalid argument" 
> > when i wanr ro insert the second type of classifier. 
> 
> I don't get any error messages when starting a script like this one:
> 
>   #!/bin/bash
> 
>   TC=./tc
>   DEV=eth0
>   LAN\x192.168.1.0/24
> 
>   $TC qdisc del dev $DEV root
>   $TC qdisc add dev $DEV root handle 1:0 htb
> 
>   $TC class add dev $DEV parent 1:0 classid 1:1 htb rate 2048kbit
>   $TC class add dev $DEV parent 1:0 classid 1:2 htb rate 4096kbit
> 
>   $TC filter add dev $DEV parent 1:0 protocol ip prio 1 u32 match ip dst $LAN classid 1:1
>   $TC filter add dev $DEV parent 1:0 protocol ip prio 2 handle 5 fw classid 1:2

Yes, this script work. I compared with my script and i observed that i 
get the error message only when i have the same prio for the filters. 
Try the fw filter with "prio 1 handle 5 fw"

Different prio's will solve my problem but still i'm curious

-- 
 Marton Sandor  -  sanyi@sigmasoft.ro

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

      parent reply	other threads:[~2003-08-13 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  2:44 [LARTC] Mixing classifiers Marton Sandor
2003-08-13 12:11 ` Steffen Moser
2003-08-13 15:53 ` Marton Sandor [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-106079009103516@msgid-missing \
    --to=sanyi@sigmasoft.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.