From: Julian Gomez <kluivert@tm.net.my>
To: netfilter@lists.netfilter.org
Subject: Re: Skipping connection tracking for certain traffic types?
Date: Sat, 31 May 2003 15:18:43 +0800 [thread overview]
Message-ID: <20030531071843.GA1765@floyd> (raw)
In-Reply-To: <20030527192155.V20519@poliisi.iki.fi>
On Tue, May 27, 2003 at 10:49:56PM +0300, Ville Mattila spoke thusly:
>Correct me on this if I'm wrong: It is a feature of Netfilter that
>whenever conntrack is registered in kernel, then for example any UDP
>packet passing through the firewall causes the state table to be consulted
>resulting in either update of an old state entry if found or creation of a
>new state.
I think there is a NOTRACK patch in p-o-m, but haven't checked really. I
kind of remember Henrik Nordstrom talking about it before, but a quick
websearch only turns up this.
http://lists.netfilter.org/pipermail/netfilter-devel/2001-September/
005541.html
next prev parent reply other threads:[~2003-05-31 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 19:49 Skipping connection tracking for certain traffic types? Ville Mattila
2003-05-31 7:18 ` Julian Gomez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 9:03 Ville Mattila
2003-05-29 12:51 ` Martin Josefsson
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=20030531071843.GA1765@floyd \
--to=kluivert@tm.net.my \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox