From: Harald Welte <laforge@netfilter.org>
To: Patrick Schaaf <bof@bof.de>
Cc: macadanet@yahoo.es,
lista de correo netfilter <netfilter-devel@lists.netfilter.org>
Subject: Re: string match -> new option
Date: Sun, 2 Mar 2003 10:59:15 +0100 [thread overview]
Message-ID: <20030302095915.GC2296@naboo.clug.de> (raw)
In-Reply-To: <20030301063948.GF24025@oknodo.bof.de>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Sat, Mar 01, 2003 at 07:39:48AM +0100, Patrick Schaaf wrote:
> > I modificated ipt_string.c
>
> Sigh. Why is it that people must work on the pieces that others
> already abandoned as fundamentally broken? See my point 1), below.
>
> > This patch acepts regular expresions.
>
> It was only a question of time...
please, again:
Look at 'libqsearch' from Philipe Biondi. (I don't have the URL here
right now, but 'libqsearch' + 'kernel' on google gives you the result).
This is the way to do pattern matching on TCP streams in the kernel...
> best regards
> Patrick
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-03-02 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 1:53 string match -> new option macadanet
2003-03-01 6:39 ` Patrick Schaaf
2003-03-01 15:47 ` Michael Rash
2003-03-02 9:59 ` Harald Welte [this message]
2003-03-02 11:36 ` Patrick Schaaf
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=20030302095915.GC2296@naboo.clug.de \
--to=laforge@netfilter.org \
--cc=bof@bof.de \
--cc=macadanet@yahoo.es \
--cc=netfilter-devel@lists.netfilter.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.