[GH-ISSUE #4656] 🛡️ Feature Request: Privacy & Security Enhancements — Optional Xray Integration #9142

Open
opened 2026-08-05 01:21:00 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @PirouzNik on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4656

Summary:
Add an option to use Xray as a transport or proxy layer for improved privacy, security, and evasion capabilities, especially for restrictive networks.

Why this is needed:

Some users operate in restricted or censored networks, and NetBird traffic can be blocked or inspected.

Xray can provide pluggable transport protocols (e.g., VLESS, Trojan, Reality) to obfuscate or encrypt traffic more strongly.

Adding this as an optional layer would give users more control over their privacy and help avoid traffic fingerprinting.

Improves privacy for those who want to avoid exposing their IP or rely on middle nodes.

Proposed Implementation:

Add support for an Xray client-side configuration within NetBird to tunnel or proxy traffic.

Allow optional self-hosted or custom Xray servers.

UI or CLI flags to enable/disable it easily.

Keep default behavior unchanged for regular users.

Benefits:

Enhanced privacy and security.

Resistance against network censorship.

Optional setup (won’t affect users who don’t need it).

References:

Xray Project GitHub

Originally created by @PirouzNik on GitHub (Oct 16, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4656 Summary: Add an option to use Xray as a transport or proxy layer for improved privacy, security, and evasion capabilities, especially for restrictive networks. Why this is needed: Some users operate in restricted or censored networks, and NetBird traffic can be blocked or inspected. Xray can provide pluggable transport protocols (e.g., VLESS, Trojan, Reality) to obfuscate or encrypt traffic more strongly. Adding this as an optional layer would give users more control over their privacy and help avoid traffic fingerprinting. Improves privacy for those who want to avoid exposing their IP or rely on middle nodes. Proposed Implementation: Add support for an Xray client-side configuration within NetBird to tunnel or proxy traffic. Allow optional self-hosted or custom Xray servers. UI or CLI flags to enable/disable it easily. Keep default behavior unchanged for regular users. Benefits: Enhanced privacy and security. Resistance against network censorship. Optional setup (won’t affect users who don’t need it). References: [Xray Project GitHub](https://github.com/XTLS/Xray-core)
saavagebueno added the feature-request label 2026-08-05 01:21:00 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#9142