Feature #3329: Allow creating "not" rules for IPsec Phase 2 - pfSense - pfSense bugtracker

Actions

Copy link

Feature #3329

closed

Allow creating "not" rules for IPsec Phase 2

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

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

IPsec

Target version:

2.5.0

Start date:

11/19/2013

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Description

We should have the ability in Phase 2 to negate the action ("none" in the SPD) so that specific traffic can be made to not enter an IPsec tunnel.

Somewhat related to #3328 (reordering P2 entries) so these exceptions can be moved above the other entries as needed.

These entries would not need to have any encryption options chosen, only the networks defined.

Files

shunt.png (21.9 KB) shunt.png

Markus Stockhausen, 07/28/2017 02:20 PM

Actions

Copy link

Updated by Jim Thompson over 10 years ago

Assignee set to Renato Botelho

Actions

Copy link

Updated by Ermal Luçi over 10 years ago

Now these should be called specifc policies.

Since phase2 is totally managed by the ipsec daemon there can be what is called shunt policies.
I am not sure where to put these on the GUI at this moment though!

Actions

Copy link

Updated by Chris Buechler about 10 years ago

Target version deleted (~~2.2~~)

not important for 2.2

Actions

Copy link

Updated by Markus Stockhausen over 7 years ago

This feature wil be really helpful. Lets assume a office firewall connected to a HQ firewall. It serves sub multiple small subnets via different interfaces. Lets assumes these are 10.11.12.0/24 (LAN) and 10.20.30.0/24 (OPT1). To build a working routing one would need tens of SAs and build them around the subnets.

A simple implementation could be a single checkbox for each SA. If it is set the local SA part will create a shunt entry in ipsec.conf

Actions

Copy link

Updated by Markus Stockhausen over 7 years ago

File shunt.png shunt.png added

Example implementation

Actions

Copy link

Updated by NCATS LAB over 6 years ago

Strongly Request feature.

We just lost a lot of time because this isn't implemented on SG-4860s.

On our REMOTE SG-4860, we has set up bridging for OPT1-OPT4 and couldn't figure out why everything worked to the GATEWAY except testing the DEF GW with PING.

System should be flexible enough to allow IPSEC tunnels on any interface without some background rule that only makes exceptions on LAN.

Thank-you

Actions

Copy link