WireGuard
Modern peer-based VPN operation, keys, AllowedIPs, endpoints, routing, firewall, MTU and troubleshooting.
What this topic solves
Modern peer-based VPN operation, keys, AllowedIPs, endpoints, routing, firewall, MTU and troubleshooting.
Follow state and packet path
Validate the underlay first, then tunnel negotiation/state, routes, policy, MTU and return path.
Input → classification/state → decision → table → next-hop/output → countersDesign before configuration
- Define the failure domain and expected convergence behavior.
- Document addressing, identifiers, timers, MTU and policy boundaries.
- Prefer explicit, observable state over assumptions.
- Plan rollback and out-of-band access before risky changes.
Commands and verification
Command syntax varies by platform and software release. The examples below come from the existing portal content and must be validated against the target platform documentation before production use.
wg show
ip addr show wg0
ip route
ip route get 10.20.0.10
ss -lun
tcpdump -ni any udp port 51820
/interface/wireguard/print detail
/interface/wireguard/peers/print detail
/ip/address/print where interface~"wireguard"
/ip/route/print detail
/ip/firewall/filter/print detail stats
# Exemplo
/interface wireguard
add name=wg-site listen-port=51820
/interface wireguard peers
add interface=wg-site public-key="CHAVE_PUBLICA_REMOTA" \
allowed-address=10.20.0.0/24 endpoint-address=198.51.100.2 \
endpoint-port=51820Evidence-driven workflow
- Define source, destination, time window and exact symptom.
- Establish the expected healthy state and compare it with the observed state.
- Inspect counters, tables, logs and packet captures before resets.
- Test one hypothesis at a time and prefer reversible changes.
- Repeat the original test after correction and check side effects.
WireGuard protocol documentation
Use the current standard/RFC and the documentation for the exact software release being operated. Vendor syntax is an implementation detail; protocol behavior should be understood independently.
Prove the behavior in a controlled topology
Build the smallest topology that reproduces the mechanism, capture control and data traffic, introduce one deliberate failure and diagnose it before applying the fix.