Bug #2201: Picking interface subnet in IPsec for an interface with no IP generates invalid racoon.conf - pfSense - pfSense bugtracker

Actions

Copy link

Bug #2201

closed

Picking interface subnet in IPsec for an interface with no IP generates invalid racoon.conf

Added by Chris Buechler almost 13 years ago. Updated over 12 years ago.

Status:

Resolved

Priority:

Low

Assignee:

Category:

IPsec

Target version:

Start date:

02/13/2012

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

If you pick an interface subnet in an IPsec P2 that has no IP, it generates an invalid racoon.conf. Input validation should prohibit picking the subnet on an interface that doesn't have a subnet on vpn_ipsec_phase2.php.

Also may want to skip that entirely in racoon.conf and log an error, in case someone changes an interface later from having an IP to none. Or prohibit changing an interface to type "none" if its subnet is used in any IPsec P2.