Project

General

Profile

Bug #9207

Phase1s created before pfSense 2.1.0 no longer work after upgrade to 2.4.3: IPsec ERROR: Could not find phase 1 source for connection [redacted]. Omitting from configuration file.

Added by Louis Sautier 12 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
IPsec
Target version:
Start date:
12/18/2018
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.4_1
Affected Architecture:
All

Description

Hi,
Before e79b24ab3534ac2af7d832038155a99902bc2c49, a phase1 did not have a protocol attribute. This a problem since d1f69741f57f9f049f80040a93278591c424a4cc because the attribute is now required.
Logs now show the following:

/vpn_ipsec.php: IPsec ERROR: Could not find phase 1 source for connection [redacted]. Omitting from configuration file.

Since this commit first appeared in 2.4.3, could something be added to the upgrade_178_to_179 function to add a protocol attribute with a value of inet to all phase1s that don't have one?

Associated revisions

Revision d188b725 (diff)
Added by Jim Pingle 12 months ago

Ensure IPsec P1 entries have a 'protocol' value. Fixes #9207

Revision b0220979 (diff)
Added by Jim Pingle 12 months ago

Ensure IPsec P1 entries have a 'protocol' value. Fixes #9207

(cherry picked from commit d188b7251a83b4a8a39ba50dfaf9a1cba35cad17)

History

#1 Updated by Jim Pingle 12 months ago

  • Assignee set to Jim Pingle
  • Target version set to 48

It would be better in a new upgrade code function, but that is certainly possible.

In the mean time, a simple edit/save of the P1 should put the protocol in place.

#2 Updated by Jim Pingle 12 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#3 Updated by Louis Sautier 12 months ago

Looks good to me, thanks for the quick fix!

#4 Updated by Jim Pingle 9 months ago

  • Target version changed from 48 to 2.5.0

#5 Updated by Jim Pingle 7 months ago

  • Target version changed from 2.5.0 to 2.4.4-p3

#6 Updated by Chris Linstruth 7 months ago

2.4.4-p3

Restored an 18.9 configuration with protocol intentionally removed. The configuration was updated to 19.1 and the protocol attribute was added back.

#7 Updated by Jim Pingle 7 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF