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.
DescriptionPatrick Uiterwijk
2014-03-20 00:00:34 UTC
Description of problem:
The tunnel connection seems to break as soon as a DHCP (IPv4) refresh occurs.
Version-Release number of selected component (if applicable):
libreswan-3.8-2.el7
How reproducible:
Fully
Steps to Reproduce:
1. Set up a DHCP server with a very low lease time (in my case, 5 minutes).
2. Connect using libreswan to a gateway that provides a subnet and domain (Red Hat VPN in my case).
3. ping a host in the remote network and in another terminal follow the journal.
Actual results:
As soon as I see the dhcp refresh happening, the connection fails (indicated by the ping no longer working and just waiting for a long time).
Expected results:
I would expect the connection to stay up, and as such the ping not being disrupted.
Additional info:
Interesting. will investigate.
Is this using nm-libreswan? or manual connection?
Comment 3Patrick Uiterwijk
2014-03-20 08:05:31 UTC
This is using a manual connection with "ipsec auto --up redhat" and the configuration files you (Paul) provided to me.
If you need any additional information, just let me know.
The only other thing that I noticed when I compared a route overview before and after the connection drops is that the metric for the "10.0.0.0" subnet increases from 0 to 1.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------
This request was NOT resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you need
to escalate this bug.