You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: iroh/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@ Iroh is a library to establish direct connectivity between peers.
4
4
It's built on peer-to-peer [QUIC](https://en.wikipedia.org/wiki/QUIC) using both relays and holepunching.
5
5
The main structure for connection is the `Endpoint` entrypoint.
6
6
7
-
Peer to peer connectivity is established with the help of a _relay server_. The relay server provides Session Traversal Utilities for NAT [(STUN)](https://en.wikipedia.org/wiki/STUN) for the peers. If no direct connection can be established, the connection is relayed via the server.
7
+
Peer to peer connectivity is established with the help of a _relay server_. The relay server provides QUIC NAT traversal (QAD) for the peers. If no direct connection can be established, the connection is relayed via the server.
8
8
9
-
Peers must know and do verify the PeerID of each other before they can connect. When using a relay server to aid the connection establishment they will register with a home relay server using their PublicKey. Other peers which can not establish a direct connection can then establish connection via this relay server. This will try to assist establishing a direct connection using STUN and holepunching but continue relaying if not possible.
9
+
Peers must know and do verify the PeerID of each other before they can connect. When using a relay server to aid the connection establishment they will register with a home relay server using their PublicKey. Other peers which can not establish a direct connection can then establish connection via this relay server. This will try to assist establishing a direct connection using QAD and holepunching but continue relaying if not possible.
10
10
11
11
Peers can also connect directly without using a relay server. For this, however the listening peer must be directly reachable by the connecting peer via one of it's addresses.
Copy file name to clipboardExpand all lines: iroh/docs/local_relay_node.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ To connect to this iroh-relay when doing your normal iroh commands, adjust the i
16
16
# iroh.config.toml:
17
17
[[relay_nodes]]
18
18
url = "http://localhost:3340"
19
-
stun_only = false
20
-
stun_port = 3478
21
19
```
22
20
23
21
If you want to give a specific port for the iroh-relay to bind to, you can create a iroh-relay config file and pass that file in using the `--config_path` flag. You need to retain a `secret_key`, so it is recommended to run `iroh-relay --config-path [PATH]` once to generate a secret key and save it to the config file before doing further edits to the file.
@@ -29,13 +27,10 @@ To change the port you want to listen on, change the port in the `addr` field:
0 commit comments