Bug #3794
closedRe-orderable IPsec
0%
Description
Allow IPSec tunnel order to be changed much like Firewall Rules can be re-ordered. The purpose is to give one tunnel priority over another in cases where you have overlapping subnets. For example you need 192.168.100.0/24 to go to destination A and 192.168.0.0/16 to go to destination B. Currently you have to delete all tunnels and re-create them in the proper order so the /24 is listed before the /16. I would expect this to work the same as static routes or at least have the option to manual tweaking the routing. The option that seems to work is deleting the /16 VPN and adding in the /24 get it working then adding back in the /16 network. Resulting in downtime and a lot of extra work.
Thanks
Robert
Updated by Robert Middleswarth about 9 years ago
Issue was fixed in 2.2 why marked as rejected?
Thanks
Robert
Updated by Jim Pingle about 9 years ago
- Status changed from Rejected to Duplicate
As mentioned in a previous comment on this ticket, it was rejected because it was a duplicate of #3328.