Project

General

Profile

Actions

Bug #3980

closed

wrong static routes added for remote P2 subnets

Added by Chris Buechler over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Category:
IPsec
Target version:
Start date:
11/03/2014
Due date:
% Done:

0%

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

Description

A static route for the remote network of every P2 is added in 2.2, pointing to WAN's gateway IP. I'm guessing the intent was to try to add it to the LAN IP, to force proper source IP selection, the way people manually add static routes now. But it points to the wrong place, and will break people's user-defined static routes that are correct.

There are enough changes in behavior in IPsec without this, let's not add routes at all for 2.2.

Actions #1

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Confirmed

actually it's strongswan itself doing this, looking at where/why.

Actions #2

Updated by Chris Buechler over 9 years ago

  • Status changed from Confirmed to Feedback
  • Assignee set to Chris Buechler

looks to be fixed, leaving for further confirmation

Actions #3

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved

fixed

Actions

Also available in: Atom PDF