Sorry, I didn't realise this will create a new thread. Can an admin deleted this please?

@viragomann Thanks! Your reply helped me understand the flow which I was trying to do from the IPSEC and WAN Rules.

Kept the WAN Rules simple and fixed IPSEC Rules and added LAN rule.

Works now! Thank you for a quick educational lesson!!

@viragomann thank you very much it now works.

It was set as "My IP Address" but seems that it don't work when it is not explicitly set.

that setting on server side is not necessary. once we setup the radius server correctly the X509 error messages were gone.

@Gblenn This is strange. I previously simply added a new tunnel and it works. It's been a while since I last did this, maybe about 6 months, and now suddenly this strange behaviour happens.

@jimp Thanks master, I will.

@andmattia
You need also to add a phase 2 on the Cloud -> MyCustomer IPSEC with 172.172.2.0/24 - 192.168.X.X.

BTW: Why are you using public network ranges inside your LAN??

Correction to my previous post: the working iOS 18.1.1 device actually does NOT have LE's CA cert manually imported. (LE is apparently now a trusted a root authority in iOS.)

The VPN configuration profile itself is self-signed however—and it's that signer's CA cert that's manually installed on this working device.

Doubtful that any of this is relevant. Just wanting to clarify. Apologies for any confusion.

@SteveITS Thanks Steve. I did not Disable Auto-added VPN rules. The block ports 500 and 4500 rules I added are being hit and the logs have been quiet, so looks like being at the bottom of the WAN list is okay.

There can be only one mobile P1 at a time. You can either remove the old one and create a new one, or change the settings on the old one to match what you want it to be now.

@reynold Actually you install Avahi as a package on pfsense, not on the windows clients.

@viragomann Hi!
Thanks a lot, ill try and let you know the result

Warm Regards

@johnpoz Correct. CGNAT is being rolled out, so I’m trying to switch anything that might be affected to v6.

@aneeshksurendran9007
If your current phase 2 doesn't cover the OpenVPN tunnel network, you need a second one.
IPSec phase 2 must always be added to both sites.

You can circumvent this, however, by natting the VPN clients access to an unused IP of the existing p2 at the main office.

@user-ng2100 Im also new!!! Nice to know that there's someone like me who are a beginner😁. Btw i dont know the answer, i just wanted to say hi, if i know someome who knows, ill let you know✌🏻

@oscar-pulgarin
Do you have multiple phase 2? If so you have to move this one up.

Do you need access the remote site, or are your only expecting incoming connections?

For incoming traffic add a rule to IPSec.
For connections to the remote site, add rules to the respective incoming interface.

@viragomann Hmm, is that common? I only have two routers in this case that I can test, and they don't do masquerading...

@Gblenn I will have a look at that, I did a bit of reading around that last night, but didn't delv deep enough etc.

Thank you

@Spyderturbo007

Assuming it is a hub and spoke topology:

main site:
first phase 2:
172.16.1.0/24 -> 192.168.50.0/24
172.16.0.0/24 -> 192.168.50.0/24

second phase 2:
172.16.1.0/24 ->172.16.0.0/24
192.168.50.0/24 -> 172.16.0.0/24

site 192.168.50.0/24
192.168.50.0/24 -> 172.16.1.0/24
192.168.50.0/24 -> 172.16.0.0/24

site 172.16.0.0/24
172.16.0.0/24 -> 172.16.1.0/24
172.16.0.0 -> 192.168.50.0/24