@hescominsoon Glad it's working better now. SMB will definitely be slower but should be far more usable.

@XrayDoc88 normally the firewall rules when you enable something only allow the network the device is on.. private and public just modes windows will put the firewall on, if its using the public policy it will block any inbound, etc..

if your remote nettwork is say 192.168.20/24 and your local network is 192.168.10/24 you would go into the rules and allow the 192.168.20 network.. Or for that matter just turn off the firewall on the host.

@RET63
If pfSense is behind a router you have probably to update the identifier on both sites.

If you have changed the ISP router also remember to configure the port forwarding on it.

@pharceface
You want to access the remote site from pfSense itself or access a service on pfSense from remote?
Then you'll need a Static Route Workaround as explained in the docs.

@michmoor said in More than one IPSec tunnel phase1 is fine, but adding another phase1 prevents an existing tunnel from re-establishing a connection:

@jimp nice.
i have been following this out of curiosity. I have been a bit worried about the stability of IPsec on the platform based on my current experience so this has been an interesting post to follow. I would've never thought about the remote id being a problem. Makes sense

Indeed an interesting finding and definitely something to investigate to see if it resolves my issue...

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.