Bug 168973

Summary:	No mechanism for configuring road-warrior gateway/client except by hand
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	ipsec-tools	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rvokal, someone, tmraz
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-14 01:52:06 UTC	Type:	---
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:	126912
Bug Blocks:

Description Bill Nottingham 2005-09-21 19:22:49 UTC

+++ This bug was initially created as a clone of Bug #126912 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040623

Description of problem:
It seems that the Redhat ifcfg-ipsec0 config for ipsec-tools can not
be configured as a gateway for ipsec road warriors.

There is a requirement that the remote device be specified on all
tunnels, which is impossible to do in a road warrior config, as there
is no way the ipsec-tools gateway can know in advance what IP
addresses the road warrior will use to connect to the server.

This is a serious limitation to RHEL3, and with the lack of stability
of freeswan is a serious setback to anybody trying to deploy a ipsec
gateway.


Version-Release number of selected component (if applicable):
ipsec-tools-0.2.5-0.4

How reproducible:
Always

Steps to Reproduce:
xxx

Additional info:

-- Additional comment from notting on 2004-06-29 01:17 EST --
AFAIK, this is not possible with ipsec-tools-0.2.x.

-- Additional comment from minfrin on 2004-06-29 06:30 EST --
Not according to http://www.ipsec-howto.org/x247.html.

So far it looks like all docs for ipsec-tools are contradictory, the
Redhat supplied docs are incomplete are quite clearly have never been
tested.

It raises the question of whether ipsec-tools have any business being
inside the RHEL3 distribution in the first place.

Comment 1 John Poelstra 2008-07-08 03:56:21 UTC

Hi Bill,

Is this bug still applicable to rawhide?

John

Comment 2 Bill Nottingham 2011-12-13 19:11:24 UTC

These scripts were moved to ipsec-tools.

Comment 3 Fedora Admin XMLRPC Client 2013-11-13 16:17:15 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Paul Wouters 2013-11-14 01:52:06 UTC

ipsec-tools is not really supported for real deployments in fedora. Please use libreswan instead. ipsec-tools is mostly used for interop testing with libreswan.
ipsec-tools has further been replaced by openswan in rhel6 (and libreswan in rhel7)