"
I am in process of revamping my home wifi setup and for that project i am setting up opnsense.
In quite a few posts in the forum but also across other pages i found one issue being discussed that i had issues with my self as well.
Adding vmxnet adapters to opnsense will scramble the order of detected interfaces in freebsd and the reason for this is how vmware tries balancing PCI devices across interfaces. The only work around i found so far to fix the issue is by using a less capable (dum) e1000 interface type instead of vmxnet adatpers but at least that way i can control the interface order and make sure they go to the right portgroup and therefore get the correct VLAN assigned.
Cudos to Matt's blog for pointing me to the right direction: https://matt.dinham.net/interface-ordering-vmware/
He's discussing this for a juniper device that sees the same issue, so opnsense is not the only solution being affected by the problem.
I must admit that i have also changed the vm settings from automatic mac address assignment to manual as i hope i know what i am doing and chose a reserved OUI range and made sure i've got a consecutive and numerical incrementing mac address scheme just to be extra sure it's in proper order.
That's all for now, just wanted to share my sucess as i was strugling a bit to get this problem solved.
Hopefully this is useful to someone else and perhaps even triggers a dev to figure out the issue from an OS level that so that we're able to leverage all creature comforts from a modern vmxnet interface.
Cheers,
PS
In quite a few posts in the forum but also across other pages i found one issue being discussed that i had issues with my self as well.
Adding vmxnet adapters to opnsense will scramble the order of detected interfaces in freebsd and the reason for this is how vmware tries balancing PCI devices across interfaces. The only work around i found so far to fix the issue is by using a less capable (dum) e1000 interface type instead of vmxnet adatpers but at least that way i can control the interface order and make sure they go to the right portgroup and therefore get the correct VLAN assigned.
Cudos to Matt's blog for pointing me to the right direction: https://matt.dinham.net/interface-ordering-vmware/
He's discussing this for a juniper device that sees the same issue, so opnsense is not the only solution being affected by the problem.
I must admit that i have also changed the vm settings from automatic mac address assignment to manual as i hope i know what i am doing and chose a reserved OUI range and made sure i've got a consecutive and numerical incrementing mac address scheme just to be extra sure it's in proper order.
That's all for now, just wanted to share my sucess as i was strugling a bit to get this problem solved.
Hopefully this is useful to someone else and perhaps even triggers a dev to figure out the issue from an OS level that so that we're able to leverage all creature comforts from a modern vmxnet interface.
Cheers,
PS
