Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
New-VMSwitch command overrides interface's MTU #84
I've been experimenting with containers on Windows Server 2016 and I ran into a problem: somewhere during the container networking setup the MTU of my interface was changed. I think I've narrowed it down to the
This unexpected MTU change will cause packet fragmentation and potentially other issues (in my case my RDP connection did not work until I lowered the MTU again). Is there a reason that
(Filing this bug here after looking at https://technet.microsoft.com/en-us/windows-server-docs/networking/sdn/contact-sdn-team - hopefully this is the right place.)
This is currently "by design". Hyper-V VM Switch does not inherit MTU settings from the network adapter. You can decrease MTU after the fact.
In our clouds we are accounting for this by enabling JF (or at least increasing MTU by specifying a specific value) and continue to expose 1514 MTU to the guest.
Delayed follow-up question: when I run a netsh command like the following to set the MTU, does anyone know where the MTU value gets stored?
I expected it to end up in the registry, but I searched using regedit and could not find 1460 anywhere. Is there another location in the file system where this value gets saved when set with store=persistent? I tried to search for this information but could not find it.
The reason I'm asking is that when I run a docker container its
**It turns out that if I run a container with
A note for anyone trying to work around this issue, which is still a nuisance over two years later...
For some reason the
However, if I run this