Project

General

Profile

Bug #8100

pfsync Initially Deletes States on Primary for Connections Established through Secondary

Added by Chris Linstruth 5 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
CARP
Target version:
Start date:
11/15/2017
Due date:
% Done:

0%

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.

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

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

History

#1 Updated by Chris Linstruth 5 months ago

Attached complete pcaps of sync interfaces.

#2 Updated by Jim Pingle 5 months ago

  • Target version changed from 2.4.2 to 2.4.3

#3 Updated by Steve Beaver 3 months ago

  • Assignee set to Jim Pingle

#4 Updated by Steve Beaver 3 months ago

  • Assignee changed from Jim Pingle to Luiz Souza
  • Target version changed from 2.4.3 to 2.4.4

Also available in: Atom PDF