Actions
Bug #7553
openCaptive portal on a parent interface blocks traffic on VLAN interfaces too
Status:
Confirmed
Priority:
Very Low
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
05/17/2017
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
Description
Using PfSense 2.3.4, I enabled a captive portal on interface em2. Then, as I needed another interface, I added a tagged VLAN on the same switch port, and created a VLAN interface using em2 as parent (em2_vlan55). Took me a while to understand that the captive portal is blocking the VLAN traffic. IMHO this should not be the case. A parent and a VLAN interface should be considered independent.
Actions