All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai RUSU <dizzy@roedu.net>
To: lartc@vger.kernel.org
Subject: [LARTC] hash filters & prio/pref
Date: Tue, 09 Apr 2002 09:44:42 +0000	[thread overview]
Message-ID: <marc-lartc-101834504818957@msgid-missing> (raw)

Hi

If using hash filters like the ones below does the prio/pref parameter
work?

tc filter add dev eth0 parent 1:0 handle 2: protocol ip u32 divisor 256
tc filter add dev eth0 parent 1:0 protocol ip u32 ht 800:: match ip
dst 0/0 hashkey mask 0x000000ff at 16 link 2:

tc filter add dev eth0 parent 1:0 prio 10 protocol ip u32 ht 2:4
match ip dst 1.2.3.4/32 flowid 1:20
tc filter add dev eth0 parent 1:0 prio 5 protocol ip u32 ht 2:4
match ip dst 1.2.3.4/32 flowid 1:10

Well, it doesnt work. The kernel send the traffic to flowid 1:20 not 1:10.
The second filter which has a better priority isnt checked before the
first one, in fact it seems that in a hash table the filters are checked
in their order of creation without any consideration of the prio/pref
parameter. This doesnt happen if I dont use hashes.

Is it a bug? Or can I do something to workarround that without, reordering
of filters position?

Thanks

----------------------------
Mihai RUSU

Disclaimer: Any views or opinions presented within this e-mail are solely
those of the author and do not necessarily represent those of any company,
unless otherwise specifically stated.


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

             reply	other threads:[~2002-04-09  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  9:44 Mihai RUSU [this message]
2002-04-09  9:53 ` [LARTC] hash filters & prio/pref Martin Devera

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-101834504818957@msgid-missing \
    --to=dizzy@roedu.net \
    --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.