Feature #893
closed
Re-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 believe the same is true with static routes. I have not tested it yet but it would be useful to able to do the same thing.
Updated by Chris Buechler about 14 years ago
- Project changed from pfSense Packages to pfSense
Updated by Chris Buechler about 14 years ago
- Subject changed from Re-orderable IPSec/Static Routes to Re-orderable IPsec
- Category set to IPsec
- Target version set to Future
that's not true of static routes, order has nothing to do with routes, most specific matching route wins.
Updated by Robert Middleswarth over 10 years ago
This is going on 4 year now. Running in the same problem again. Unlike static routes IPsec routes are done by the order they are in. How hard would it be to include an up / down arrow like it is in the firewall rules.
Thanks
Robert
Updated by Jim Pingle over 10 years ago
- Status changed from New to Closed
Duplicate of #3328 (It's newer but already properly assigned and targeted)