From 3805237d74bf17785a3a7caa33ae1c0a9ed2e12a Mon Sep 17 00:00:00 2001
From: Alexey <247128645+axkurcom@users.noreply.github.com>
Date: Wed, 31 Dec 2025 05:28:32 +0300
Subject: [PATCH] Update README.md

---
 README.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/README.md b/README.md
index a9181b7..c5a4615 100644
--- a/README.md
+++ b/README.md
@@ -62,6 +62,21 @@ WantedBy=multi-user.target
 4. In Shell type `systemctl status telemt` - there you can reach info about current MTProxy status
 5. In Shell type `systemctl enable telemt` - then telemt will start with system startup, after the network is up
 
+## FAQ
+### Telegram Calls via MTProxy
+- Telegram architecture does **NOT allow calls via MTProxy**, but only via SOCKS5, which cannot be obfuscated
+### How does DPI see MTProxy TLS?
+- DPI sees MTProxy in Fake TLS mode as TLS
+- the SNI you specify sends both the client and the server;
+- ALPN is similar to HTTP 1.1/2;
+- high entropy, which is normal for AES-encrypted traffic;
+### Whitelist on IP
+- MTProxy cannot work when there is: 
+  - no IP connectivity to the target host
+  - OR all TCP traffic is blocked
+  - OR all TLS traffic is blocked,
+- like most protocols on the Internet; this situation is observed in China behind the Great Chinese Firewall and in Russia on mobile networks
+
 ## Why Rust?
 - Long-running reliability and idempotent behavior
 - Rust’s deterministic resource management - RAII