Crash upon applying CODELQ to untagged parent interface when also applied to daughter VLAN
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
I ran into this when upgrading from 2.2.6 on an Intel NUC system and have reproduced it in a Hyper-V machine.
#1 Updated by Michael Knowles about 5 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.