Skip to content

Commit

Permalink
docs: clarify WebRTCDirect cannot reuse the same port as QUIC
Browse files Browse the repository at this point in the history
  • Loading branch information
@sukunrt @hacdias
sukunrt authored and hacdias committed Nov 22, 2023
1 parent 6a51849 commit 3ae04c5
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/config.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2169,9 +2169,9 @@ nodes to connect to other nodes without special configuration, such as TLS
certificates. This can be useful for browser nodes that do not yet support
[WebTransport](https://blog.libp2p.io/2022-12-19-libp2p-webtransport/).

Enabling this transport allows Kubo node to act on `/udp/4001/webrtc-direct`
Enabling this transport allows Kubo node to act on `/udp/4002/webrtc-direct`
listeners defined in `Addresses.Swarm`, `Addresses.Announce` or
`Addresses.AppendAnnounce`.
`Addresses.AppendAnnounce`. At the moment, WebRTC Direct doesn't support listening on the same port as a QUIC or WebTransport listener

**NOTE:** at the moment, WebRTC Direct cannot be used to connect to a browser
node to a node that is behind a NAT or firewall.
Expand Down

0 comments on commit 3ae04c5

Please sign in to comment.