-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
rhel-8.3.0
-
None
-
Important
-
rhel-sst-security-crypto
-
ssg_security
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
Description of problem:
If at the service start time there is no default route, later on when a default route is added the service is unable to bring up a connection, showing the error message "We cannot identify ourselves with either end of this connection. XX.XX.XX.XX or 0.0.0.0 are not usable"
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. configure network without a gateway
2. start libreswan
3. add default gateway
4. ipsec auto --up conn
Actual results:
https://access.redhat.com/solutions/3610301
Expected results:
find a way to know there is a default route and automatically bring up connections that are marked `auto` or `route` in the config file
Additional info:
workaround is to write a script to check for this condition and restart libreswan, and install it as a service to monitor libreswan service
strongswan does manage to get itself informed about such changes