Feature Request: Replace / add support for TrustTunnel instead of WireGuard for P2P connections (better DPI resistance)

[iForged]

Netbird's WireGuard-based P2P works great in open networks, but in censored/restricted environments (Russia, Egypt, Iran etc.) standard WireGuard is easily detected and blocked.
TrustTunnel (open-source since Jan 2026, https://github.com/TrustTunnel/TrustTunnel) is a modern HTTPS-masquerading protocol (HTTP/2 + QUIC/TLS) that looks like regular web traffic — much harder to DPI-block, with near-zero speed loss compared to obfuscated WireGuard.
Request: Please consider adding support for TrustTunnel as an alternative (or replacement) transport for P2P connections, or allow switching per-peer/network.
This would make Netbird far more usable in high-censorship scenarios without extra wrappers.
As I wrote above, this option will likely be better than adding obfuscation in terms of useful traffic, which is discussed here: #1096

[lixmal]

How would this work for P2P? TrustTunnel appears to be Hub and Spoke, so not much different than NetBird's relay

[iForged]

Yes, you are absolutely right. At the moment, TrustTunnel does not support peer-to-peer networking, but according to their roadmap, this feature is planned.
https://github.com/TrustTunnel/TrustTunnelClient?tab=readme-ov-file#roadmap