Only again 23 ethernet interfaces managed ?

[Frankisk]

I’m posting my problem here because the last time, the half resolution was came by an update.

In my ancien topic : https://forum.opnsense.org/index.php?topic=26792.0, I had explained that I created an OPNSense VM in a Hyper-V lab server, as a central firewall/router, between VM servers and clients, to control who can access what.

But with more and more server and client additions, the number of ethernet interfaces has also increased, and I found that only the first 23 interfaces are manageable by the OPNSense web interface.

With the update to 22.1.1_3 and the following ones after, the number of interfaces has increased at 32, that is not the maximum of 64 of the version 2 of VM, but who was enough for my platform to now.

But, with the last update to 24.7_9, the quantity downed to 23 like before, that has had break links with some VMs, that make them unable to be used.

I will like to have an correction in the next update to recome the count to 32, and better to arrive at 64.

Thanks for your help.

[Frankisk]

I had upgraded to 2.7.1 and the count stay at 23 operationnal interfaces.

[Patrick M. Hausen]

Creating an issue on github might have a better chance of being seen by the actual developers.

While Franco and friends are quite active here on the platform, this is in no way a direct channel to "the project" but a user forum.

[Monviech (Cedrik)]

Can't Hyper-V create a trunk port like ESXI? In ESXI you could create the vnic with vlan 4095 (VGT Tagging Mode). Then the VM itself could manage its own VLANs with 802.1Q. So you essentially just needed one port for all of your VLANs.