https://redmine.pfsense.org/issues/12468

The 1 step was to push this config to clients, so the packet on VPN ipse is routed inside the Open VPN tunnel

alt text

Under local networks there are :

Lan,
the remote net identified in phase2 n.1
the remote net identified in phase2 n.2

You can't do that with policy-based tunnels.

You have two choices:

Keep the policy-based tunnels and setup Dynamic DNS and gateway groups on both sides so that if a WAN fails, the switches the hostname and single IPsec tunnel to the other WAN. This works, but takes a long time to switch since it relies on DNS (several minutes, most likely) Ditch the policy-based tunnels and use VTI. Configure two tunnels (1.1.1.1<->3.3.3.3, 2.2.2.2<->4.4.4.4) and use FRR with either OSPF or BGP to handle the routing. When setup properly, dynamic routing protocols are smart enough to detect when a path is down and use the other alternate path in a timely manner.

Strange i had to add a rule tha is not generating any traffic.

alt text

it is not generating any traffic but a big amount of evaluation.

I'll try later to disable it.

Other params are ok.

Thanks for your message. I still have this problem, and can't find a solution for it. The only "fix" I found is downgrading to 2.5.1, then it works immediately again :-/

I am actually not using the native Windows 10 client, but the Shrewsoft VPN client on Windows. On iOS I use the native iOS client.

This quote you found in the StrongSwan documentation, is that only since the version that is used in pfSense 2.5.2 ?

In the end I switched over to WireGuard - smashing it in around 6-8 MB/s. Tried everything with IPSec but gave up. I think I might have to investiage Wireguard further and switch the other VPNS over too.. The WireGuard seems to really forgiving of the StarLink latency/dropped packets.

Here is a file copy from a remote server to local along with 20x robocopy in the background doing file compares (no actual transfers)

FC.JPG wg.JPG

@bp81 I believe we have found the resolution, and I wanted to post it here for anyone else encountering the issue.

In our DNS forwarder, we had a domain override set for our company's domain. This is the same domain in the hostname for the remote gateway listed above. The domain override was pointing at a DNS server that is not accessible without the tunnel up. Clearly this was causing the IPSec service to fail repeatedly to establish its tunnel.

So there was a misconfiguration on our part which we have fixed. I still maintain that it's a bug if the ipsec service causes the web gui to crash / become unresponsive even when it's a self induced failure state due to misconfiguration. I understand it's possible this may be a limitation of the ipsec service, but it is worth looking at even if it is an edge case.

Bonjour,
je rencontre actuellement le meme probleme entre un pfsense et un fortinet. J'ai appliqué les propositions de gerdesj (hormis le reboot coté fortinet).
Pour le moment le probleme persiste.
Si quelqu'un a une idée.
Merci

Hello,
I currently encounter the same problem between a pfsense and a fortinet. I applied the proposals of gerdesj (apart from the reboot on the fortinet side).
For the moment the problem persists.
If someone has an idea.
Thank you

Oct 11 09:46:30 charon 55488 06[NET] <con100000|1> sending packet: from 10.10.10.254[500] to 84.14.183.243[500] (336 bytes)
Oct 11 09:46:30 charon 55488 06[IKE] <con100000|1> retransmit 1 of request with message ID 0
Oct 11 09:46:30 charon 55488 06[CFG] ignoring acquire, connection attempt pending
Oct 11 09:46:30 charon 55488 06[KNL] creating acquire job for policy 10.10.10.254/32|/0 === 84.14.183.243/32|/0 with reqid {1}
Oct 11 09:46:29 charon 55488 06[CFG] ignoring acquire, connection attempt pending
Oct 11 09:46:29 charon 55488 06[KNL] creating acquire job for policy 10.10.10.254/32|/0 === 84.14.183.243/32|/0 with reqid {1}
Oct 11 09:46:28 charon 55488 07[CFG] vici client 2 disconnected
Oct 11 09:46:28 charon 55488 07[CFG] vici client 2 requests: list-sas
Oct 11 09:46:28 charon 55488 07[CFG] vici client 2 registered for: list-sa
Oct 11 09:46:28 charon 55488 07[CFG] vici client 2 connected
Oct 11 09:46:26 charon 55488 06[NET] <con100000|1> sending packet: from 10.10.10.254[500] to 84.14.183.243[500] (336 bytes)
Oct 11 09:46:26 charon 55488 06[ENC] <con100000|1> generating IKE_SA_INIT request 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) N(FRAG_SUP) N(HASH_ALG) N(REDIR_SUP) ]
Oct 11 09:46:26 charon 55488 06[CFG] <con100000|1> sending supported signature hash algorithms: sha256 sha384 sha512 identity
Oct 11 09:46:26 charon 55488 06[CFG] <con100000|1> configured proposals: IKE:AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
Oct 11 09:46:26 charon 55488 06[IKE] <con100000|1> IKE_SA con100000[1] state change: CREATED => CONNECTING

