CloudEdge SAM Azure x PVE Smoke Evidence
Date: 2026-05-29
Branch/build: cloudedge-mvp, routerd v20260528.2308 (439ec316)
Result: PASS
Evidence bundle:
/home/imksoo/routerd-labs/cloudedge-sam/evidence/20260529T161157Z-439ec316-clean
Topology
- Cloud client:
10.77.60.7/24 - On-prem client:
10.77.60.9/24 - Cloud router primary:
10.77.60.4/24 - Cloud router Azure NIC secondary capture address:
10.77.60.9 - On-prem router: router06,
10.77.60.1/24onens21 - Overlay:
wg-hybrid,169.254.110.1/32to169.254.110.2/32
Azure Capture
ce-router-nichad IP forwarding enabled.- Primary private IP was
10.77.60.4. - Secondary private IP was
10.77.60.9. routerd-cloudguest OS did not retain10.77.60.9as a local interface address after routerd reconciliation.10.77.60.9/32was delivered overwg-hybrid.
Cloud Side
RemoteAddressClaim/onprem-client-10-77-60-9wasReady.- Capture type was
provider-secondary-ip. captureDeassignedOSAddress.enforced=true.- Delivery route was installed:
10.77.60.9 dev wg-hybrid scope link metric 120. ip route get 10.77.60.9selectedwg-hybrid.10.77.60.9/32was absent from local interfaces.routerctl doctor hybridwasoverall=pass,fail=0.
On-Prem Side
RemoteAddressClaim/cloud-client-10-77-60-7wasReady.- Capture type was
proxy-arponens21. - Proxy neighbor existed:
10.77.60.7 proxy. - Delivery route was installed:
10.77.60.7 dev wg-hybrid scope link metric 120. ens21.proxy_arp=1.routerctl doctor hybridwasoverall=pass,fail=0.
Connectivity
- Cloud client to on-prem client ping: 3/3 received, 0% loss.
- On-prem client to cloud client ping: 3/3 received, 0% loss.
- Cloud client to on-prem client SSH succeeded with source preserved:
SSH_CONNECTION=10.77.60.7 ... 10.77.60.9 22. - On-prem client to cloud client SSH succeeded with source preserved:
SSH_CONNECTION=10.77.60.9 ... 10.77.60.7 22. - NAT was not observed.
- Client default gateways were unchanged.
Clean-Run Hardening Checks
- Azure Ubuntu reintroduced
10.77.60.9/24oneth0before routerd startup. - routerd
439ec316de-assigned that address without a manualip addr delworkaround. - routerd applied WireGuard without the previous manual
/dev/stdinworkaround. - Evidence was captured before Azure VM deallocation.
- Azure VMs were deallocated after evidence capture; the resource group was not torn down.
Known Notes
- The FORWARD policy doctor check was skipped where the
routerd_filtertable was unavailable; dataplane smoke still passed. - router06 global status remained
Pending, butdoctor hybridpassed and the SAM dataplane path was healthy. captureDeassignedOSAddress.deassigned=falsein steady state means there was no address to remove during that reconcile;enforced=trueplus the local-address doctor pass is the relevant assertion.