e74a705c67
We are soon going to start assigning shared-in nodes a CGNAT IPv4 in the Hello tailnet when necessary, the same way that normal node shares assign a new IPv4 on conflict. But Hello wants to display the node's native IPv4, the one it uses in its own tailnet. That IPv4 isn't available anywhere in the netmap today, because it's not normally needed for anything. We are going to start sending that native IPv4 in the peer node CapMap, only for Hello's netmap responses. This change enables Hello to display that native IPv4 instead, when available. Updates tailscale/corp#25393 Change-Id: I87480b6d318ab028b41ef149eb3ba618bd7f1e08 Signed-off-by: Brian Palmer <brianp@tailscale.com> |
||
|---|---|---|
| .. | ||
| c2ntypes.go | ||
| derpmap.go | ||
| proto_port_range_test.go | ||
| proto_port_range.go | ||
| tailcfg_clone.go | ||
| tailcfg_test.go | ||
| tailcfg_view.go | ||
| tailcfg.go | ||
| tka.go | ||