All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Dahlem <Robert.Dahlem@gmx.net>
To: netfilter-devel@lists.netfilter.org
Cc: Ronald.Moesbergen@bkvision.nl, kaber@trash.net
Subject: Re: [Patch] ipsec-nat patches for 2.6.10 (was: ipsec-nat patches for 2.6.9)
Date: Wed, 05 Jan 2005 02:11:57 +0100	[thread overview]
Message-ID: <41DB3EDD.4050403@gmx.net> (raw)
In-Reply-To: <41BF5BB9.5090901@trash.net>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

Hi,

On 14.12.2004 22:44, Patrick McHardy wrote:

>>What is the timeline for getting these patches (and policy match) into
>>the kernel.org tree? The next major release of Shorewall relies on them
>>for native 2.6 IPSEC support.  

> I will submit them once 2.6.10 is out.

Yesterday I had a problem with 2.6.10, IPSEC and connection tracking, 
please see:

  http://lists.netfilter.org/pipermail/netfilter/2005-January/057751.html

Thanks to Michael Mueller's hint on the netfilter list, Patricks 
McHardy's patches and Ronald Moesbergen's adaption to Kernel 2.6.9 I was 
able to build my own working patches against 2.6.10. Please find them 
attached and consider it as my small participation (and my excuse for 
breaking in :-) .

Please not that someone changed xfrm_policy_get_afinfo() and 
xfrm_policy_put_afinfo() to static somewhere between 2.6.9 and 2.6.10, 
so I had to "resurrect" them. Works for me, review probably necessary.

In retrospect the topic is kind of problematic. At least this one:

  http://www.guninski.com/where_do_you_want_billg_to_go_today_2.html

itches me to run 2.6.10. With a plain 2.6.x kernel I can't, because 
connection tracking and IPSEC together is well known as NoGo. My own 
knowledge of kernel hacking can only be considered improvable, so my 
private patch is a risk as well as running <= 2.6.9.
Fscking lost, huh? :-)

I would love to hear the ipsec-nat patches will make it into 2.6.11.

Kind Regards,
              Robert

P.S.: Some minutes ago I found Ronald Moesbergen's patches for 2.6.10 on 
the list. No competition intended.


[-- Attachment #2: NEED_REVIEW_netfilter-ipsec-patches-linux-2.6.10.tar.gz --]
[-- Type: application/octet-stream, Size: 7231 bytes --]

      reply	other threads:[~2005-01-05  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25  8:19 [Patch] ipsec-nat patches for 2.6.9 Ronald Moesbergen
2004-12-14 18:47 ` Tom Eastep
2004-12-14 21:31   ` Patrick McHardy
2005-01-05  1:11     ` Robert Dahlem [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=41DB3EDD.4050403@gmx.net \
    --to=robert.dahlem@gmx.net \
    --cc=Ronald.Moesbergen@bkvision.nl \
    --cc=kaber@trash.net \
    --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.