Project

General

Profile

Actions
Copy link

Bug #3872

closed

Enabling a disabled VLAN subinterface with multiple CARP VIPs configured causes system crash

Added by Stuart Ridsdale almost 11 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/19/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.x
Affected Architecture:
All

Description

When tagged VLAN interfaces have multiple CARP VIPs configured, disabling the interface via the GUI and then enabling causes the system to crash (sometimes the crash does not occur but this has been rare).

This was initially observed on an embedded hardware appliance running the embedded Nanobsd 2G 386 image running 2.1.3. Issue persisted on 2.1.5. (Crash experienced on multiple hardware appliances)

Further testing was done on the 2.1.5 Virtualbox VM running amd64 and the problem was also experienced here.

Attached is the copy of the test configuration that was used on the amd64 2.1.5 Virtualbox installation. In brief:

WAN interface - untagged on em0 with 2 CARP VIPs configured. Disable/enable does not cause crash.
VLAN2_em0 interface - tagged with VLAN id 2 on em0 with two CARP VIPs configured. Disable/enable causes crash.
EM2_Untagged interface - untagged on em2 with 2 CARP VIPs configured. Disable/enable does not cause crash.
VLAN4_em2 interface - tagged with VLAN id 4 on em2 with 1 CARP VIP configured. Disable/enable does not cause crash.
VLAN5_em2 interface - tagged with VLAN id 5 on em2 with 2 CARP VIPs configured. Disable/enable causes crash.

The only other configuration on this device that was not default was an IP address on the LAN interface over which the testing was carried out.

I have attached a couple of examples of the crash reports.

Files

Download all files
vip_crash_config.xml (18.2 KB) vip_crash_config.xml Test config Stuart Ridsdale, 09/19/2014 07:25 AM
crash_reports.txt (3.58 MB) crash_reports.txt Crash reports Stuart Ridsdale, 09/19/2014 07:25 AM
crash_reportstest_config.txt (119 KB) crash_reportstest_config.txt crash reports from test config. Previous showed issue but from a different config Stuart Ridsdale, 09/19/2014 08:14 AM
Actions
Copy link
 #1

Updated by Ermal Luçi almost 11 years ago

You have tried if you recieve this problem on 2.2?

Actions
Copy link
 #2

Updated by Ermal Luçi almost 11 years ago

So to understand even more.
You say the vips are on the VLAN interfaces and you disable the vlan interface, right?
This configuration gives you crashes?

Actions
Copy link
 #4

Updated by Stuart Ridsdale almost 11 years ago

Hi,
No, I have not tried this in 2.2.

Yes, the VIPs are on the VLAN interfaces. I then disable the VLAN interface with the VIPS configured on it, no problem. Then enable the the interface and when clicking 'apply' the firewall crashes.

Actions
Copy link
 #5

Updated by Stuart Ridsdale almost 11 years ago

Sorry, just to reiterate this only happens when two or more CARP VIPs are configured on the VLAN interfaces.

Actions
Copy link
 #6

Updated by Chris Buechler about 10 years ago

  • Status changed from New to Resolved
  • Affected Version set to 2.1.x

I created a config matching Stuart's description, and could easily replicate the panic after disabling and enabling an interface on 2.1.5. Upgraded system to 2.2.2 and it's no longer replicable. This was fixed probably in FreeBSD 10.1 or possibly something we changed in our code in 2.2.x.

Actions
Copy link

Also available in: Atom PDF