From 4e6498e3f1ab024e9d35ac8688e0c812ddcdbc07 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Tue, 21 Apr 2026 18:51:38 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/FAQ.md b/FAQ.md
index e68eacd..fe106e3 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -407,6 +407,25 @@ Ensure your relay server (`hbbr` which uses TCP `21117` port) is running on the
 > 
 > User: Never mind, the relay server wasn't listed after the update.
 
+- Case 3
+> User: 1- When connecting from any router to any other router without a firewall, the connection works correctly and you don't encounter any problems.
+> 2- When connecting from a regular router to a router with an OpenSense or PFSense firewall, the connection doesn't work. However, the reverse works correctly.
+>
+> RustDesk: Could you please do the following for both directions of the connection (A → B and B → A)?
+> 
+> Perform an A → B connection attempt, then collect the newly generated hbbs and hbbr logs.
+> 
+> Perform a B → A connection attempt, then collect the newly generated hbbs and hbbr logs again.
+> 
+> Please make sure to clearly separate the logs for each direction. We will use them to compare whether the IP used to connect to the ID/relay server is different in each case.
+> 
+> RustDesk: We can now confirm that the connection is being successfully established each time. However, the PeerInfo is not being received via the relay, which indicates that the firewall is likely blocking or interfering with the communication between the client and the relay server.
+> 
+>RustDesk: Please try allowing traffic to and from rustdesk-p.mrwn.site:60253 in your firewall.
+>
+>User: It's working! 
+
+
 
 We run the server on a Synology Docker container.