Project

General

Profile

Actions

Bug #2818

closed

IPSec phase2 "Automatically ping host" function broken. Bug confirmed.

Added by Dan Lundqvist about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
Start date:
02/14/2013
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
All

Description

Tested on: 2.1-BETA1 (i386) built on Sun Feb 10 22:04:57 EST 2013
plus small manual correction from gitsync regarding "link down".
Also have not seen any checkins related to this kind of problem in build between 10-15 Feb.

The IPSec phase2 "Automatically ping host" does not work for IPv4 configured phase 2 tunnels.

Some investigation ruled that the root cause is that the "/var/db/ipsecpinghosts" and "/var/db/currentipsecpinghosts"
does not get populated with IPv4 entries even if they are defined in the IPSec phase2 settings.

I have also tried to clear / apply / reconfigure / apply with recent build but same result.
Only the IPv6 entries is stored.

Which will have the result that NO IPv4 tunnels will have any AutoPing running.

I have confirmed both with printouts of the files above and also verified by doing PacketCapture that only
IPv6 pings are getting through which corresponds to what I see in the ipsecpinghosts and currentipsecpinghosts.

I will remove some uniqe details in my IP to protect and replace with xxx (local) and yyy (remote).

[2.1-BETA1][]/var/db(3): cat ipsecpinghosts
2001:470:28:xxx::1|2001:470:28:yyy::1|3|||||inet6|

[2.1-BETA1][]/var/db(4): cat currentipsecpinghosts
2001:470:28:xxx::1|2001:470:28:yyy::1|3|||||inet6|

Also see attached config.xml for section: IPSec, Interfaces, Gateways.

Best regards
Dan Lundqvist
Stockholm Sweden


Files

Actions

Also available in: Atom PDF