Grant Limberg

@rhetr thanks for digging in on that. Hadn't seen that Stack Exchange link before. Could definitely be an issue in Linux if it's also appearing on other things like Hamachi....

can you paste the output of `cat /proc/cpuinfo`? (Just one of the CPU records from the file will be fine)

Hrmm, so for joining, it looks like zerotier is creating the interface with the default MTU before even receiving the network config?

Assuming the network config is coming in correct, it should be correct on `ZT_VIRTUAL_NETWORK_CONFIG_OPERATION_UP` https://github.com/zerotier/ZeroTierOne/blob/269501eaa0c22bdc402e689b0d061325fb6ddbce/service/OneService.cpp#L2426 So the value is either cached incorrectly, or coming across the wire incorrectly sometimes

@qt1 MTU is not settable via `local.conf`. It's a network level option controlled by the network controller.

We don't recommend altering the default MTU, and as described above, there's currently an issue with it. That said, it is a modifiable field when using the https://my.zerotier.com API directly....

OK. Well this is still the wrong place to bring up something off the current topic. This issue is about MTU changes not being persisted on Linux boxes. For talking...

@mlboy ever figure this out? I'm running into the same issue

Current workaround until this is fixed macOS fix: * Close the ZeroTier tray application * Open a terminal and execute the following command: rm ~/Library/Application\ Support/ZeroTier/One/authtoken.secret and possibly rm ~/Library/Application\...

| is there a way to modify the destination port of the request @fathermrsing No. Destination port depends on what ports the destination has ZeroTier running on. There's no way...