Connections dropped when Backup Firewall is restarted in CARP cluster

Started by ruffy91, March 25, 2019, 08:33:41 AM

Previous topic - Next topic
Our client PCs have connection problems when in a CARP cluster the Backup node is restarted.
I think the problem is related to https://github.com/opnsense/core/issues/3197 and this issue has not been fully understood and resolved.

I can see following in the log of the Master when restarting the Backup:
Mar 25 08:23:57   opnsense: /usr/local/etc/rc.newwanip: On (IP address: 172.16.0.2) (interface: PFSYNC[opt5]) (real interface: igb5).
Mar 25 08:23:57   opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb5'
Mar 25 08:23:57   opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for PFSYNC(opt5) but ignoring since interface is configured with static IP (172.16.0.2 ::)
Mar 25 08:23:57   kernel: igb5: link state changed to UP
Mar 25 08:23:53   opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for PFSYNC(opt5) but ignoring since interface is configured with static IP (172.16.0.2 ::)
Mar 25 08:23:53   kernel: igb5: link state changed to DOWN
Mar 25 08:22:04   opnsense: /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface PFSYNC.
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv4 default route
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: ROUTING: no IPv6 default gateway set, assuming wan
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt5'
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: On (IP address: 172.16.0.2) (interface: PFSYNC[opt5]) (real interface: igb5).
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb5'
Mar 25 08:22:03   opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for PFSYNC(opt5) but ignoring since interface is configured with static IP (172.16.0.2 ::)
Mar 25 08:22:03   kernel: igb5: link state changed to UP
Mar 25 08:21:59   opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for PFSYNC(opt5) but ignoring since interface is configured with static IP (172.16.0.2 ::)
Mar 25 08:21:59   kernel: igb5: link state changed to DOWN

So the dedicated PFSYNC interface is going down and up again as expected, but it is also calling rc.newwanip which causes connection problems on client PCs.

Does anyone have the same problem in this configuration?
(VIP on LAN and WAN + dedicated direct PFSYNC connection)