From: Crutcher Dunnavant <crutcher@datastacks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Request for comments
Date: Thu, 19 Jul 2001 12:30:49 -0400 [thread overview]
Message-ID: <20010719123049.B12691@mueller.datastacks.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0107191757400.17990-100000@groove.rdsnet.ro>
In-Reply-To: <Pine.LNX.4.21.0107191757400.17990-100000@groove.rdsnet.ro>; from ctrl@rdsnet.ro on Thu, Jul 19, 2001 at 06:44:52PM +0300
++ 19/07/01 18:44 +0300 - Cornel Ciocirlan:
> a) more efficient packet filtering. After a cache entry is created for a
> flow, we apply the ACLs for the packet and associate the action with the
> flow. All subsequent packets belonging to the same flow will be
> dropped/accepted without re-appying the packet filtering rules
I'm seeing an identification problem arise here. You have to be able to
identify packets in a flow robustly, and you have to be able to spot packets
trying to fake it. I dont see any way in which you will be able to avoid
the packet filtering rules here.
--
Crutcher <crutcher@datastacks.com>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$
next prev parent reply other threads:[~2001-07-19 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 15:44 Request for comments Cornel Ciocirlan
2001-07-19 16:30 ` Crutcher Dunnavant [this message]
2001-07-19 17:24 ` Francois Romieu
2001-07-19 17:29 ` jlnance
[not found] <Pine.LNX.4.21.0107191757400.17990-100000@groove.rdsnet.ro.suse.lists.linux.kernel>
2001-07-19 17:33 ` Andi Kleen
2001-07-19 17:52 ` Jakob Østergaard
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 18:33 Request for Comments Jan Willem Stumpel
2014-10-10 16:22 Request for comments Barclay Jameson
2014-10-10 17:04 ` John Spray
2024-09-02 5:38 Duncan Roe
2024-09-02 12:33 ` Pablo Neira Ayuso
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=20010719123049.B12691@mueller.datastacks.com \
--to=crutcher@datastacks.com \
--cc=linux-kernel@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.