Okay, so I took a pot shot at @adam-ierymenko and told him Bridging should be easier... It turns out it is, lol. I blame Microsoft!
Hyper-V has some security features that prevent the system from communicating on the network using a Mac Address that wasn't assigned to it via Hyper-V... There's a fix for that!
In PowerShell, on the Hyper-V host, run the following (it should be typed all on one line... I broke it up for readability)...
*note: This enables the Mac spoofing on ALL NICS attached to the VM.
get-vmnetworkadapter -VMName MYVMNAME|where {$_.SwitchName -eq "MY_HYPERV_SWITCH"}|
set-vmnetworkadapter -MacAddressSpoofing on
Edit: In VMware, you will need to enable Forged Transmits and Promiscuous Mode on the VM that you run things like this on. I don't have access to a VMware system to chek this.