Wed Jul 21, 2021 7:58 am
I'm on a desktop now with the hyperv network stack installed for native os vlan bridging to various virtual interfaces. VMware Workstation is installed, and binds to the same virutal nics.
With Windows 10, you need to understand that if you're sharing the physical network connection between the host and the virtual machines, there is now a logical/software bridge object between you/userland and the actual wire, even if you don't have any vlans configured.
All vlans and vlan-interfaces are configured using powershell only; there's no gui or netsh interfaces to mange vlans / hyperv networking on Windows 10.
Mikrotk discovery works fine for me either on one of the hyper-v vlan-ed os interfaces to my main nic, or via one of the many usb3 nics i'e used (natively, no hyperv management/integration) for various testing/initial-device-config activities.
If you've got IPv4 and/or IPv6 bound to an interface that's visible from userland, discovery should work over that interface (protocol-specific, v4 for v4, v6 for v6).
It's all working swimmingly for me....
I know this probably wasn't a lot of help. "Works for me" isn't usually the most helpful reply.
However, "it works for most people" is still a valid data point.
What's 'special' and/or 'half-configured' on your system?