[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/36870 (FAST_IPSEC cannot handle optional SA -> busy loop)
The following reply was made to PR kern/36870; it has been noted by GNATS.
From: Wolfgang Stukenbrock <Wolfgang.Stukenbrock%nagler-company.com@localhost>
To: gnats-bugs%NetBSD.org@localhost, degroote%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost,
Subject: Re: kern/36870 (FAST_IPSEC cannot handle optional SA -> busy loop)
Date: Fri, 08 Aug 2008 14:55:45 +0200
it took a long time, but now I've had some time and a machine to test it ...
Sorry for the long delay, but I've had a lot of other trouble here ...
I've retrieved a complete current version, compile and install it on an
The problem seems to be fixed. No problem occurred anymore.
Please pull up the fix into the next possible release.
Thanks in advance.
PS. While settup up the test, I was wondering a little bit, that in no
kernel config of the current version the FAST_IPSEC option is included
or even introduced in a comment. Also only in very few kernel setups
IPSEC is enabled - e.g. in no amd64 config at all.
Does nobody else use it?
> Hi to all,
> I've had a look at the diffs and they look OK compared to the version
> actually running on our machines.
> We are running a modified version of the FAST_IPSEC code in the
> NetBSD4.0 Release in a productive manner here, so it is not possible to
> just take the new implementation (or some fixes) and try it. (This
> report was not the only misbehaviour of the FAST_IPSEC code.)
> I will adapt the changes as soon as I can do into our source base, but
> this may take some weeks, because I'm very busy at the moment.
> If this is OK, I come back to you when I've finished testing.
> Best regards
> W. Stukenbrock
> Zitat von degroote%NetBSD.org@localhost:
>> Synopsis: FAST_IPSEC cannot handle optional SA -> busy loop
>> State-Changed-From-To: open->feedback
>> State-Changed-By: degroote%NetBSD.org@localhost
>> State-Changed-When: Sat, 03 May 2008 21:55:55 +0000
>> A fix has been commited. Can you confirm that it solves your issue ?
Main Index |
Thread Index |