From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] U32 filter for IPSEC (ESP)
Date: Wed, 08 Jan 2003 18:29:41 +0000 [thread overview]
Message-ID: <marc-lartc-104205065011701@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104180993325505@msgid-missing>
On Mon, Jan 06, 2003 at 12:49:54AM +0100, Gilles Douillet wrote:
> so this u32 filter should work ? (I can use fw filter because the
> firewall/VPN can't mark pakets :-(
>
> tc filter add dev ethX parent X:0 protocol ip prio X u32 match ip protocol
> 50 0xff flowid X:XX ?
Looks fine, but try proving it - just send this traffic to anotherwise empty
class and run 'tc -s qdisc ls dev eth0' and 'tc -s class ls dev eth0' to see
if the counters change.
Regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-08 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 23:49 [LARTC] U32 filter for IPSEC (ESP) Gilles Douillet
2003-01-08 18:29 ` bert hubert [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-104205065011701@msgid-missing \
--to=ahu@ds9a.nl \
--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.