Marco Berizzi <[EMAIL PROTECTED]> wrote:
>
> Is this bug recently introduced? I'm using this
> config since 2.6.16/openswan 2.4.4 (two years).
> I haven't never noticed: now I must restart openswan
> once a day :-(
No it's been there forever but I haven't worked out exactly
what triggers it yet or
Herbert Xu wrote:
> Marco Berizzi <[EMAIL PROTECTED]> wrote:
> > Hello everybody.
> > I'm experimenting a pretty strange ipsec problem with 2.6.23.x
> > and openswan 2.4.11
> > Here is the output from 'ip -s x p':
>
> It's a bug in openswan but I haven't had the time to track it
> down yet.
Is th
Marco Berizzi <[EMAIL PROTECTED]> wrote:
> Hello everybody.
> I'm experimenting a pretty strange ipsec problem with 2.6.23.x
> and openswan 2.4.11
> Here is the output from 'ip -s x p':
It's a bug in openswan but I haven't had the time to track it
down yet. Anyway, the kernel is not involved sinc
Hello everybody.
I'm experimenting a pretty strange ipsec problem with 2.6.23.x
and openswan 2.4.11
Here is the output from 'ip -s x p':
src 172.16.0.0/23 dst 192.168.15.2/32 uid 0
dir out action allow index 529 priority 2368 ptype main share
any flag 0x00
00
lifetime config:
