Feature #946


Allow aliases to be used to define IPsec phase 2 networks

Added by Jim Pingle about 11 years ago. Updated almost 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:


Eventually it would be nice to allow using aliases on the IPsec phase 2 definition screen for local and remote networks. It would be an easy and clean way to avoid having to manually make many entries that are identical except for the subnet definitions.

The GUI code would just need to add the alias autcomplete mechanism to the "Address" field, perhaps either by sharing the "Network" choice in type, so it would be "Network or alias", or use a choice for just "Alias". We might need to restrict it to host and network alias types. The backend would just need to generate the appropriate pairings of phase 2 declarations in racoon.conf, matching each entry in the local alias/network to an entry in the remote alias/network.

Actions #1

Updated by Ermal Luçi about 7 years ago

  • Target version changed from Future to 2.3

This is possible to implement easily now that strongswan is used.

Actions #2

Updated by Jim Thompson almost 7 years ago

  • Assignee set to Ermal Luçi
Actions #3

Updated by Jim Thompson about 6 years ago

  • Assignee changed from Ermal Luçi to Renato Botelho


Actions #4

Updated by Chris Buechler about 6 years ago

  • Target version changed from 2.3 to Future
Actions #5

Updated by Grzegorz Sliwa over 5 years ago

It will be great see it in next release of pfSense.
Today I must create ~100 tunnels phase 2.
I had to create 5 my internal networks to external subnets.... and I must do it one by one.
With aliases I could create alias: my_local_network for example and route it all to external subnets much easier.

Actions #6

Updated by Auric Sosa almost 4 years ago

Has been over 7 year now, it will be good to have that option?

Is there an update on this?


Also available in: Atom PDF