Denton Gentry
Denton Gentry
Substantially similar to https://github.com/tailscale/tailscale/issues/814
Near BUG-55bf2acb1da82b40cd4d95e7439a4a5fe347a488590342404535a5f8b5102032-20220524150545Z-b8e51a4d70ef9158 ``` 2022-05-24 22:00:09.771271 +0900 +0900: [RATELIMIT] format("netmap diff: (none)") (2 dropped) 2022-05-24 22:00:09.771282 +0900 +0900: netmap diff: (none) ```
We're expecting to release Tailscale 1.14 next week, and at this point though we'll be using Go 1.17 we won't be in a position to produce native ARM64 binaries in...
The MSI installer provides native ARM64 support. https://pkgs.tailscale.com/stable/#windows
I promise that we will update the bug when work begins in earnest.
This was a choice to be able to launch the feature for initial use. For a device owned by a User, the Check action is to have the User login...
The client software does not currently communicate tx/rx byte counts to the coordination server at all, so it isn't a matter of just adding it to the API. Is there...
I think this is as done as it is going to get. TX/RX byte counts through the API is in conflict with battery life concerns about clients communicating more often...
Closing during bug scrub
For point 1 the `var msg []byte` is still there but has been refactored into sendMapRequest https://github.com/tailscale/tailscale/blob/aaba49ca1053fda6e98069ea3451c4051e1efedf/control/controlclient/direct.go#L737 For point 2 the DecodeAll is in decodeMsg https://github.com/tailscale/tailscale/blob/aaba49ca1053fda6e98069ea3451c4051e1efedf/control/controlclient/direct.go#L901