We use the self-hosted version of NetBird ~10 clients, all working great, all the clients have dual WAN configuration with failover. The clients are in different cities. The problem is that whenever the main WAN goes down it reconnects through the Relay witch is working but ads the extra latency from the Relay + all our backup WANs are cellular 3G/4G and ads more latency. If we reboot the client or reconnect NetBird on client it connects fine without the Relay through the backup WAN.
I think NetBird is retrying to reestablish the old connection, it fails and goes to Relay and hangs to it.
To Reproduce
Main WAN goes down
Expected behavior
If the connection fails (main WAN goes down), try to reconnect without the Relay. Or if it goes through Relay retry a direct connection after 2-3 minutes.
Describe the problem
We use the self-hosted version of NetBird ~10 clients, all working great, all the clients have dual WAN configuration with failover. The clients are in different cities. The problem is that whenever the main WAN goes down it reconnects through the Relay witch is working but ads the extra latency from the Relay + all our backup WANs are cellular 3G/4G and ads more latency. If we reboot the client or reconnect NetBird on client it connects fine without the Relay through the backup WAN. I think NetBird is retrying to reestablish the old connection, it fails and goes to Relay and hangs to it.
To Reproduce
Main WAN goes down
Expected behavior
If the connection fails (main WAN goes down), try to reconnect without the Relay. Or if it goes through Relay retry a direct connection after 2-3 minutes.
Are you using NetBird Cloud?
self-host
NetBird version
0.28.6