Is Windows "9014" jumbo frame the same as Linux "9000"?

Question

I'm setting up VMs networking using bridges. Whole network is configured using 9000 MTU on Linux machines and Linux bridges and 9116 l2mtu on router (I think Linux doesn't expose this setting via ip command). Now I'm reading about jumbo frames in Windows and I noticed it has dropdown MTU menu so I can't just type whatever I want. "9k" MTU seems to be announced as "9014" bytes. I'd be reaaaally sad if it was actual MTU but then I noticed L2 header is 14B long so I guess it sounds like too big coincidence - so does Windows count MTU like l2mtu in Linux? or real jumbo size in windows is 9014+14 = 9028?...

Answer 1

Today I wanted to know what the Packet Size in Basler GigE Vision camera means. You can set a MTU there which is applied when the image data is transmitted.
The driver of the Intel Network Card in my computer supports Jumbo Frames of 4088 and 9014 bytes, so I wanted to know which value I have to set in the camera to get the maximum frame size.

I cannot give an exact answer on your question, but here's what I found out.
Here's a screenshot of one of the packets with image data when I set the packet size in the camera to 8000 bytes:

(the nice coloring was done with Paint.Net)

As you can see,

• the total packet size is 8014 bytes
• the "Ethernet II" header (pink) has 14 bytes, leaving 8000 bytes for the IP part of the packet.
• the IPv4 header (blue) has 20 bytes
• the UDP header (green) has 8 bytes

For details and a comparison about Standard and Jumbo Frames, have a look at Wikipedia: Jumbo Frame and Wikipedia: Maximum transmission unit.
Notice: Wikipedia mentions a 4 byte FCS (Frame Check Sequence) after the Ethernet header. However, this was not observed in the captured packets.

To answer your question as good as possible: I think that Linux refers to the size of the IP packet while Windows and my Intel driver refers to the size of the whole Ethernet packet.