ClearFoundation Tracker - ClearCenter
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012421ClearCenterapp-static-vpn-basic - Static VPN for Homepublic2017-01-16 10:252017-01-16 12:37
Reporterdloper 
Assigned To 
PrioritylowSeveritytweakReproducibilityhave not tried
StatusconfirmedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0012421: Static VPN has bad validation for remote subnet
DescriptionRemote and local subnets require RFC1918 addressing for LAN addresses. This is typical but it is out of spec since IPSec should be able to work behind firewalls that use Public IP addresses for LAN addresses.

Proper validation should be for normalized IPv4 addresses instead. Perhaps a popup that is warning the user that they are using public IP addresses for the LAN network should be better implemented.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0012431confirmed  Static VPN has bad validation for remote subnet 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-01-16 10:25dloperNew Issue
2017-01-16 12:35user2ProjectClearOS => ClearCenter
2017-01-16 12:35user2Categoryapp-ipsec - IPsec Engine => General
2017-01-16 12:36user2Statusnew => confirmed
2017-01-16 12:36user2CategoryGeneral => app-static-vpn-basic - Static VPN for Home
2017-01-16 12:36user2Product Version7.3.0 Beta 1 =>
2017-01-16 12:36user2SummaryStatic IPSec for Business has bad validation for remote subnet => Static VPN has bad validation for remote subnet
2017-01-16 12:36user2Target Version7.3.0 Updates =>
2017-01-16 12:37user2Issue cloned: 0012431
2017-01-16 12:37user2Relationship addedrelated to 0012431

There are no notes attached to this issue.