From: Nikolay Kichukov <hijacker@oldum.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic shaping vpn (GRE) traffic
Date: Mon, 11 Dec 2006 09:06:24 +0000 [thread overview]
Message-ID: <457D1F90.5070704@oldum.net> (raw)
In-Reply-To: <8cf5f0480612100855k56470461hdac146e0f2db7757@mail.gmail.com>
Hello syncmaster4,
I am not much of an routing expert myself, but if you are getting the
Illegal match error message, try looking in the command syntax or the
kernel config to check if you compiled all the necessary modules for the
command you are using.
Have you got support for protocol 47? Just guessing here.
-Nik
syncmaster4 wrote:
> Looking for some advise from the experts out there.
>
> We do simple traffice shaping and I'm having trouble figuring out how to
> shape vpn traffic using a tc filter.
>
> The following filter works fine for SSH
> tc filter add dev eth2 parent 1:0 protocol ip u32 match ip sport 22
> 0xffff classid 1:10
>
> The following throws and "Illegal match" error when trying to filter GRE
> traffic.
> tc filter add dev eth2 parent 1:0 protocol ip u32 \
> match ip protocol 47 0xff \
> match ip u16 0x10 00ff at 24 \
> classid 1:10
>
> Any pointers are greatly appreciated!
>
> CentOS 4.4 - 2.6.9-42.0.3.ELsmp
>
> Thanks!
> Craig
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-12-11 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 16:55 [LARTC] traffic shaping vpn (GRE) traffic syncmaster4
2006-12-11 9:06 ` Nikolay Kichukov [this message]
2006-12-11 18:04 ` Nikolay Kichukov
2006-12-11 19:24 ` 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=457D1F90.5070704@oldum.net \
--to=hijacker@oldum.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.