Mission setup
Browser-facing WebTransport URL. Use HTTPS + HTTP/3 bridge endpoints, not raw UDP/9001 listeners.
Optional second WebTransport endpoint for round-robin or mirror tests.
Overrides probes to a specific backend bridge when you need to isolate one node.
Number of ACK metadata samples used to show which backend or LB target answered.
Selects direct, alternating, or mirrored traffic across the primary and optional fallback bridge.
Autheo-provided public DNS name for the LB front door.
Use 443 for Certik / third-party validation unless Autheo provides another port.
Public IP DNS should resolve to; used by host-side DNS diagnostics.
Autheo VPC/private address, useful only for operator-side infrastructure checks.
Raw Quinn UDP backend reached by the LB bridge, not a browser target.
Autheo-provided LB WebTransport endpoint for front-door validation.
Edit this for third-party testing
What you need to provide: public DNS or IP for your hardware bridge.
Edit this for third-party testing
Use 443 when possible; 8443 is common for non-root or lab bridge deployments.
Edit this for DNS checks
Public IP your custom hostname should resolve to for DNS diagnostics.
Private LAN/VPC IP of the custom bridge host for firewall and reachability checks.
Edit this for third-party testing
Raw backend the WebTransport bridge forwards to. Use 127.0.0.1:9001 only when bridge and listener share the hardware host.
Edit this for third-party testing
Use this if you are testing your own hardware node through its WebTransport bridge.
Edit this for UC4-UC7 testing
Primary endpoint UC4 will probe and send traffic to after Apply selected UC scenario.
External Tester Mode · Recommended for Certik / third-party UC4-UC7 validation
UC4-UC7 are guided paths for validating Autheo infrastructure, the load balancer front door, and
operator-supplied hardware bridge or raw QUIC backend details. Amber fields are the ones third-party
testers usually need to edit.
Autheo test infrastructure
Main bridge:
Load balancer:
Expected path:
/pqcnet-gossipRecommended WebTransport port:
443Third-party / custom node inputs
Custom bridge endpoint:
Raw QUIC backend peer:
Public host/IP:
Debug/backend peer:
Active transport path: choose UC4-UC7 and apply the scenario.
- Sender (Node 1+): Initialize wasm -> Install host transport -> Probe bridge TLS/WebTransport -> Send one batch.
- Listener (Node 0): Initialize wasm -> Install host transport -> Probe listener hooks -> Start listener.
- Use Connect selected role for an automatic role-based setup flow.
- Cloud rule: keep
PQCNET_RAW_QUIC_PEER=127.0.0.1:9001only when the bridge and raw listener run on the same host; otherwise point it at the listener's reachable private IP/DNS.
Browser host note: this page can send only to a WebTransport endpoint (HTTPS + HTTP/3). Point
the peer field at `pqcnet-webtransport-bridge`, which forwards to raw `pqcnet-super-node` on UDP/9001.
Default primary bridge endpoint: `https://bridge.autheolabs.com/pqcnet-gossip`.
Default secondary bridge endpoint: `https://lb.autheolabs.com/pqcnet-gossip`.
Cloud quick start: start Node 0/raw listener first, then start the WebTransport bridge, then use this page for Node 1+ sender tests.
If Probe bridge TLS/WebTransport succeeds but Send one batch + ACK fails, the browser reached the bridge but the bridge likely could not reach
PQCNET_RAW_QUIC_PEER.
Guided third-party test flow