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: src/pages/about-netbird/faq.mdx
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,12 @@ export const title = 'FAQ'
5
5
## What firewall ports should I open to use NetBird?
6
6
7
7
### Incoming ports
8
+
8
9
NetBird's agent doesn't require any incoming port to be open; It negotiates the connection with the support of the signal and relay services.
9
10
That said, it helps to open inbound UDP to port 51820 on one of the peers if they are only getting relayed.
11
+
10
12
### Outgoing ports
13
+
11
14
NetBird usually won't need open ports, but sometimes you or your IT team needs to secure and verify
12
15
all outgoing traffic, and that may affect how NetBird clients connect to the [control layer](/about-netbird/how-netbird-works)
13
16
and negotiate the peer-to-peer connections.
@@ -23,6 +26,7 @@ and negotiate the peer-to-peer connections.
23
26
</Note>
24
27
25
28
Below is the list of NetBird hosted endpoints and ports they listen to:
29
+
26
30
* Management service:
27
31
***Endpoint**: api.netbird.io
28
32
***Port**: TCP/443
@@ -53,11 +57,10 @@ Below is the list of NetBird hosted endpoints and ports they listen to:
53
57
***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.
54
58
* It is advised to wildcard `*.relay.netbird.io` when possible, to avoid interrupts.
55
59
56
-
57
-
58
60
## Why and what are the anonymous usage metrics?
59
61
60
62
### Why did we add metrics collection?
63
+
61
64
As an open-source project and business, making data-driven decisions is essential. By collecting anonymous metrics, we can understand our adoption rate, feature usage, and the types of client operating systems in use. We kindly ask our community users to keep metrics enabled, as this helps us assess the impact of bugs and measure the quality of our software over time.
62
65
63
66
<Note>
@@ -67,6 +70,7 @@ The collection is strict to our management system.
67
70
If the metric collection infringes any internal regulation or policy, it can be disabled by setting the flag `--disable-anonymous-metrics=true` to the management service startup command. the default interval is 12 hours, but it can be adjusted with the environment variable `NETBIRD_METRICS_INTERVAL_IN_SECONDS`.
68
71
69
72
### What are the metrics being collected?
73
+
70
74
We are collecting the following metrics:
71
75
* Number of accounts
72
76
* Number of users
@@ -82,9 +86,10 @@ We are collecting the following metrics:
82
86
* Service version
83
87
* Metrics generation time
84
88
85
-
86
89
### Metrics UUID
90
+
87
91
We are using an installation ID for each management service which is generated once and stored in your management store database. It doesn't have any trace of any other private information, and it helps distinguish each deployment.
88
92
89
93
### Metrics pusher IP
94
+
90
95
We are not storing the pusher IP address; it gets discarded once the request is complete.
0 commit comments