This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
WireGuard is a small configuration: an interface address, a listen port, a private key, and a peer with a public key and an allowed prefix. The generators draft that text. They do not open a tunnel.
The private key is prompt-for-this until it lives in the store. A key in git is a key you rotate. AllowedIPs is the prefix that may cross, not a guess of 0.0.0.0/0 unless you have written why this peer should take all traffic.
One lab peer. The other end is a device you administer. Do not point a peer at a network you do not run.
The comparison page owns the choice against other VPNs. This page is the lab file you can read.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name both peers.
- Draft a config.
- Replace keys with a store reference.
- Write AllowedIPs as a prefix you mean.
- Delete a world route unless it is the written design.
- Do not start the tunnel in the writing hour.
Mistakes that outlive the command
WireGuard Setup Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A private key committed.
- AllowedIPs set to the world as a habit.
- A peer you do not administer.
- Two VPN types started together.
- The same key reused everywhere.
Decisions to write down
One decision for WireGuard Setup Guide: Both peers are yours. The key is not in the file. AllowedIPs is explicit. One peer only. And the tunnel is not up yet.
Checks before you call it done
Confirm this before you call the change done: Peer names are in the ticket. The draft has no private key. The prefix is written. No foreign peer was added. And start-up waits for a lab window. If one of those fails, stop.
prompt-for-this is not a WireGuard key.
AllowedIPs is a prefix you mean.Before you leave the device
WireGuard Setup Guide ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.