Xray is Not Just a Proxy: Programmable Traffic Routing (Dokodemo-door, WARP, Tor)

Описание: When people talk about Xray, they usually focus on anonymity or bypassing firewalls. But if you dig deeper, Xray is actually a powerful, programmable traffic router that lives in user space.

In this video, I want to move beyond basic proxying and show you the full mental model of Xray: Inbound → Routing → Outbound.

We start simple by mapping local ports using `dokodemo-door`. Then, we stretch that concept across the internet by chaining two Xray instances via an encrypted tunnel. Finally, we push the logic further by selectively routing traffic through Cloudflare’s WARP network and accessing `.onion` domains via Tor—all decided by centralized routing rules, not kernel tricks.

By the end of this tutorial, Xray should stop looking like "just a proxy" and start looking like a general-purpose networking swiss-army knife.

📂 Configuration Files & Notes
https://github.com/filip-lebiecki/xra...

🛠 Tools Used

Xray Core: The traffic router.
iperf3: For testing network paths.
wgcf: To generate Cloudflare WARP profiles.
Docker: To run the Tor SOCKS proxy.

---

⏱️ Chapters
00:00 Intro: Xray is more than a proxy
01:05 Part 1 — Port Mapping with dokodemo-door
03:57 Part 2 — Extending Port Mapping Over Distance (Chaining Xray)
06:32 Part 3 — Securing the Tunnel (Encryption)
07:34 Part 4 — Cloudflare WARP as an Xray Outbound
09:14 Part 5 — Generating a WARP profile with wgcf
11:01 Part 6 — Selective Routing: IPv6 via Cloudflare, IPv4 Direct
12:23 Part 7 — Routing .onion Traffic Through Tor
15:25 Outro

#XrayCore #Networking #SelfHosting #Linux #Privacy #CloudflareWARP #Tor #TrafficRouting #SysAdmin #dokodemo #cybersecurity