Function probe_node 

pub async fn probe_node(
    backend: &dyn LocalBackend,
) -> (SelfIdentity, HashMap<IpAddr, String>)

Who this node is and what it calls its peers, from one reading of status.

Both at once because both come out of the same document, and running tailscale status twice at startup to parse the same JSON two ways is work nobody asked for.