WebRTC Fallback Relay Testing Matrix

[seetadev]

🎯 Goal

Verify that custom relay fallback works correctly when direct WebRTC connection fails due to NAT traversal issues (e.g., VPNs or firewalls).

---

🧪 Test Environment

• Peer A: Private peer behind VPN 1
• Peer B: Private peer behind VPN 2
• Relay Node: Custom relay based on libp2p (see [relay setup link])

---

🗂️ Test Matrix

Test Case	Topology Description	Expected Outcome	Status
✅ TC1	Both peers on same LAN or public IP	Direct connection established	✅ Verified
🟨 TC2	Peer A on VPN 1, Peer B on VPN 2	Hole punching fails, fallback to relay	🔄 Scheduled
🟦 TC3	Peer A behind NAT, Peer B on public IP	Hole punching may succeed	⬜ Optional
🟧 TC4	Both peers on mobile hotspots	Hole punching fails, relay used	⬜ Optional

---

🔍 What to Log

• Connection mode reported (Direct / Relay)
• Browser console logs (ICE candidate details)
• libp2p debug logs: DEBUG=libp2p:*
• Relay server logs (peer registration, data relaying)
• UI display state (direct vs relay icon/label)

---

📌 Notes

• Use js-libp2p-example-webrtc-private-to-private UI for live feedback.
• Run relay server using .sh scripts in rust-libp2p/examples/relay-server.
• Later: compare latency/performance between direct and relay connections.

---

✅ Next Steps

• Schedule TC2 VPN-to-VPN test
• Push logs and screenshots for TC2
• Document fallback logic + failure detection
• PR to README.md with this test plan