IPSEC NAT Problem
jom last edited by
I am trying to port an existing ASTARO configuration to pfsense. That's the desired Setup:
192.168.0.0/24 (NAT to 172.17.22.155) <-> 184.108.40.206/16 (that's a faked IP)
In ASTARO there is a SNAT rule to do the NAT from 192.168.0.0/24 to 172.17.22.155, the tunnel is defined by
172.17.22.155/29 <-> 220.127.116.11/16
With pfSense the tunnel comes up with defining the phase2 connection by 172.17.22.155/29 <-> 18.104.22.168/16, WITHOUT NAT/BINAT.
As soon as I define the phase2 setup like 192.168.0.0/24 (NAT to 172.17.22.155/29) <-> 22.214.171.124/16 the tunnel fails and I have the following problems:
- pfsense complains that the networks 192.168.0.0/24 and 172.17.22.155/29 do not fit
- even if I change the setup to be 192.168.0.0/29 (NAT to 172.17.22.155/29) <-> 126.96.36.199/16 the tunnel will not come up
- defining the setup like 192.168.0.0/24 (NAT to 172.17.22.155) <-> 188.8.131.52/16 makes the tunnel not come up
I assume that ASTARO does the NATing before evaluating the IPSEC tunnel and pfsense does not. Is there a way to NAT the traffic to 184.108.40.206/16 before it hits the IPSEC tunnel?
What options do I have?
eri-- last edited by
Normally you should provide the log of what is going wrong.
From ipsec side of things this does not matter at all.
As soon in pfSense you define the natting the other side will not see the private ips at all.
So it does not matter how you express policies of NAT here since the other side will not look ever at that.
Its just some parameters do not match there and that is what the log will express hence the need for it.