This was solved by missing GW on WAN interfaces

Ah, didn't spot this yesterday when I looked

https://redmine.pfsense.org/issues/11910

This can be considered solved I think.

Just for the record. Just loaded the cert onto a Yubikey 5 hardware smartcard. Same error/result.

@mmapplebeck Hello.
Have you solved the reconnection issue?
I have updated Pfsense to version 2.5.2. I have check and confirm all data from site A to site B. I have reduce the time to reconnected and that aliave some trouble but not fix it. Too I have enable and set MSS to 1400.
Every day one of my tunnels is blocked. It doesn't seem to renegotiate the connection well. After terminate one of the Phase 1 zombie connections, the communication is reset.
Also another tunnel connection fails time to time and I have to disable it for any of the Phase 2 to work again.

@elvisimprsntr The router is a TP-Link load balancer that does the connection to the ISP, I tried The Port Forwarding UDP/TCP 500 (Virtual Servers) to the pfsense IP Address but same issue...

Your pre-shared key does not exactly match the key at the far side.

https://docs.netgate.com/pfsense/en/latest/troubleshooting/ipsec.html#phase-1-pre-shared-key-mismatch

If it works sometimes and not others, it may be that it only works when initiating in one direction. It could still be a problem with the key, but perhaps something more subtle like an extra space at the start/end that is ignored when checking on one side but not the other.

@michelz said in High CPU load (100% on one core) when enabling Phase 1:

Disable properly means IPSec won't need it and won't have these errors in the log?

Correct. When disabled with the patch, references to that daemon and/or its services are not present in the IPsec configuration, so the errors will not happen.

@keyser Updated: It actually works if your IPsec is running in tunnelmode and you make sure to resolve the vpn endpoint name to the public IP on the WAN interface, from the inside as well :-)

@jimp Great, thanks for the hint. I was thinking the right direction, but missed the setting. I look more thoroughly again and found it.

@djohnson
This is a late reply but it may assist someone else in future.
The VOIP audio traffic (RTP) require separate UDP ports to be open. The exact range will vary depending on your VoIP system.

Hence, if the RTP ports are not open, you can experience a "working" system, but with a complete lack of audio.

This looks indeed not possible to do.
Post may be locked.

@jimp Thanks to! Changed to TLS Web Server certificate, error disappeared.

anyone?

That could definitely be a problem if there are two running. I'm not sure how that might happen, though.

Is it actually two and not just two threads or a worker of some kind?

This is normal:

root 35995 0.0 0.2 10752 1696 - Is 15:38 0:00.00 daemon: /usr/local/libexec/ipsec/charon[36322] (daemon) root 36322 0.0 2.0 51140 19356 - I 15:38 1:07.25 /usr/local/libexec/ipsec/charon --use-syslog

But if you see multiples of either of those then it could be the source of the problem.

There could be some kind of an odd timing issue where it's getting started twice, a race condition that depends on other environmental factors that may vary.

Might need to comb through the logs for both of those PIDs and then check other logs for entries around the time when the second PID started. See if there was anything logged in the system log, gateway log, etc.