Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 83716

Summary: IPSec unable to start
Product: [Retired] Red Hat Linux Reporter: Dave Sherman <dsherman>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-06 00:48:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Dave Sherman 2003-02-07 15:03:42 UTC
Description of problem:
IPSec appears to be either missing or disabled in the latest kernel update
(2.4.18-24.8.0). I can no longer create a VPN tunnel to my office, as the ipsec
service is unable to start.

Version-Release number of selected component (if applicable):
2.4.18-24.8.0

How reproducible:
[root@dedannshae root] # service ipsec start
ipsec_setup: Starting FreeS/WAN IPsec 1.99...
ipsec_setup: insmod: ipsec: no module by that name found
ipsec_setup: modprobe: Can't locate module ipsec
ipsec_setup: kernel appears to lack KLIPS
ipsec_setup: OOPS, should have aborted!  Broken shell!

If I boot into the previous kernel, ipsec start fine and I have my VPN working.

Steps to Reproduce:
1. See above.
2.
3.
    
Actual results:
See terminal output above.

Expected results:
Standard IPSec startup messages and VPN functionality.

Additional info:

Comment 1 Arjan van de Ven 2003-02-07 15:21:21 UTC
Red Hat Linux kernels haven't ever included IPSec support.
We're looking at it for a future release, however past kernels have never
included it. 

Comment 2 Dave Sherman 2003-02-07 15:26:54 UTC
OK, then apparently the latest kernel broke the freeswan kernel module. My
freeswan version is:
freeswan-module-1.99_2.4.18_19.8.0-0
freeswan-1.99_2.4.18_19.8.0-0

Can this bug be moved over to the kernel module maintainer, or whoever takes
care of this?

Comment 3 Arjan van de Ven 2003-02-07 15:29:59 UTC
we don't ship those freeswan modules...
You need to recompile them for the latest kernel to work. if you have a .src.rpm
somewhere of them you can do that by rpmbuild --rebuild --target i686 <foo>.src.rpm

Comment 4 Dave Sherman 2003-02-07 15:34:22 UTC
Ah. OK, thanks for the help. I'll check freeswan.org first, as I originally got
binary rpms from there (I think - I had thought they came with RH 8.0, but
apparently not :-) ).

Comment 5 Bill Nottingham 2003-06-06 00:48:11 UTC
Closing, not a RH bug.