-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zerotier windows - not ajusting interface mtu #2294
Comments
Try to leave and re-join the network on the client |
Hello If you mean to go to zerotier UI and do "disconnect" and "reconnect" we did, but did not do anything. As per my point of view, it should
|
I mean on the client |
Yes, on the client: we disconnect and reconnect but MTU remains the same (2800) even if the zerotier central mtu is 1388 |
I thought this had been fixed actually. #1804 maybe only linux got fixed. The real issue is, users shouldn't need to fuss with the virtual mtu to make it work on mobile carriers |
We also rebooted the machine, no way. |
As per Linux I do confirm that latest version on Ubuntu works fine: change the MTU on Zerotier Central and it "adapts" |
We are experiencing this issue which causes packet loss on Windows
If you change to zerotier MTU to something lower than 2800, the windows client ignores this setting and the windows interface mtu says at 2800; if you query via zerotier-cli get NET_ID mty you get the correct value.
In our case, with windows zerotier client 1.12.2 and also latest version, we get:
zerotier-cli get NET_ID mtu - we get 1388
if we do
netsh interface ipv4 show subinterface
2800 1 2240 58058 ZeroTier One [NET_ID]
So if one of the members is on a mobile network which requires lower mtu, you can ping from mobile to windows, but from windows to mobile you get erratic behaviour.
If we force it via netsh interface ipv4 set interface "ZeroTier One [NET_ID]" mtu=1388 it works fine.
Client should be modified as mobile client: when MTU gets changed on the zerotier network, it gets notified and modifies the Windows interface mtu accordingly.
The text was updated successfully, but these errors were encountered: