IPsec problems: setkey error "invalid keymsg length", racoon spins in busy loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Medium
|
Andy Whitcroft |
Bug Description
Binary package hint: linux-image-
When I upgraded from hardy to intrepid, my IPsec configuration stopped working. The first symptom I noticed was upon boot, racoon was spinning itself in a busy loop, sucking up all of one CPU. After tinkering with setkey trying to edit the running IPsec configuration, I found that setkey would give me the error "invalid keymsg length".
I found http://
I built a kernel from the git tree at kernel.ubuntu.org with this fix, and both setkey and racoon work as intended. I will build a kernel from the same tree without that patch later today to verify that it is indeed the culprit.
Hi Matt,
Thanks for the report and especially the reference to the upstream git commit id. The patch you've referenced is already included in the upcoming Jaunty kernel. I've gone ahead and opened an Intrepid nomination for this to be considered for a Stable Release Update for the Intrepid kernel. Thanks.
ogasawara@ yoji:~/ ubuntu- jaunty$ git log 920da6923cf03c8 a78fbaffa408f8a b37f6abfc1 a78fbaffa408f8a b37f6abfc1
commit 920da6923cf03c8
Author: Alexey Dobriyan <email address hidden>
Date: Fri Oct 31 16:41:26 2008 -0700
key: fix setkey(8) policy set breakage