Bug #4933
closed
Vlan interfaces created in web ui show up in ifconfig but don't show up in the UI.
0%
Description
I have two pfSense firewalls running CARP and pfSync. em0 is the WAN interface, em1 is LAN, em2 is unused, and em3 is a dedicated interface for pfSync. em1 currently has 5 VLANS that are working as expected. Traffic from these VLANS is filtered using floating rules and run through a captive portal.
If I attempt to create another VLAN on ANY interface on either firewall, the interface shows up in ifconfig from the CLI but does not show up in the "Interfaces -> VLANS" page or the "Interfaces -> assign" page. It cannot be assigned an IP from the web UI in this state.
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Feedback
- Affected Version deleted (
2.2.4)
where/how are you creating them? this all works of course, it's widely used.
Updated by Ben Kuhn almost 10 years ago
Yeah, I have this working in other builds. That's why I'm thinking it's a bug.
I'm creating the vlans through the web interface. Interfaces -> Assign, click on VLAN tab. Click the "+" to add one. Choose the interface (em1.) Enter the VLAN ID (505.) Enter a description ("Vendor Wireless".) Click Apply.
As soon as I click "Apply" the VLAN interface shows up in ifconfig but it's not there in either the VLANs tab or the interface assignment tab where I can assign it an IP.
Are there any configs or logs I can grab? I'm not seeing anything in the system logs when this happens.
Updated by Ben Kuhn almost 10 years ago
Here is a screencast of the behavior: https://youtu.be/MwF_AyR5_ck
Updated by Chris Buechler over 9 years ago
it doesn't show up for assignment because it doesn't show in the VLANs list there. no idea how that could happen, there would be a huge number of people reporting issues if it were a replicable issue as shown. What config changes do you have under Diag>Backup/restore, Config History tab for that change? What does the <vlans> to </vlans> part of your config look like?
Updated by Ben Kuhn over 9 years ago
Well, I went to try to reproduce the problem again and now the vlan is showing up. Weird. Well, this can be closed for now.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Not a Bug
Ok thanks. If you come up with a means of replicating, please report back.