Replies: 1 comment
-
Hello, @mfld-pub! Thanks for your report. As the MTU change does not present in the UI (also as in the ZeroTier Central), it wasn't properly tested. It could also be the bug as in the ZeroUI backend, or in the ZeroTier controller itself on specific version. The presented error is really strange, as it should not fail there. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Have some sites in the mix where the WAN MTU is something exotic.
When I join these sites to ZT networks issues are observed that indicate MTU problems.
i.e. pings work but transfers of large data fail. SSH login works but freezes during banner display.
I found my API key in db.json
The token seems to work - I can interact with the API:
curl -s -H "Authorization: Bearer mysuperawesometoken" -H "Content-Type: application/json" https://localhost/api/network | jq -r '.[]| "\(.config.name)***\(.id)"' | column -t -s "***"
works and displays my networks.
But when I try to force a network ID's MTU to something custom it will seem to accept it but it doesn't take effect.
I try doing it like this:
curl -X POST "https://localhost/api/network/somenetworkid" -H "Authorization: Bearer mysuperawesometoken" -d '{"config": {"mtu": 1432}}'
When I check, all MTU are showing as 2800.
EDIT: Just noticed that zu-main container restarts when I try to post to the API endpoint to modify an MTU.
Will likely turn this into a bug or feature request. Should I be able to set a custom MTU with zero-ui or is it not currently a feature ?
Beta Was this translation helpful? Give feedback.
All reactions