The two most common topologies I've seen for WireGuard are: 1) Client-server, where the client is behind NAT and the server is publicly available at some DNS.

The two most common topologies I've seen for WireGuard are: 1) Client-server, where the client is behind NAT and the server is publicly available at some DNS. The client specifies the server by hostname as the endpoint, and the server doesn't bother specifying an endpoint. Client roams when they switch networks, server roams when they roll over the server, everybody is happy. 2) Peer-to-peer, where the nodes are directly addressable by IP address, whether by public IP or private virtual private IP. In this case, the node dialing in sets an endpoint of the node being dialed, and the node being dialed doesn't bother specifying an endpoint. Thereafter node identity is verified by private key and nodes can fully roam within the firewall-limited subnet. In every case I've seen, roaming by default is the right choice.