From: KOVACS Krisztian <hidden@balabit.hu>
To: Evan Langlois <evan@ddos.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: TProxy w/2.6
Date: Mon, 21 Jun 2004 19:04:52 +0200 [thread overview]
Message-ID: <20040621170452.GA6797@sch.bme.hu> (raw)
In-Reply-To: <54933.68.92.26.41.1087835494.squirrel@mercury.ddos.com>
Hi,
On Mon, Jun 21, 2004 at 11:31:34AM -0500, Evan Langlois wrote:
> I've been unable to get the TPROXY patch to patch against 2.6.5 ,2.6.6,
> nor 2.6.7. I've tried the patches on the original authors site and the
> patches in patch-o-matic-ng. The ones on the original authors site don't
> patch against a vanilla kernel of the version indicated. I have no idea
> what kernel patches they already had installed to make that patch, or what
> its supposed to patch against. I'd really prefer to use 2.6 for epoll.
>
> Does anyone have any suggestions of where to go from here?
Ask the right person! :)
The patches on our homepage were created for 2.6.6 with Jozsef
Kadlecsik's TCP window tracking patch applied. The one in POM-ng should
apply on 2.6.6 (and probably fail on others). BTW, applying window
tracking onto 2.6.7 has failed for me, so applying TProxy will fail as
well.
You can somewhat lower these requirements by skipping 04-nat_delete,
since that is a rarely-used optional part, and it is the only part of the
patches which requires the TCP window tracking code. I've just re-checked
that the patches contained in our tarball apply without rejects on vanilla
2.6.6.
--
Regards,
KOVACS Krisztian
next prev parent reply other threads:[~2004-06-21 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 16:31 TProxy w/2.6 Evan Langlois
2004-06-21 17:04 ` KOVACS Krisztian [this message]
2004-06-22 19:11 ` Evan Langlois
2004-06-22 22:08 ` KOVACS Krisztian
2004-06-24 1:12 ` Evan Langlois
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=20040621170452.GA6797@sch.bme.hu \
--to=hidden@balabit.hu \
--cc=evan@ddos.com \
--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.