From: KOVACS Krisztian <hidden@balabit.hu>
To: netfilter@lists.netfilter.org
Subject: Re: ipsec-01-output-hooks / ipsec-02-input-hooks patches vs. 2.6.14
Date: Mon, 21 Nov 2005 13:17:52 +0100 [thread overview]
Message-ID: <200511211317.52647@nienna> (raw)
In-Reply-To: <43819D19.9010506@atosorigin.com>
Hi,
On Monday 21 November 2005 11.10, Markus Marquardt wrote:
> i've tried to apply the netfilter pom-ng-20051115 patches for
> ipsec-01-output-hooks and ipsec-02-input-hooks against kernel 2.6.14.2.
>
> When using patch-o-matic-ng both complained about missing nf_reset. When
> trying to apply them manually, the former applied with some offset &
> fuzz, the latter failed and complained about missing files etc.
>
> Is there any workaround or work-in-progress to make this working on
> 2.6.14?
Patrick McHardy has been working on getting those patches ready for
mainline inclusion lately. He has posted the latest incarnation of his
patches to the netfilter-devel mailing list recently. (Note however, that
those patches are for the latest Linux 2.6.15 development branch and not
for 2.6.14.) You can take a look at the patches in the mailing list
archive:
http://marc.theaimsgroup.com/?l=netfilter-devel&m=113250450910387&w=2
So yes, there's very serious work going on to get those patches in
mainline (probably in 2.6.16).
--
Regards,
Krisztian Kovacs
next prev parent reply other threads:[~2005-11-21 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 10:10 ipsec-01-output-hooks / ipsec-02-input-hooks patches vs. 2.6.14 Markus Marquardt
2005-11-21 12:17 ` KOVACS Krisztian [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 15:07 Markus Marquardt
2005-11-22 13:39 ` Marco Berizzi
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=200511211317.52647@nienna \
--to=hidden@balabit.hu \
--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 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.