From: Anton <anton.vazir@gmail.com>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: TPROXY 4.1 patch?
Date: Sun, 18 May 2008 19:50:24 +0500 [thread overview]
Message-ID: <200805181950.24777.anton.vazir@gmail.com> (raw)
Hi !
Just hoping if anyone may have a working TPROXY 4.1 patch
against any of 2.6.24 or 2.6.25 kernel versions?
Patches provided by BALABIT on their site does not apply
cleanly on the mainstream kernels (and even after manual
patching of rejects kernel does not compile than, some
structure inconsistancies) , I suppose the patches have
been taken out of some of the kernel developments branches,
but I've did not found how to download any of this
branches. -git gives only stable tags, but there is just a
numeric tags...
There is some patches in the
http://people.netfilter.org/hidden/tproxy/
but they does not apply cleanly to a stable kernels either.
If someone have a patch or any advice, I'd be just
gratefull, TPROXY+SQUID is a great stuff btw.
Kind regards,
Anton.
next reply other threads:[~2008-05-18 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 14:50 Anton [this message]
2008-05-19 13:38 ` TPROXY 4.1 patch? KOVACS Krisztian
2008-05-19 13:55 ` Anton
2008-05-19 14:00 ` KOVACS Krisztian
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=200805181950.24777.anton.vazir@gmail.com \
--to=anton.vazir@gmail.com \
--cc=netfilter-devel@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.