Tuesday, September 18, 2018

Is Windows10 1803 blocking LLC broadcast over SR-IOV? (HyperV server sees the traffic)

I have an application which communicates with hardware over ethernet using LLC Broadcast (for streaming) and LLC Unicast (for configuration) traffic. When using Unicast traffic the packets pass and the software can communicate with the device, but when trying to listen to the broadcast stream, I get nothing in the VM.

The server can see the traffic, and previous fully-patched versions of Windows10 on the same host can see the Broadcast traffic.

When using the same patch level on ESXI/KVM/VirtualBox VMS, and when running the same patch-level bare-metal, the broadcast stream passes through. This only seems to affect HyperV - I suspect due to some effect related to SR-IOV (since HyperV seems to require SR-IOV to pass LLC traffic.)

Sample broadcast packet as follows (from wireshark on a esxi VM without SR-IOV): 9494 11.524637 AltaSolu_07:00:1f Broadcast LLC 874 I P, N(R)=32, N(S)=38; DSAP 0x40 Group, SSAP ISO Network Layer (OSLAN 2) Command

Is there something some here knows of that I need to look into to re-enable this traffic in a Windows10-1803 VM running under Hyper-V?

Trying Google-fu and other members of the involved org's network teams has yielded nothing so far most likely because this seemingly a rather unique problem.



No comments:

Post a Comment