Android client defaults to force relay connection

[araemo]

This seems like a bad default. The point of a p2p overlay network like this is to optimize the connection speed/latency/path while still offering security.

Forcing relay use by default defeats half the purpose, in my opinion.

I'm glad the option is there, but why is it enabled by default?

[sjansen1]

On my Selfhosted installation, i see that NetBird on Android is always relayed, Phone could do a direct connect via IPv4 or IPv6, some nodes are in the same network segment, still relayed.

[araemo]

On my Selfhosted installation, i see that NetBird on Android is always relayed, Phone could do a direct connect via IPv4 or IPv6, some nodes are in the same network segment, still relayed.

Yep, just go into advanced settings on the android app and un-check force relay connection.

I do not understand why that is a default.

[sjansen1]

On my Selfhosted installation, i see that NetBird on Android is always relayed, Phone could do a direct connect via IPv4 or IPv6, some nodes are in the same network segment, still relayed.

Yep, just go into advanced settings on the android app and un-check force relay connection.

I do not understand why that is a default.

Thanks for the hint, i didnt know there was such option and its enabled by default.

[SEsternO]

+1. Combined with no convenient way to setup the self-hosted server (like a QR-code or a netbird:// app link with server url + maybe setup key), it now becomes even more inconvenient for users to go and manually disable this setting. And with hundreds of users on one instance, when some of them inevitably forget to disable it, this creates an unnecessary load on a server, which becomes more critical when servers resource limitations are strict. This feels more like a bug than anything else.