Bug 150553 – RHEL4 ipsec configuration (network to network)

Bug 150553 - RHEL4 ipsec configuration (network to network)

Summary:	RHEL4 ipsec configuration (network to network)

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Web Site
Classification:	Red Hat
Component:	Documentation (Show other bugs)
Sub Component:
Version:	current
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	John Ha
QA Contact:	John Ha
Docs Contact:

URL:	http://www.redhat.com/docs/manuals/en...
Whiteboard:
Keywords:	Documentation

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-08 04:10 EST by Steven Whitehouse
Modified:	2014-08-04 18:15 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-03-17 13:25:29 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Steven Whitehouse 2005-03-08 04:10:11 EST

Description of problem:

The above URL suggests two configuration parameters SRCGW and DSTGW,
however these two are never used in
/etc/sysconfig/network-scripts/ifup-ipsec

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

RHEL4

Comment 2 Bill Nottingham 2005-03-15 16:48:04 EST

They shouldn't be necessary, no. SRCGW may be needed for setting a
route, but it can be automatically computed.

Comment 3 John Ha 2005-03-17 13:25:29 EST

Thanks for the info, Bill.

Apparently, the fields are optional (though, puzzlingly, they are required
fields in the IPSEC druid in system-config-network).

In any event, the next release of the Red Hat Enterprise Linux Security Guide
will state that these fields are optional.

Thanks for your report.

Note You need to log in before you can comment on or make changes to this bug.