libp2p WebTransport Transport WebTransport Sessions

For each session the general flow is:

1. Creation
2. Wait for ".ready"/".closed" to resolve or reject
3. Open a bidirectional stream to perform a noise handshake
4. Hand off to the libp2p upgrader to make the connection usable by the application

The graph below shows the current state of the transport running live in the page.

• "pending" - a session has been created but ".ready"/".closed" have yet to resolve or reject
• "open" - a session has been created, ".ready" has resolved and the noise handshake has completed
• "ready_error" - `.ready`/`.closed` rejected
• "noise_error" - `.ready` resolved but the noise handshake failed
• "upgrade_error" - the noise handshake succeeded but upgrading the connection failed (e.g. an internal libp2p error)
• "ready_timeout" - `.ready`/`.closed` did not resolve or reject in a timely fashion
• "noise_timeout" - `.ready` resolved but we could not transfer data over a bidirectional stream opened on the channel
• "close" - a graceful close from the local end of the session
• "abort" - a non-graceful close from the local end of the session
• "remote_close" - the remote closed the session

Clicking a dataset from the legend will toggle it's inclusion in the graph.

• Opened sessions in the last 0s: 0
• Max opened connections per minute: 0
• Totals:
  • Success: 0
  • Ready error: 0
  • Noise error: 0
  • Upgrade error: 0
  • Ready timeout: 0
  • Noise timeout: 0
  • Failure rate: 0

Node

• Peer ID: Unknown
• Status: Initialising
• Connections: 0
• Addresses: 0

Peers

Query

Simulate network traffic by running a DHT query to find peers close to a random set of bytes Go

The source code for this page can be found at ipfs-shipyard/www-libp2p-webtransport-sessions