| Summary: | incomplete policy for loopback when using *protoport=X/Y | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ken Reilly <kreilly> |
| Component: | openswan | Assignee: | Avesh Agarwal <avagarwa> |
| Status: | CLOSED ERRATA | QA Contact: | Aleš Mareček <amarecek> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.1 | CC: | amarecek, avagarwa, ebenes, eparis, herbert.xu, iboverma, jwest, omoris, pm-eus, sgrubb |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openswan-2_6_32-4_el6_1.1 | Doc Type: | Bug Fix |
| Doc Text: |
IPsec connections over a loopback interface did not work properly when a specific port was configured. This was because incomplete IPsec policies were being set up, leading to connection failures. This update fixes this issue, and complete policies are now correctly established.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-19 21:26:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 711975 | ||
| Bug Blocks: | |||
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0961.html |
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: IPsec connections over a loopback interface did not work properly when a specific port was configured. This was because incomplete IPsec policies were being set up, leading to connection failures. This update fixes this issue, and complete policies are now correctly established.