OPNsense Forum
English Forums => General Discussion => Topic started by: pmladenov on December 07, 2020, 06:44:22 pm
-
Hello,
Today I noticed an annoying "feature" with my virtual lab and physical pre-production setup. Once I add an additional VLAN ID (via webgui - Interfaces -> Other Types -> VLAN) all data traffic using already existing VLANs on the same physical interface is temporary stopping for 2-3 seconds. This happens on a single physical interface as well as LAGG group.
Is that something expected and is there any workaround for preventing it?
(I'm running 20.7.5)
Regards,
Plamen
-
A little bit more on the "feature" - I start believing this is a bug.
I found out why there is a traffic glitch:
When I create a new VLAN on top of the LACP group all physical interfaces (part of the LACP group) flaps.
Moreover adding a new VLAN from the GUI not always works - quite often when I click "Apply" button and nothing happens (there's no error message, everything looks good, but the new vlan is not created, can't be seen from the GUI and I have to start over doing exactly the same in order to have the vlan created).
Apparently that creates operation issues (no one wants to disrupt production traffic over the existing VLANs when tries to add a new VLAN...) My workaround for the moment is to create the vlan on the standby unit first (yes, physical interfaces flaps, but at least there's no prod traffic) and after that to force CARP failover and create the vlan on the new standby unit and force failover again....
I reproduced the same behavior in the virtual LAB (vmware workstation and 20.7.5 running as a VM) as well as several physical Dell VEP devices. Same thing happens even on a single physical interface only without being part of LAGG.
-
For the missing VLAN - I've checked, although VLAN interface is not seen from the GUI (neither from Interfaces -> Other Types -> VLAN, nor under Interfaces -> Assignments) the interface has been created on the BSD level, which of course interrupt again the whole LACP group.
-
Is there any easy way I can run the GUI in debug mode and see all interface related commands (ifconfig ...) parsed to the BSD OS?
-
Do you use Edge Ports at the switch. I know GUI resets connection when adding vlan in the Interface where GUI is, but it's mit 3 seconds. Maybe related to more complex setup
-
Hey,
for the record - i had been trying vlans on top of lacp back in pfsense already and there was an abundance of issues. I had to give up (VLANs no, but on top of LACP, yes).
So, if you would go looking, go looking in ifconfig output as you proceed, and check if flags show up, or do not show up when they should, etc.