From: Catalin BOIE <util@deuroconsult.ro>
To: lartc@vger.kernel.org
Subject: Re: Fwd: [LARTC] Hashing filters
Date: Wed, 14 May 2003 09:30:58 +0000 [thread overview]
Message-ID: <marc-lartc-105290573215071@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105288767101323@msgid-missing>
> tc filter add dev $IF parent 30:0 prio 5 protocol ip u32
> tc filter add dev $IF parent 30:0 prio 5 handle 2: protocol ip u32 divisor 256
> tc filter add dev $IF parent 30:0 prio 5 handle 3: u32 ht 2:0: divisor 256
> tc filter add dev $IF parent 30:0 prio 5 u32 ht 3:6: match ip dst 192.168.0.6 flowid 30:6
>
> tc filter add dev $IF protocol ip parent 30:0 prio 5 u32 ht 800:: \
> match ip dst 192.168.0.0/24 hashkey mask 0x0000ff00 at 12 link 2:
> tc filter add dev $IF protocol ip parent 30:0 prio 5 u32 ht 800:: \
> match ip dst 192.168.0.0/24 hashkey mask 0x000000ff at 12 link 3:
>
> Doesn't work. Traffic never goes to class 30:6 but stays unclassified.
> Any suggestions?
Because traffic goes to 2:X filters.
Put
> tc filter add dev $IF protocol ip parent 30:0 prio 5 u32 ht 800:: \
> match ip dst 192.168.0.0/24 hashkey mask 0x000000ff at 12 link 3:
before the 2: test.
> Thank you.
>
> Michael
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
---
Catalin(ux) BOIE
catab@deuroconsult.ro
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-14 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 4:46 Fwd: [LARTC] Hashing filters Michael Ulitskiy
2003-05-14 9:30 ` Catalin BOIE [this message]
2003-05-14 17:26 ` Michael Ulitskiy
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-105290573215071@msgid-missing \
--to=util@deuroconsult.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.