From: "David S. Miller" <davem@davemloft.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: hadi@cyberus.ca, kaber@trash.net, netdev@oss.sgi.com
Subject: Re: [RFC] string matching ematch
Date: Wed, 26 Jan 2005 15:26:09 -0800 [thread overview]
Message-ID: <20050126152609.59e1a15e.davem@davemloft.net> (raw)
In-Reply-To: <20050126214119.GP31837@postel.suug.ch>
On Wed, 26 Jan 2005 22:41:19 +0100
Thomas Graf <tgraf@suug.ch> wrote:
> I'm not sure if mixing stateful with stateless stuff is such of a good
> idea. I think it should be separated and have stateful filters only be
> executed when the flow matters, not packets.
I think keeping things totally stateless would be the best
idea.
next prev parent reply other threads:[~2005-01-26 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 15:07 [RFC] string matching ematch Thomas Graf
2005-01-26 21:03 ` David S. Miller
2005-01-26 21:41 ` Thomas Graf
2005-01-26 23:26 ` David S. Miller [this message]
2005-01-27 14:20 ` Thomas Graf
2005-01-27 20:17 ` Pablo Neira
2005-01-27 20:51 ` Thomas Graf
2005-01-31 13:59 ` jamal
2005-02-01 1:26 ` Pablo Neira
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=20050126152609.59e1a15e.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).