From: netfilter@interlinx.bc.ca
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: testing checksum in helpers is redundant with tcp_window_tracking
Date: Fri, 28 Feb 2003 07:13:40 -0500 [thread overview]
Message-ID: <20030228121336.GB9692@pc.ilinx> (raw)
In-Reply-To: <Pine.LNX.4.33.0302281127290.27528-100000@blackhole.kfki.hu>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Fri, Feb 28, 2003 at 11:33:15AM +0100, Jozsef Kadlecsik wrote:
>
> No, I think that is a bad idea. The tcp-window-tracking patch patches the
> default helpers (ftp, irc) and remove the redundant checkings.
Right. I have noticed this. But based on that idea, it should patch
all of the helpers, but that becomes a maintenance nightmare.
> However the
> current status of the patch is 'extra'.
Right. I understand that.
> No other
> subsystem/patch should be made dependent of it.
If it were a requirement type of dependancy, I would completely agree
with you, but I am talking about an optional "take advantage of it if
it's there and business as usual if it's not" type dependency.
Adding a macro to tcp-window-tracking (simply signifying it's in the
kernel) and wrapping the tcp checks in helpers with a test for the
macro does not introduce any loss of functionality at all. A module
writer doesn't even have to use it if he doesn't want to, but if he
wants his module to be as efficient as possible in the presence of
tcp-window-tracking, he can use the macro.
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-02-28 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:21 testing checksum in helpers is redundant with tcp_window_tracking netfilter
2003-02-28 9:04 ` Patrick Schaaf
2003-02-28 10:33 ` Jozsef Kadlecsik
2003-02-28 12:13 ` netfilter [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=20030228121336.GB9692@pc.ilinx \
--to=netfilter@interlinx.bc.ca \
--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.