Bug 1105179
Summary: | ipsec_auto --ready doesn't work properly | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Aleš Mareček <amarecek> | ||||
Component: | openswan | Assignee: | Paul Wouters <pwouters> | ||||
Status: | CLOSED ERRATA | QA Contact: | Jaroslav Aster <jaster> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.6 | CC: | eparis, jaster, ksrot | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1105180 (view as bug list) | Environment: | |||||
Last Closed: | 2014-10-14 08:19:36 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1105180 | ||||||
Attachments: |
|
Description
Aleš Mareček
2014-06-05 14:02:50 UTC
ipsec auto --ready does not take a connection name. This is a bug in the man page that states: ipsec auto { --status | --ready } connection (ipsec auto --status also does not take a connection name) It does state so later in the man page: The --ready, --rereadsecrets, --rereadgroups, and --statusoperations do not take a connection name. The displayed usage message is correct in this respect: ipsec auto [--showonly] --{ready|status|rereadsecrets|rereadgroups} The startup of the IKE daemon does allow for that initial gap within the first 1-3 seconds. The pluto daemon starts. It performs setup and when it is ready to be configured shell scripts will call addconn to add connections. This will happen asynchronously in the background as it sometimes needs to start thousands of connections and the service starting cannot block on this operation. What your scripts do is to immediately try to --ready and --up a connection that has not been added to pluto yet by the backgrounded scripts. While we could add a pauze to wait for loading the connections, this causes an unwanted delay when people have thousands of connections loading. There is no reason to wait for the first connections that are loaded to not be available while other connections load. The proper way to start a connection on boot is not your script, but to use auto=start (for connections you want to ipsec auto --up on boot) or auto=route (for connections you want to ipsec auto --route on boot) If you deem it important enough to update this man page entry for 6.6, please let me know. Otherwise, feel free to close this as not-a-bug Hi Paul, at first thank you for quick response! I know about option "auto=start" but this is not a case. From some reason I would want to start my tunnel manually (then auto=add is proper option in config file). Starting tunnel immediately after daemon start is unintentional but it's the same for the output of open/libreswan claiming it doesn't know the connection. What I'm asking is how to know when deamon is ready to accept requests from client (the whole config file parsed)? We can live with "sleep <seconds>" but I'd rather have some check point that daemon is ready to go. Anyway, there are (and I think "will be") errata for openswan in RHEL-6 in the future so the manual page should be fixed at least. Created attachment 902601 [details]
patch for ipsec auto man page and usage text
Patch to fix the usage of the --ready command to show it does not take an argument. It also removes other obsoleted options that were left in the man page related to "acerts" and "aacerts"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1588.html |