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.
Bug 1564977 - Initiator does not reply after establishing ipsec sa with esn=yes
Summary: Initiator does not reply after establishing ipsec sa with esn=yes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.5-Alt
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-09 05:29 UTC by Wei Chen
Modified: 2018-08-22 09:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-22 09:02:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Paul Wouters 2018-04-10 11:16:37 UTC 
wireshark shows:

06:29:44.186298 IP6 fe80::200:10ff:fe10:1060 > ff02::1: ICMP6, router advertisement, length 48
06:29:52.275013 IP6 3000::215:17ff:fe37:13cd.isakmp > 3001::200:10ff:fe10:1180.isakmp: isakmp: parent_sa ikev2_init[I]
06:29:52.275068 IP6 3001::200:10ff:fe10:1180 > 3000::215:17ff:fe37:13cd: ICMP6, destination unreachable, unreachable port, 3001::200:10ff:fe10:1180 udp port isakmp, length 364
06:29:52.311652 IP6 3001::200:10ff:fe10:1180.isakmp > 3000::215:17ff:fe37:13cd.isakmp: isakmp: parent_sa ikev2_init[R]
06:29:52.315238 IP6 3000::215:17ff:fe37:13cd.isakmp > 3001::200:10ff:fe10:1180.isakmp: isakmp: child_sa  ikev2_auth[I]
06:29:52.315280 IP6 3001::200:10ff:fe10:1180 > 3000::215:17ff:fe37:13cd: ICMP6, destination unreachable, unreachable port, 3001::200:10ff:fe10:1180 udp port isakmp, length 308
06:29:52.348028 IP6 3001::200:10ff:fe10:1180.isakmp > 3000::215:17ff:fe37:13cd.isakmp: isakmp: child_sa  ikev2_auth[R]
06:29:53.507980 IP6 3001::200:10ff:fe10:1180 > 3000::215:17ff:fe37:13cd: ESP(spi=0xa09d654e,seq=0x1), length 44
06:29:57.333008 IP6 fe80::215:17ff:fe71:2ec3 > 3000::215:17ff:fe37:13cd: ICMP6, neighbor solicitation, who has 3000::215:17ff:fe37:13cd, length 32
06:29:57.333266 IP6 3000::215:17ff:fe37:13cd > fe80::215:17ff:fe71:2ec3: ICMP6, neighbor advertisement, tgt is 3000::215:17ff:fe37:13cd, length 24
06:29:57.334243 IP6 fe80::215:17ff:fe37:13cd > 3001::200:10ff:fe10:1180: ICMP6, neighbor solicitation, who has 3001::200:10ff:fe10:1180, length 32
[...]

This does not seem related to ESN at all. It seems more related to our builtin exception that ensures v6 neighbour discovery happens in the clear
Note You need to log in before you can comment on or make changes to this bug.