From afca863997be8783eceec005be465e83aa65847f Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sun, 1 Jun 2025 16:28:13 +0800
Subject: [PATCH] Updated FAQ (markdown)

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

diff --git a/FAQ.md b/FAQ.md
index e3414b5..020268c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -80,6 +80,14 @@ Go to [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) o
 
 If you host the server in your intranet with some type of routers, you may have network problem because of NAT hairping.
 
+Here is how ChatGPT explains NAT hairping.
+
+> Now, let's say you're inside your network, on your laptop, and you try to access that same web server using its public IP address or domain name.
+>
+> - Without NAT Hairpinning: Your request goes to your router, which sees that the destination IP is its own public IP. Normally, the router expects traffic destined for its public IP to come from the internet (external network). It might get confused, or simply not know how to route the traffic back to the internal server, and the connection will fail.
+>
+> - With NAT Hairpinning: When your router has NAT Hairpinning enabled, it recognizes that the request from an internal device is destined for its own public IP (which is also configured to forward to an internal server). Instead of sending the request out to the internet and then trying to route it back in (which is inefficient and often fails), the router intelligently redirects the request directly back into the internal network to the correct internal IP address of the server.
+
 One simple solution for NAT hairping (loopback) is that both internal and external use domain. Internally, use an internal DNS Server (or modify your hosts file) to point the domain to an intranet IP.
 
 https://rustdesk.com/docs/en/self-host/nat-loopback-issues/