[SOLVED] Need help understanding VLAN and parent interface relationship on 23.7

[jorglodita]

Hi! This is a bit technical question and my English is far from perfect, hope I am using the right words but sorry if I make any mistake.

This is about VIRTUALIZED setups and OPNsense. Sorry for the caps but its important.

Until 22.1 we could use VLAN without the parent interface enabled. For example: if I wanted so create the "VLAN 10" over vtnet2 I could just create it and it worked, not needed to have the "vtnet2 interface enabled. Well, to be more precise you could create it after 22.1, but it will badly work.

After 22.1 something changed and now you need to have the parent interface enabled (vtnet2 in this case), then you can create that "VLAN 10" and  it will work perfectly. You had to have unused parent interfaces enables to make VLAN work over them.

I am not blaming OPNsense for this, its made for a reason and that's absolutely OK. Why I am opening a thread then?

Yesterday I was installing 23.7 from scratch on a new computer. In the first setup I was prompted to create VLANs, I said "yes". I created a new VLAN, I choose the desired interface for it (vtnet0) and did continue with the installation, all was perfect.
When I finished and went to the dashboard a big thing surprised me: the VLAN created in the installation was there but...I didn't see the parent interface on the list of enabled interfaces! I double checked, the installed didn't created and enabled the parent interface. I could even create an interface with that parent interface (vtnet0), it was not created on install. Just had the "vlan10_vtnet0" (or something similar) and nothing more, I expected a "vtnet0" parent created and enabled too.

Has something changed related to this between 22.1 and 23.7? We can now create VLAN without enabling their parent interfaces? There is a new option now to bypass this that did not see? Cant understand why this has changed.

Thanks a million in advance!

[Patrick M. Hausen]

After 22.1 something changed and now you need to have the parent interface enabled (vtnet2 in this case), then you can create that "VLAN 10" and  it will work perfectly. You had to have unused parent interfaces enables to make VLAN work over them.

That was reverted in 22.7.4:

Last but not least the "assign VLAN parent and enable" migration note from 22.1 is no longer required as the boot will attempt to configure all existing hardware devices once with the selected defaults.

https://docs.opnsense.org/releases/CE_22.7.html

[jorglodita]

After 22.1 something changed and now you need to have the parent interface enabled (vtnet2 in this case), then you can create that "VLAN 10" and  it will work perfectly. You had to have unused parent interfaces enables to make VLAN work over them.

That was reverted in 22.7.4:

Last but not least the "assign VLAN parent and enable" migration note from 22.1 is no longer required as the boot will attempt to configure all existing hardware devices once with the selected defaults.

https://docs.opnsense.org/releases/CE_22.7.html

All totally cleared and explained, thanks a million for your time!