>>I have the console output now, it crashed the very first time this time
>>around. Another difference is that the values as printed seem ok now.
>>Pid 176 would be raccoon, I expect.
>	my wild guess is that you are running two copies of racoon daemon by
>	mistake.

	sorry, i checked your original posting.  could you check where the
	kernel code is returning EINVAL in UPDATE message handling?  it should
	be somewhere inside sys/netkey/*.c (some printfs should do it).
	http://mail-index.netbsd.org/port-vax/2002/06/21/0000.html

itojun