Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Problem with combination different types of connections.
ipsec.conf look like this:
conn testA
auto=add
authby=secret
type=transport
left=127.0.0.1
right=127.0.0.1
ike=3des-sha1
phase2=esp
loopback=yes
conn testB
auto=add
authby=secret
type=passthrough
left=127.0.0.1
right=127.0.0.1
ike=3des-sha1
leftprotoport=tcp/10000
loopback=yes
It is important the order of calling ipsec auto --route testA and ipsec auto
--route testB commands.
1. If ipsec auto --route testB called first and then ipsec auto --route testA,
the behaviour is as I expecting (packets on port 10000 are without ipsec)
2. But if I call ipsec auto --route testA first and then ipsec auto --route
testB (stricter rule). All packets are with ipsec (on port 10000 too).
I am not sure that it is a bug or expected behaviour, but records in ip xfrm
policy are same in both cases and in manual pages isn't describe that the order
of calling ipsec auto --route is important.
Comment 1RHEL Program Management
2012-05-03 05:11:17 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 2RHEL Program Management
2012-09-28 14:11:18 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Problem with combination different types of connections. ipsec.conf look like this: conn testA auto=add authby=secret type=transport left=127.0.0.1 right=127.0.0.1 ike=3des-sha1 phase2=esp loopback=yes conn testB auto=add authby=secret type=passthrough left=127.0.0.1 right=127.0.0.1 ike=3des-sha1 leftprotoport=tcp/10000 loopback=yes It is important the order of calling ipsec auto --route testA and ipsec auto --route testB commands. 1. If ipsec auto --route testB called first and then ipsec auto --route testA, the behaviour is as I expecting (packets on port 10000 are without ipsec) 2. But if I call ipsec auto --route testA first and then ipsec auto --route testB (stricter rule). All packets are with ipsec (on port 10000 too). I am not sure that it is a bug or expected behaviour, but records in ip xfrm policy are same in both cases and in manual pages isn't describe that the order of calling ipsec auto --route is important.