Project

General

Profile

Actions

Bug #8565

closed

NAT with IPSec

Added by Fabien DE BIASI over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/12/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I have a configuration described in the Word attached document.
The version of the PFSENSE product is
2.0.1-RELEASE (amd64)
built on Mon Dec 12 18:16:13 EST 2011
FreeBSD 8.1-RELEASE-p6

A remote user built a tunnel from a remote site and shall reach a network via Tunnel and the NAT.
From the remote to the server, the packet is well encrypted within the tunnel and cross the PFSENSE where the NAT runs fine and the IP packet is correctly sent to the server.
When the server answers, the PFSENSE does the NAT, which is fine, but the packet is sent back to the WAN interface instead of the tunnel one. It seems the tunnel rules are not checked after the NAT rules.
Is it a bug of that version, is the configuration wrong somewhere ?
Best regards
Fabien


Files

NAT and IPSec with PFsense.docx (186 KB) NAT and IPSec with PFsense.docx Fabien DE BIASI, 06/12/2018 07:07 AM
Actions

Also available in: Atom PDF