Update faq.mdx to reflect relay usage (#255)

* Update faq.mdx to reflect relay usage

Updated the Documentation to account for the relay service. May be used in a peer-to-peer setting, where one peer acts as a router.

* Fixed Typo
This commit is contained in:
Arne
2024-12-05 10:18:03 +01:00
committed by GitHub
parent f74b56cf24
commit 9545fa09e2

View File

@@ -36,6 +36,13 @@ Below is the list of NetBird hosted endpoints and ports they listen to:
* `nslookup turn.netbird.io`
* In more restricted environments, `netbird status` will show `keepalive ping failed` errors without a firewall rule for TURN
* Example `nftables` outbound firewall rule: `ip daddr turn.netbird.io tcp dport 443-65535 accept`
* Relay service:
* **Endpoint**: *.relay.netbird.io
* **Port**: TCP/443
* **IPv4**: The list is dynamic and geo-distributed; When looking at the `netbird status -d` output, you can see which relay you are connecting to.
* It is advised to wildcard `*.relay.netbird.io` when possible, to avoid interrupts.
## Why and what are the anonymous usage metrics?