The core idea is to provide a simple "one touch" method to maintain connections for people who are not confident with any IT boileplate like profiles/settings/MTU/keys/etc.
Workflow under the hood:
- Add tunnel => user input "example.com"
- DNS request resolve( TXT, _wg.example.com ) => "dhcp_url: https://dhcp.example.com/endpoint?public_key; methtod: h3/h2; config_url: https://account.example.com"
- HTTP GET h3 https://dhcp.example.com/endpoint?public_key => example.com.conf
- That's it.
- Additionally there is a url for server-side configuration of a tunnel. No need of any authorization, since connection is established and DNS is maintained by provider, so link may point to nonpublic internal resource, where keys are already known.
Workflow for enduser:
- User input "example.com"
- Connected!
The core idea is to provide a simple "one touch" method to maintain connections for people who are not confident with any IT boileplate like profiles/settings/MTU/keys/etc.
Workflow under the hood:
Workflow for enduser: