Project

General

Profile

Actions
Copy link

Bug #3297

closed

IPsec log parsing code does not skip disabled Phase 1 entries

Added by Jim Pingle about 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ermal Luçi
Category:
Logging
Target version:
2.2
Start date:
10/30/2013
Due date:
% Done:

40%

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

Description

The IPsec log parsing code does not skip disabled Phase 1 entries, however, that may be OK but needs consideration.

If you have multiple tunnels to the same remote IP (e.g. one on WAN1, one on WAN2) if you disable the WAN1 entry, when the WAN2 tunnel connects it shows the description from the WAN1 tunnel.

However, if no second/overlapping entry is present, it is still useful to see the disabled tunnel description for diagnostic purposes.

Perhaps the code needs some extra logic to somehow use a disabled entry only if no overlapping entry is present?

Actions
Copy link
 #1

Updated by Ermal Luçi almost 11 years ago

  • % Done changed from 0 to 40

Now you can identify the related logs with the connection name.
So this should be a less of an issue.

The page of logs needs updating related to this.

Actions
Copy link
 #2

Updated by Jim Thompson over 10 years ago

  • Assignee set to Ermal Luçi
Actions
Copy link
 #3

Updated by Ermal Luçi over 10 years ago

  • Status changed from New to Closed

I do not think this is an issue anymore!

Since the connection name is in the logs.

Actions
Copy link

Also available in: Atom PDF