Project

General

Profile

Actions

Bug #15930

open

Mobile IPsec clients can't connect after gateway failover

Added by Danilo Zrenjanin 19 days ago. Updated 12 days ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:

Description

If a gateway group is defined and selected as the Interface in the IPsec setup, connections will function properly while the primary gateway is operational. However, when the primary gateway fails and the secondary gateway takes over, mobile IPsec clients are unable to connect to the backup WAN until the IPsec service is manually stopped and restarted.

Following the gateway failover:

The file located at /var/etc/ipsec/strongswan.conf correctly reflects the backup WAN interface with interfaces_use = ix2.
The configuration file at /var/etc/ipsec/swanctl.conf accurately displays the local ID as local_addrs = 192.168.99.10.
Packet capture confirms that packets are arriving on the backup WAN interface.
Nevertheless, the Status > System Logs > IPsec section does not display any logs related to incoming connection attempts, and the client reports that there was no response on the server side.

Restarting the IPsec service on the firewall allows clients to seamlessly connect to the backup WAN without any issues.

The issue described at https://redmine.pfsense.org/issues/15685 may be related; however, the local_addrs parameter is now accurate.


Related issues

Related to Bug #15685: Mobile IPsec does not automatically switch to failover gatewayResolvedMarcos M

Actions
Actions

Also available in: Atom PDF