|
|||||||||||
|
Re: linux-ipsec: Annoying problem with Pluto
From: Richard Guy Briggs <rgb(at)conscoop.ottawa.on.ca>
Date: Fri May 22 1998 - 09:32:39 EDT
If you have the kernel logging on, it should let you know what went wrong...mind you this is out of synch with your output. The other way, I suppose is to do some custom error codes. I don't know how platform independant/hardware independant this can be. > It wasn't clear from your posting, but I am guessing that you ran
The 0.8 release will accept the SA without complaining, properly reclaim the old memory and allocate new and replace the SA. I have just checked in some changes (post-0.8) that will force a deletion of an SA before it will permit the setting of a new one. > Supporting evidence: egrep -ni SPI from Hugh Daniel's message yields
Agreed. > Richard: is there a way in which we (you) can make the errno values
As I said above, there should be some kernel log output if there was a problem, and I don't know yet how easy it will be to return custom error codes from the kernel. There may already be some that might be useful. > This is another reason that SPIs need to come from the kernel. For
Yes, agreed. It is on the TODO list. What is its priority (and all the rest of the items on the TODO)? Also on the TODO is SA expiry and signalling to pluto. > SPIs are generated by Pluto, not the kernel, and fresh copies of Pluto
Yes, especially if that spi was bundled with another. That has also been addressed in some of the post-0.8 commits to the repository.
> Hugh Redelmeier
Slainte Mhath, rgb -----BEGIN PGP SIGNATURE-----
iQCVAwUBNWV+dd+sBuIhFagtAQEe6QP/VLyVi6HpSZnGnN36u1Gl14lG+rAZme3P
moY9ULURBzuPjzsUuaBK1TTBqLTZiQwh3iGZqZQcvt2qo+31I1Y8LL1usZEvhjgW
AKKQuG7SrdB32Y6PrJbChIGE0q9dgB3ZbefACls115G7FUUR1JWjO7P+UNfoNG8+
A/K6HlGjiZU=
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:12 EDT |
||||||||||
|
|||||||||||