Bug #8100: pfsync Initially Deletes States on Primary for Connections Established through Secondary - pfSense - pfSense bugtracker

Actions

Copy link

Bug #8100

open

pfsync Initially Deletes States on Primary for Connections Established through Secondary

Added by Chris Linstruth about 7 years ago. Updated almost 3 years ago.

Status:

New

Priority:

Normal

Assignee:

Luiz Souza

Category:

CARP

Target version:

CE-Next

Start date:

11/15/2017

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

Affected Architecture:

Description

Steps to duplicate:

Create a typical HA pair.
Enter Persistent CARP Maintenance Mode on Primary to initiate a fail over.
Establish a new TCP session. Was tested here with a long scp transfer to an outside server from an inside host.
Observe states created on both nodes with traffic going through Secondary.
Leave Persistent CARP Maintenance Mode on Primary, initiating fail back.
Observe states deleted from Primary but still exist on Secondary. Traffic in TCP session stalls.
Enter Persistent CARP Maintenance Mode on Primary to initiate a fail over. Wait for TCP session to start passing traffic again.
Observe states recreated on Primary.
Fail back and fail over again at will. States will now persist until closed.

Condition does not exist if states are initially established while Primary is the CARP MASTER.

Tested with latest 2.4.2 snapshots.

Files

Download all files

pfsync-primary.cap (1.88 MB) pfsync-primary.cap		Chris Linstruth, 11/15/2017 04:20 PM
pfsync-secondary.cap (1.9 MB) pfsync-secondary.cap		Chris Linstruth, 11/15/2017 04:20 PM