cg31

依赖wg的安全机制足够了，属于使用加密的信道。再加一层反而画蛇添足。

It seems this is an error from libgit2, which is used by git2-rs. I wonder if cargo-edit could use an option "git-fetch-with-cli=true" like cargo to fix it.

I tried using git-cli to update registry index, it indeed fixed the issue: https://github.com/cg31/cargo-edit/commit/42e025e066dbbda820d800500c359d2218e1abbe

The MTU=8600 looks strange, have you tried using a regular one?

I just did a test, but I don't have a gigabyte link. It seems there is no speed issue with Nebula on a 100M link. the physical interface ``` iperf...

> I ran a little longer. Non lighthouse was run twice, then lighthouse responded. I have the same experience. It seems Nebula doesn't establish the network fast. But it is...

This PR is for an opposite request... but I think it can also satisfy your request: https://github.com/slackhq/nebula/pull/217

I just tried the master branch, it looks like also needed some optimization [384] 0.0-89.2 sec 10.0 GBytes 963 Mbits/sec This is where a tunnel is useful. For the record,...

It is hard to spot the bottleneck just by looking at the code. Profiling tools are needed to find the hot spots.

Maybe it is related to OS? Could you use "-n 10G" to iperf? So we can compare to the result with the result on Windows?