Hubert Feyrer
2009-06-25 09:48:25 UTC
I wonder what the status of our FAST_IPSEC implementation is.
It's not (even) commented-out in i386/GENERIC, and the manpage
also has a few holes (no sysctls listed, etc.)
Does anyone use FAST_IPSEC? Successfully? Possibly with
hardware accelerated cryptography?
FWIW, enabling it in the kernel gets me a lot of
ipsecpol: done, sp 0x0 error 0,
spewed on the console. The patch below reduces this somewhat.
Does anyone want to commit this?
- Hubert
Index: ipsec.c
===================================================================
RCS file: /cvsroot/src/sys/netipsec/ipsec.c,v
retrieving revision 1.39
diff -u -r1.39 ipsec.c
--- ipsec.c 27 Jun 2008 17:28:24 -0000 1.39
+++ ipsec.c 25 Jun 2009 09:45:41 -0000
@@ -727,7 +727,7 @@
KEY_FREESP(&sp);
sp = NULL;
}
- DPRINTF(("ipsecpol: done, sp %p error %d, \n", sp, *error));
+ if (sp != NULL || *error != 0) DPRINTF(("ipsecpol: done, sp %p error %d, \n", sp, *error));
return sp;
}
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
It's not (even) commented-out in i386/GENERIC, and the manpage
also has a few holes (no sysctls listed, etc.)
Does anyone use FAST_IPSEC? Successfully? Possibly with
hardware accelerated cryptography?
FWIW, enabling it in the kernel gets me a lot of
ipsecpol: done, sp 0x0 error 0,
spewed on the console. The patch below reduces this somewhat.
Does anyone want to commit this?
- Hubert
Index: ipsec.c
===================================================================
RCS file: /cvsroot/src/sys/netipsec/ipsec.c,v
retrieving revision 1.39
diff -u -r1.39 ipsec.c
--- ipsec.c 27 Jun 2008 17:28:24 -0000 1.39
+++ ipsec.c 25 Jun 2009 09:45:41 -0000
@@ -727,7 +727,7 @@
KEY_FREESP(&sp);
sp = NULL;
}
- DPRINTF(("ipsecpol: done, sp %p error %d, \n", sp, *error));
+ if (sp != NULL || *error != 0) DPRINTF(("ipsecpol: done, sp %p error %d, \n", sp, *error));
return sp;
}
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de