ProficientNowTechRFCs
Platform RFCs/Rfcs/Spec wireguard/RFC WG 0001

2. Phases

RFC-WG-0001                                                      Section 2
Category: Specification                                              Phases

2. Phases

← Prerequisites | Index | Next →


Phase Overview

PhaseNameOutcome
1Plan VPN addressingWG subnet and per-host IPs defined
2Install and configure WireGuardwg0 configured on each host
3Establish peer connectivityHosts can reach each other over WG
4Enforce WG-only ingressPublic/LAN ingress blocked; WG ingress allowed
5Operational validationDocumented checks pass

Phase 1: Plan VPN Addressing

Tasks

TaskDescriptionOutcome
1.1Select WG subnetRFC-level subnet assigned (e.g., 10.50.0.0/24)
1.2Assign WG IPsEach host has a unique WG IP
1.3Select endpointsEach host endpoint IP recorded

Test

VerificationMethodExpected Result
Address plan existsReview planUnique WG IPs and endpoints defined

Iterate

CheckpointProceed IfRollback If
All addresses uniqueNo conflictsDuplicate WG IPs found

Rollback

StepAction
1.R1Reassign conflicting WG IPs

Phase 2: Install and Configure WireGuard

Tasks

TaskDescriptionOutcome
2.1Install WireGuard packagesWireGuard present on each host
2.2Generate keysPublic/private keys stored on each host
2.3Create wg0 configsEach host has wg0 configuration

Test

VerificationMethodExpected Result
Config files presentFile checkwg0 config exists on all hosts

Iterate

CheckpointProceed IfRollback If
Keys and configs validPeer entries completeMissing keys or peer entries

Rollback

StepAction
2.R1Regenerate keys
2.R2Rebuild wg0 configs

Phase 3: Establish Peer Connectivity

Tasks

TaskDescriptionOutcome
3.1Bring up wg0WireGuard interface is active
3.2Verify peer handshakePeers show recent handshake
3.3Verify WG routingTraffic routes via wg0

Test

VerificationMethodExpected Result
Peer handshakeWG status checkRecent handshake timestamps
WG reachabilityICMP over WGPeers reachable via WG IP

Iterate

CheckpointProceed IfRollback If
WG connectivity stableNo packet lossHandshake absent or unstable

Rollback

StepAction
3.R1Recheck endpoints and firewall
3.R2Restart wg0 on affected hosts

Phase 4: Enforce WG-Only Ingress

Tasks

TaskDescriptionOutcome
4.1Set UFW defaultsDefault deny inbound, allow outbound
4.2Allow WG interfaceWG ingress permitted
4.3Restrict public/LAN ingressPublic/LAN ingress blocked except required ports

Test

VerificationMethodExpected Result
WG ingress allowedFirewall policy reviewwg0 ingress allowed
Public ingress blockedExternal checkService ports not reachable on public/LAN

Iterate

CheckpointProceed IfRollback If
WG-only behaviorWG reachable; public blockedPublic access still possible

Rollback

StepAction
4.R1Revert firewall rules
4.R2Re-apply ruleset with corrections

Phase 5: Operational Validation

Tasks

TaskDescriptionOutcome
5.1Validate encryptionWG traffic shows active handshakes
5.2Validate service reachabilityWG peers can access services
5.3Validate public isolationPublic/LAN cannot access services

Test

VerificationMethodExpected Result
WG encryptionWG status reviewActive handshakes and data transfer
Service accessReachability checksServices reachable via WG IP
Public isolationPublic access checksServices not reachable on public/LAN

Iterate

CheckpointProceed IfRollback If
All validations passStable and consistentAny failed validation

Rollback

StepAction
5.R1Re-run phases 3–4 checks

End of Phases — RFC-WG-0001