Bug #2201
Picking interface subnet in IPsec for an interface with no IP generates invalid racoon.conf
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
02/13/2012
Due date:
% Done:
0%
Estimated time:
Affected Version:
2.0
Affected Architecture:
Release Notes:
Default
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.
Associated revisions
Reject an interface without a subnet as a network source in the IPsec Phase 2 GUI. Fixes ticket #2201
Don't let an empty subnet into racoon.conf, it can cause parse errors. Ticket #2201
Reject an interface without a subnet as a network source in the IPsec Phase 2 GUI. Fixes ticket #2201
History
#1
Updated by Jim Pingle about 9 years ago
Updated by - Status changed from New to Feedback
#2
Updated by Jim Pingle over 8 years ago
- Status changed from Feedback to Resolved
Don't let an empty subnet into racoon.conf, it can cause parse errors. Ticket #2201