This is the Goolge Translate for "gold" 's Chinese text:

IMHO, NETMAKER is so difficult to use, it has high requirements on the server and client, only professionals can use it. There are so many problems that it doesn't work right now.
Public cloud service, not safe, I want to use it in my home network, DDNS, but after the IP of NETMAKER changes, the client can't connect, the client does not recognize DDNS, but just accesses the original IP
The parameters required by the server made me dizzy, and there were multiple network addresses that needed to be configured.
https://www.jordanwhited.com/posts/wireguard-endpoint-discovery-nat-traversal/
WireGuard Endpoint Discovery and NAT Traversal using DNS-SD
In this post we will set out to establish a WireGuard tunnel between dynamically addressed peers that are both sitting behind a NAT. One of the primary goals for achieving this is to stick with WireGuard in its purest form, the code that now ships with the Linux Kernel.
WireGuard Endpoint Discovery and NAT Traversal using DNS-SD
About UDP hole punching, you can refer to the technology
headscale is considering developing a WEB GUI, I might switch to
In my opinion, NETMaker should be redesigned from the top-level architecture,
Use as little domain name and port as possible, suitable for home, after the router
At no time should the private key be sent to NETMAKER, this is the underlying principle.
IPV6 access issues should be considered,
NETCLIENT should be able to access the network whether it is IPV4 or IPV6
gold — 04/17/2022
Only one URL is required, and when the server IP changes, the client can respond in time