From: Roberto Nibali <ratz@drugphish.ch>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] TCP window tracking patch backported from the 2.6 tree
Date: Tue, 28 Jun 2005 18:01:07 +0200 [thread overview]
Message-ID: <42C17443.60909@drugphish.ch> (raw)
In-Reply-To: <Pine.LNX.4.58.0506281201590.12765@blackhole.kfki.hu>
Hello Jozsef,
Thanks, looks like tomorrow is another netfilter day for me.
> The TCP window tracking patch backported from the 2.6 tree can now be
> found in the patch-o-matic-ng svn repository. The 2.4 version of the
> nf-log patch (which is required) has been updated as well.
Is the conntrack_error-api still needed and if so, where can I find it?
I'm referring to:
https://svn.netfilter.org/netfilter/trunk/patch-o-matic-ng/patchlets/tcp-window-tracking/info
> Please report me any success/failure reports wether it's an improvement
> compared to the previous version in your environment or not.
Do you happen to have a changelog written down somewhere or shall I diff
the two linux-2.4 patches?
Regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2005-06-28 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 10:08 [PATCH] TCP window tracking patch backported from the 2.6 tree Jozsef Kadlecsik
2005-06-28 16:01 ` Roberto Nibali [this message]
2005-06-29 7:39 ` Jozsef Kadlecsik
2005-06-29 9:18 ` Roberto Nibali
2005-06-29 10:07 ` Jozsef Kadlecsik
2005-06-29 10:26 ` Jozsef Kadlecsik
2005-06-29 14:55 ` Daniel Hartmeier
2005-06-30 7:48 ` Jozsef Kadlecsik
2005-06-30 11:13 ` Daniel Hartmeier
2005-07-01 11:58 ` Jozsef Kadlecsik
2005-07-06 11:15 ` Daniel Hartmeier
2005-07-06 11:40 ` Jozsef Kadlecsik
2005-07-06 12:37 ` KOVACS Krisztian
2005-06-29 14:22 ` Roberto Nibali
2005-06-30 7:51 ` Jozsef Kadlecsik
2005-07-01 21:31 ` Jozsef Kadlecsik
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=42C17443.60909@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=kadlec@blackhole.kfki.hu \
--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.