But, if it is allowed for Linux, why not leverage the same technique in Windows? Configuration walkthrough Would we be able to do the same with a NIC team in a Windows Server guest virtual machine? Well, yes! It sounds like a dirty hack inspired by Linux bonding, which might be way beyond anything resembling a supported configuration. In Ubuntu, you can set a chosen static MAC address on a bond and on the member interfaces inside the guest operating system. Setting a static MAC address on a guest NIC team in Hyper-V During failover, it will swap to the other one. As such, this does not require NIC spoofing. That is why we need MAC spoofing enabled on both member vNIC in the Hyper-V settings for this to work! In a Windows guest, you will find that the MAC address for the LBFO team gets one of the MAC addresses of its member vNICs assigned.
It does not take one of the MAC addresses of the member vNICs. On Ubuntu (or Linux in general), the bond interface has a generated MAC address assigned. Only then will you have network connectivity and are you able to get a DHCP address. Ubuntu network bondĪs you have read by now in the blog post I linked to above, we need to enable MAC Spoofing on both vNICs members of an interface bond in Ubuntu virtual machine on Hyper-V. Do you remember my blog post about configuring an interface bond in a Ubuntu Hyper-V guest? If not, please read it as what I did there got me thinking about setting a static MAC address on a guest NIC team in Hyper-V. Before we talk about setting a static MAC address on a guest NIC team in Hyper-V.
0 kommentar(er)
