From: Patrick McHardy <kaber@trash.net>
To: Johannes Graumann <graumann@caltech.edu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: patch-o-matic-ng questions and remarks from newbie
Date: Sun, 07 Nov 2004 22:08:07 +0100 [thread overview]
Message-ID: <418E8EB7.8050604@trash.net> (raw)
In-Reply-To: <20041107102832.463003a4@localhost>
Johannes Graumann wrote:
>I'm reposting this in the devel mailing list in the hope to find more of
>an echo than in the 'normal' one ...
>
>Hello,
>
>In order to use my shorewall/2.6 based firewall to route IPSECed
>(openswan) wireless, I need to apply these patches from the
>patch-o-matic-ng (extra):
>1) ipsec-01-output-hooks
>2) ipsec-02-input-hooks
>3) ipsec-03-policy-lookup
>4) ipsec-04-policy-checks
>5) policy
>
>It took me a whole night to figure out that these are only cleanly
>applicable to a 2.6.6 kernel and nothing later - which is ok with me ...
>if I only would have managed to find this information without loading
>down 2.6.9, 2.6.8, 2.6.7 and 2.6.6 source and testing the patch-o-matic
>with every single one of these! Can somebody please help me dummy in
>finding this information? Are these patches expected to get a revamp to
>be capable to cope with 2.6.9?
>
>
Someone recently posted patches for 2.6.9 to this list, please
search the archives.
>On another note: are/when are these features scheduled to go into the
>2.6 series?
>
Very soon hopefully. I'll post my patches for 2.6.10 for discussion
in a couple of days.
Regards
Patrick
next prev parent reply other threads:[~2004-11-07 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 18:28 patch-o-matic-ng questions and remarks from newbie Johannes Graumann
2004-11-07 21:08 ` Patrick McHardy [this message]
2004-11-15 22:13 ` Johannes Graumann
2004-11-15 22:23 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 4:20 Johannes Graumann
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=418E8EB7.8050604@trash.net \
--to=kaber@trash.net \
--cc=graumann@caltech.edu \
--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.