patch-o-matic-ng questions and remarks from newbie

patch-o-matic-ng questions and remarks from newbie

[Johannes Graumann]

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?
On another note: are/when are these features scheduled to go into the
2.6 series?

Thanks for any hints,

Joh

patch-o-matic-ng questions and remarks from newbie

[Johannes Graumann]

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?
On another note: are/when are these features scheduled to go into the
2.6 series?

Thanks for any hints,

Joh

Re: patch-o-matic-ng questions and remarks from newbie

[Patrick McHardy]

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

Re: patch-o-matic-ng questions and remarks from newbie

[Johannes Graumann]

Thanks,

I found those and have finally managed to get my kernel to compile.
One general question of mine remains unsolved: is there - aside from
trial and error - some way to figure out which patch in the
patch-o-matic-ng plays well with what kernel?

Thanks, Joh

On Sun, 07 Nov 2004 22:08:07 +0100
Patrick McHardy <kaber@trash.net> wrote:

> 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
> 
> 
> 

Re: patch-o-matic-ng questions and remarks from newbie

[Patrick McHardy]

Johannes Graumann wrote:

>Thanks,
>
>I found those and have finally managed to get my kernel to compile.
>One general question of mine remains unsolved: is there - aside from
>trial and error - some way to figure out which patch in the
>patch-o-matic-ng plays well with what kernel?
>
They should have dependencies that are automatically checked,
but usually something like "kernel >= 2.6.7 is used", this of
course doesn't catch future versions that the patch won't work
with anymore.

Regards
Patrick