I do notice in 24.11, the LAN interface and LAN subnet are having a different link number:

192.168.6.0/24 link#21 U lagg0.4091 192.168.6.1 link#16 UHS lo0

You can see link#21 vs link#16.

I don't have a 24.03 anymore, but on my other 22.05, the link numbers are same:

10.147.10.0/24 link#20 U lagg0.40 10.147.10.1 link#20 UHS lo0

Could this impact how ipsec policy does the route selection?

@viragomann Yes, I think so too.

Thanks for the anwser @keyser

I checked here that the "Split connections" option just appear with IKEv2 only, in my case the IPsec configuration is working with IKEv1. So I will need to try this out of the company working hour.

About creating IPsec tunnel from A to C, it has a few reasons, one is that the site B is the main core so we centralized all the configuration there, and to be honest my real scenario have more than 3 spokes so create a lot of new IPsec tunnels on site A will transform this firewall in a second core.

Anyway, thanks for the help, I will read more about it and try enable this option to check if works.

The issue was related to the port 8080 rule on the Juniper device. After making the adjustment, access was granted, and everything worked perfectly.
Thank you!

@oscar-pulgarin
Maybe the logs give hints on what is going wrong. Check both sites.

@Decepticon Thanks for the reply. This is an IPSec VPN, and I use the gateway monitoring for multi-wan failover. The IPSec gateways don't show in that section but do think it has something with a route not advertising.

OpenVPN can be configured for smartphone use and set up to access a NAS at home or what have you.

I thought I'd post what I did and what solved my problem. I can now see (access) the remote shares on all computers. The two computers that I could not reach by entering \\local computer IP address in Windows Explorer were both updated to the latest 24H2 version of Windows 11 Pro. I couldn't figure out how to create custom firewall rules on these computers. So instead, I went to Settings>Privacy & Security>Windows Security>Firewall & Network Protection>Allow an app through firewall. In the list of apps "File and Printer Sharing" was already checked for a private network. But there was also listed "File and Printer Sharing (Restrictive)" that was not checked. That entry is not present on version 23H2 of Windows 11 Pro. I checked the private network option, and now I can reach the network shares on both computers using \\local computer IP address in Windows Explorer.

I thought this might be helpful if others have the same issue with a site to site IPsec VPN.

Hi,
you may try do reboot the pfsense, the routing table is sometimes a little bit weird.

@TheWaterbug
If it's a policy-based IPSec there is no possibility to route certain hosts over it, you would only be able to route all upstream traffic over the VPN.
If it's a VTI you can do this.

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

@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...