Project

General

Profile

Bug #6295

Crash upon applying CODELQ to untagged parent interface when also applied to daughter VLAN

Added by Jan Olbrecht over 4 years ago. Updated 12 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Limiters
Target version:
-
Start date:
05/01/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3
Affected Architecture:

Description

On a single NIC system / VM using VLANs pfsense 2.3 crashes and can no longer reboot to a functional state when CODELQ is applied to the untagged parent interface while also being applied to a VLAN daughter interface.

eth0 (untagged) = LAN
eth0 (vlan 2) = WAN

1. Apply CodelQ to WAN
2. Apply CodelQ to LAN

pfSense crashes.

I ran into this when upgrading from 2.2.6 on an Intel NUC system and have reproduced it in a Hyper-V machine.

History

#1 Updated by Michael Knowles over 4 years ago

I can confirm I have been fighting this issue too today, but with a dual (actually a triple) NIC ESXi host.

In my case I had the untagged parent interface on the LAN NIC and created a VLAN on there also, and the end result of a few instances of trying this was that pfsense crashed and was no longer bootable, either hanging on preparing the VLAN interface or kernel panicking during boot and getting into a boot loop. I can confirm that both 2.3 and 2.3_1 exhibited the issue.

#2 Updated by Luiz Souza about 4 years ago

  • Assignee set to Luiz Souza

#3 Updated by Shaun Maher over 2 years ago

Hi all.

Just a heads up that this issue still exists in 2.4.2 (amd64).

Cheers.
Shaun.

#4 Updated by Jim Pingle 12 months ago

  • Category changed from Traffic Shaper (ALTQ) to Limiters

Also available in: Atom PDF