From 7877770a7d6245180ba59251ee06f436a5ce919d Mon Sep 17 00:00:00 2001
From: mlsmaycon <mlsmaycon@gmail.com>
Date: Tue, 5 Jul 2022 01:36:06 +0200
Subject: [PATCH] Add FAQ page

---
 docs/FAQ/firewall-ports.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 docs/FAQ/firewall-ports.md

diff --git a/docs/FAQ/firewall-ports.md b/docs/FAQ/firewall-ports.md
new file mode 100644
index 00000000..54f33a3f
--- /dev/null
+++ b/docs/FAQ/firewall-ports.md
@@ -0,0 +1,22 @@
+---
+id: firewall-ports
+title: What firewall ports should I open to use NetBird?
+sidebar_position: 1
+---
+### Incoming ports
+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.
+### Outgoing ports
+NetBird usually won't need open ports but sometimes you or your IT team needs to secure and verify 
+all outgoing traffic and that may affect how NetBird clients connect to the [control layer](/overview/architecture) 
+and negotiate the peer-to-peer connections.
+
+Below is the list of NetBird hosted endpoints and ports they listen to:
+* Management service: 
+  * **Endpoint**:api.wiretrustee.com
+  * **Port**: TCP/33073
+* Signal service:
+    * **Endpoint**:signal.wiretrustee.com
+    * **Port**: TCP/10000
+* Relay (TURN) service:
+    * **Endpoint**:turn.netbird.io
+    * **Port range**: UDP/5555-65535
\ No newline at end of file