Bug 87107

Summary: Boot process will not complete with IPSEC enabled and no ipsec.conf file
Product: Base System Reporter: Ken Diliberto <ken>
Component: kernAssignee: Remko Lodder <remko>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Ken Diliberto 2005-10-08 05:40:10 UTC 
After compiling IPSEC into the kernel and installing the new kernel, the system will ask which shell to use if ipsec_enable="YES" and the /etc/ipsec.conf file does not exist when the system is rebooted.

How-To-Repeat: Boot the system with IPSEC enabled and no ipsec.conf file.
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2006-12-25 14:31:45 UTC 
State Changed
From-To: open->closed

This is not true, data will just not be encrypted if the ipsec.conf is not 
there (since the gw does not know the encryption domain of the remote host 
so to say). You probably had an " too much somewhere, causing a broken /etc/rc.conf 
which results in the behaviour you are seeing. 

Since i am fairly confident this is the case i will close the PR. If I am wrong 
(yes ofcourse I can be wrong ;-)) please poke me and I will look together with the 
submitter how we can resolve this.
Comment 2 Remko Lodder freebsd_committer freebsd_triage 2006-12-25 14:31:45 UTC 
Responsible Changed
From-To: freebsd-bugs->remko

grab the PR to get the feedback.