From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] invert u32 match selector
Date: Sat, 25 Feb 2006 16:04:06 +0000 [thread overview]
Message-ID: <44007FF6.20302@dsl.pipex.com> (raw)
In-Reply-To: <20060221172517.6e5a433c.mailinglists@lucassen.org>
richard lucassen wrote:
> On Wed, 22 Feb 2006 11:43:40 +0200
> "Vaidas" <admin@vdx.lt> wrote:
>
>
>>With u32 you cannot negate, that's why it is lame...
>
>
> And why doesn't this work? (I send all port 80 to 1.2.3.4 to class 14
> /before/ I send the rest to classid 13):
>
> $TC filter add dev ${DEV_IFB} parent 1:0 prio 2 protocol ip u32 \
> match ip protocol 0x6 0xff \
> match ip dport 80 0xffff \
> match ip dst 1.2.3.4/32 \
> classid 1:14
>
> $TC filter add dev ${DEV_IFB} parent 1:0 prio 2 protocol ip u32 \
> match ip protocol 0x6 0xff \
> match ip dport 80 0xffff \
> classid 1:13
>
> Any ideas?
Looks OK to me - try what Anton suggested to be safe but order is
usually enough.
I guess IFB means this is ingress - if you are doing nat / or the ip you
match is on that machine maybe it not passing ifb with the address you
expect.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-25 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 16:25 [LARTC] invert u32 match selector richard lucassen
2006-02-22 9:43 ` Vaidas
2006-02-22 10:35 ` richard lucassen
2006-02-22 11:04 ` Anton Glinkov
2006-02-25 16:04 ` Andy Furniss [this message]
2006-02-26 17:38 ` richard lucassen
2006-03-01 15:01 ` Andy Furniss
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=44007FF6.20302@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox