Bug 833910

Summary: openswan doesn't recognize the loopback option
Product: Red Hat Enterprise Linux 7 Reporter: Aleš Mareček <amarecek>
Component: openswanAssignee: Avesh Agarwal <avagarwa>
Status: CLOSED CURRENTRELEASE QA Contact: Aleš Mareček <amarecek>
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: eparis, jrieden, omoris, sforsber, sgrubb
Target Milestone: beta   
Target Release: 7.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openswan-2.6.38-10.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1028369 (view as bug list) Environment:
Last Closed: 2013-11-08 10:01:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 717785, 1028369    

Description Aleš Mareček 2012-06-20 14:11:44 UTC
Description of problem:
It seems that openswan doesn't recognize option "loopback" in RHEL-7.
$ service ipsec start
failed to start openswan IKE daemon - the following error occured:
can not load config '/etc/ipsec.conf': /etc/ipsec.conf:17: syntax error, unexpected STRING [loopback]
$ head -17 /etc/ipsec.conf | tail -1
        loopback=yes


Version-Release number of selected component (if applicable):
openswan-2.6.37-3.el7

How reproducible:
Always

Steps to Reproduce:
1. Run the beaker test: /CoreOS/openswan/Regression/bz711975-incomplete-policy-for-loopback-when-using
NOTE: There is also ipsec.conf included
  
Actual results:
FAIL

Expected results:
PASS (loopback option work in RHEL-6)

Additional info:

Comment 5 Avesh Agarwal 2012-12-10 20:39:36 UTC
This has been fixed in openswan-2.6.38-10.el7.

Comment 6 Aleš Mareček 2013-02-08 10:10:21 UTC
I can confirm the issue has dissappeared with openswan-2.6.38-10.el7 (tested on x86_64 and ppc64).

Comment 7 Ondrej Moriš 2013-05-27 08:53:35 UTC
I will retest this issue on the latest RHEL7.

Comment 10 Eric Paris 2013-11-07 17:15:32 UTC
moving this from openswan to libreswan (as we aren't shipping 'openswan' in rhel7)   Paul, you should be able to attach this bug directly to the errata.