My 2022 server says LFBO is deprecated, but I unlocked it with: New-VMSwitch -Name "LAN" -NetAdapterName "LINK-AGGREGATION" -AllowNetLbfoTeams $true -AllowManagementOS $true Seems to work, adapter is in Hyper-V
I've been struggling with this for a couple of weeks. I'm a network guy and somewhat know what I am doing. Not to brag but to skip any basics stuff like questions regarding if the firewall might be Blocking it or anything. I absolutely have not been able to get this to work pass get vlan tagged traffic to reach the host machine like you are showing. There are also a few blogposts which detail how to do this. It flat out is not working on Windows11Pro and I have tried everything and it is frustrating! I used to do this with Intel Proset tools which is now gone. I am trying this on the same exact adaptor you show in the video. - - - --- set to Access VlanXX.. Host machine cannot pass traffic to or from the virtual interface. I am testing with the same I226-V (similar) ethernet adaptor you show in the video. All of the posts say this works. I have been unable to get this to work! They also mention using -Passthru
If your physical ports are trunked to already allow VLAN 3 on the trunk, why create a VM Network adapter for the -ManagementOS just to be able to tag the VM's VM network adapter with VLAN 3? Unless you want the ManagementOS to "talk" on VLAN 3 as well, this was not necessary as all you had to do was to just tag the VM's network adapter with VLAN 3 if it was part of the trunk. Just curious.
can u help me please, I am trying to learn to configure, with a VLAN topology, which uses a virtual Mikrotik router with VLAN settings. example as picture. can I ask for your email to send the topology image. thanks
He knows well, just that SET is targeted for different purpose, SET is for integrating separate NICs for single use whereas LFBO is for dividing single adapter into more virtual adapters. SET is also possible to use for it, but is very awkward.
I set up 5 VLANS, but cant get the routing to work well. It seems to use all virtual network adapters to communicate out. A gateway is needed for intervlan routing, but if i put one in windows os gets all messed up and seems to send out random gateways. I tried removing the gateways and manually creating routes but lost connection then… not sure how it should be set up
My 2022 server says LFBO is deprecated, but I unlocked it with: New-VMSwitch -Name "LAN" -NetAdapterName "LINK-AGGREGATION" -AllowNetLbfoTeams $true -AllowManagementOS $true
Seems to work, adapter is in Hyper-V
I've been struggling with this for a couple of weeks. I'm a network guy and somewhat know what I am doing. Not to brag but to skip any basics stuff like questions regarding if the firewall might be Blocking it or anything.
I absolutely have not been able to get this to work pass get vlan tagged traffic to reach the host machine like you are showing. There are also a few blogposts which detail how to do this.
It flat out is not working on Windows11Pro and I have tried everything and it is frustrating!
I used to do this with Intel Proset tools which is now gone.
I am trying this on the same exact adaptor you show in the video.
- - - --- set to Access VlanXX.. Host machine cannot pass traffic to or from the virtual interface.
I am testing with the same I226-V (similar) ethernet adaptor you show in the video. All of the posts say this works. I have been unable to get this to work!
They also mention using -Passthru
If your physical ports are trunked to already allow VLAN 3 on the trunk, why create a VM Network adapter for the -ManagementOS just to be able to tag the VM's VM network adapter with VLAN 3? Unless you want the ManagementOS to "talk" on VLAN 3 as well, this was not necessary as all you had to do was to just tag the VM's network adapter with VLAN 3 if it was part of the trunk. Just curious.
15:08 you mean via the gui of that vm, right?
Like you did on 08:20?
Yes
can u help me please, I am trying to learn to configure, with a VLAN topology, which uses a virtual Mikrotik router with VLAN settings.
example as picture.
can I ask for your email to send the topology image.
thanks
not even you know what you were speking about
He knows well, just that SET is targeted for different purpose, SET is for integrating separate NICs for single use whereas LFBO is for dividing single adapter into more virtual adapters. SET is also possible to use for it, but is very awkward.
I set up 5 VLANS, but cant get the routing to work well. It seems to use all virtual network adapters to communicate out. A gateway is needed for intervlan routing, but if i put one in windows os gets all messed up and seems to send out random gateways. I tried removing the gateways and manually creating routes but lost connection then… not sure how it should be set up