Project

General

Profile

Todo #576

Make sure IPsec upgrade code properly handles mobile clients

Added by Jim Pingle over 9 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Configuration Upgrade
Target version:
Start date:
05/06/2010
Due date:
% Done:

0%

Estimated time:

Description

The IPsec code changes from 1.2.3 to 2.0 are quite large in some areas. Now that it is possible to replicate a 1.2.3-style mobile tunnel configuration (See #108), we need to ensure that the upgrade code handles this scenario gracefully.

History

#1 Updated by Chris Buechler over 9 years ago

  • Category set to Configuration Upgrade
  • Target version set to 2.0
  • Affected Version set to 2.0

#2 Updated by Jim Pingle over 8 years ago

Apparently there are issues here. Just saw a config from a customer that upgraded with mobile tunnels and the upgrade code did not carry over the mobile phase 2 definition. Still needs work.

#3 Updated by Jim Pingle over 8 years ago

  • Status changed from New to Feedback

There was no IPsec mobile client upgrade code at all. I committed some with 49bb5c0 and it seems to work properly for me (after fixing a related IPsec upgrade issue in a5187d4).

#4 Updated by Chris Buechler about 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF