Wed Apr 06, 2022 6:57 am
... ok, I've been struggling with this exact issue for the last month or so ... I guess I wasn't expecting to need a _second_ nat rule to do the reverse.
I do have one final question though - which network block needs to be on my local end of the IPSec policy? using the example CIDRs here, would I want the non-NAT block (192.168.2.0/24) or the NAT block (192.168.22.0/24)? I'm assuming we want the policy to match traffic after the NAT rule has taken effect, so the policy should match 192.168.22.0/24 source addresses?
UPDATE - yes, this worked, I now have a functional IPSec tunnel with a policy for 192.168.22.0/24 and NATted traffic traversing it
Last edited by
mjch on Wed Apr 06, 2022 10:40 am, edited 1 time in total.