Bug 126912
Summary: | Roadwarrior config impossible for ipsec-tools | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Graham Leggett <minfrin> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | rvokal, someone |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-21 19:26:35 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: | |||
Bug Blocks: | 168973 |
Description
Graham Leggett
2004-06-28 23:18:49 UTC
AFAIK, this is not possible with ipsec-tools-0.2.x. 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. Sorry about that, you are correct. With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating changes for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects. As such, changes of this magnitude to the configuration infrastructure for ipsec-tools probably aren't going to be backported to RHEL 3/RHEL 4. This bug has been cloned as a enhancement for a later release. |