Brad Fitzpatrick 44b07aa708 netcheck: STUN less aggressively to known distant servers ... If Australia's far away and not going to be used, it's still going to be far away a minute later. No need to send backup just-in-case-UDP-gets-lost STUN packets to the known far away destinations. Those are the ones most likely to trigger retries due to delay anyway (in random 50-250ms, currently). But we'll keep sending 1 packet to them, just in case our airplane landed. Likewise, be less aggressive with IPv6. The main point is just to see whether IPv6 works. No need to send up to 10 packets every round. Max two is enough (except for the first round). This does mean our STUN traffic graphs for IPv4-vs-IPv6 will change shape. Oh well. It was a weird eyeball metric for IPv6 connectivity anyway and we have better metrics. We can tweak this policy over time. It's factored out and has tests now.		2020-05-04 23:37:01 -07:00
..
netcheck_test.go	netcheck: STUN less aggressively to known distant servers	2020-05-04 23:37:01 -07:00
netcheck.go	netcheck: STUN less aggressively to known distant servers	2020-05-04 23:37:01 -07:00