Project

General

Profile

Actions

Bug #910

closed

CARP+Bridging+NAT can lead to "freeze"/"lockup"

Added by Jim Pingle over 13 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
CARP
Target version:
-
Start date:
09/20/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

As reported by a user here http://forum.pfsense.org/index.php/topic,28442.0.html (And experienced by myself last week)

If you have three or more Interfaces in a CARP+Bridging scenario on 1.2.3 or 2.0 it can cause issues, either in general or perhaps only when NAT is involved.

How to reproduce:
  • Add CARP VIPs to WAN
  • NAT LAN to a CARP VIP
  • Bridge OPT1 to WAN

In my case I has CARP on LAN as well, and a sync interface, and a backup unit going. Active unit would stay alive anywhere from 30 seconds to an hour, then lock up tight. The secondary would take over, and then eventually fail. If the primary was immediately rebooted by hand, the backup unit would stay up indefinitely.

When it got hung up, it was not responsive to ping, nor console input. No panic, no reboot, just seized up. One time pressing the power button on the unit did result in the console printing an error that it was not in the proper state to handle the event.

We don't recommend CARP+Bridging anyhow, but it might be nice to know what is going on that makes it lock that severely.

Actions #2

Updated by Ermal Luçi over 13 years ago

  • Status changed from New to Feedback

A patch to fix this issue has been committed.

Actions #3

Updated by Chris Buechler about 12 years ago

  • Status changed from Feedback to Resolved
Actions #4

Updated by Chris Buechler almost 8 years ago

  • Target version deleted (Future)
Actions

Also available in: Atom PDF