Actions
Bug #2394
closedIPsec keepalive doesn't work with 0.0.0.0/0 local subnet
Start date:
04/23/2012
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
Description
When you have a keepalive IP defined in a phase 2 that uses 0.0.0.0/0 (everything) as the local network, the logic that populates /var/db/ipsecpinghosts fails and it doesn't add anything to that file, so it doesn't send those pings. Probably should just pick the LAN IP in that case, or really it can pick any IP, since anything matches in that instance.
Updated by Ermal Luçi about 12 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset b0bf6bd017e27f6d8161fe8fff0ba8e6a71f96a3.
Updated by Chris Buechler over 11 years ago
- Status changed from Feedback to Resolved
Actions