Project

General

Profile

Actions
Copy link

Bug #12580

closed

IPsec Status - incorrect match

Added by Georgian Matei almost 4 years ago. Updated almost 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
21.05.1
Affected Architecture:
All

Description

Netgate XG-7100
Serial: 1916200092
Version: 21.05.2-RELEASE (amd64)

If you are using mutliple Routed IPsec tunnels and you upgraded your pfsense you will get an odd issue regarding monitoring matching the vpn connection to the wrong number.
Old Route based vpns used to be named con1000,con2000 etc... after the upgrade the new route based vpn connections created get named con1,con2 etc, this causes the IPsec status monintoring to match connections established by con1 under connections establishewd by con1000, same for con2 getting matched to con2000, it's like the monitoring script is ignoring all the 0's from the name and only matches the first part.
I attached screnshot were con4 is matched under the name for con4000 and con3 is matched under con3000.

Files

Capture.PNG (103 KB) Capture.PNG Georgian Matei, 12/10/2021 04:06 AM
Actions
Copy link
 #1

Updated by Viktor Gurov almost 4 years ago

  • Status changed from New to Duplicate

Duplicate of #11910

Actions
Copy link

Also available in: Atom PDF