75a03fc719
If we get a packet in over some DERP and don't otherwise know how to reply (no known DERP home or UDP endpoint), this makes us use the DERP connection on which we received the packet to reply. This will almost always be our own home DERP region. This is particularly useful for large one-way nodes (such as hello.ts.net) that don't actively reach out to other nodes, so don't need to be told the DERP home of peers. They can instead learn the DERP home upon getting the first connection. This can also help nodes from a slow or misbehaving control plane. Updates tailscale/corp#26438 Change-Id: I6241ec92828bf45982e0eb83ad5c7404df5968bc Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> |
||
|---|---|---|
| .. | ||
| archtest | ||
| deptest | ||
| integration | ||
| iosdeps | ||
| jsdeps | ||
| natlab | ||
| nettest | ||
| tailmac | ||
| tools | ||
| allocs.go | ||
| clock_test.go | ||
| clock.go | ||
| log_test.go | ||
| log.go | ||
| reflect.go | ||
| resource.go | ||
| test-wishlist.md | ||
| tstest_test.go | ||
| tstest.go | ||