[GH-ISSUE #2637] Windows Client: Network Routes dissappear after Peer Login Expiration and don't reappear #5683

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

Originally created by @Rob787 on GitHub (Sep 24, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2637

Describe the problem

We noticed the following behaviour which is at the moment preventing us from deploying Netbird productively:

The network routes seem to dissappear from Windows Peers after they've been asked to re-login (previously login expired per default setting). After reauthentication, the network routes are not updated and remain empty. The only way to get them back is by triggering a change on the network routes server side (e.g. deactivating and activating a route quickly).

To Reproduce

Steps to reproduce the behavior:

  1. Reauthenticate after Netbird login expired
  2. Reconnect
  3. Check Network Routes of client and see they are empty
  4. Server-side: Deactivate and immediately activate a network route
  5. Client: check Network Routes and observe they are now repropagated

Expected behavior

Network Routes to immediately propagate after reauthentication.

Are you using NetBird Cloud?

Self-hosted for testing purposes, might move to cloud in future for production

NetBird version

0.29.4
behaviour also observed on 0.29.3

NetBird status -dA output:

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS.
We advise reviewing the anonymized files for any remaining PII.

netbird.debug.256237502.zip

Screenshots

N/A

Additional context

N/A

Originally created by @Rob787 on GitHub (Sep 24, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2637 **Describe the problem** We noticed the following behaviour which is at the moment preventing us from deploying Netbird productively: The network routes seem to dissappear from Windows Peers after they've been asked to re-login (previously login expired per default setting). After reauthentication, the network routes are not updated and remain empty. The only way to get them back is by triggering a change on the network routes server side (e.g. deactivating and activating a route quickly). **To Reproduce** Steps to reproduce the behavior: 1. Reauthenticate after Netbird login expired 2. Reconnect 3. Check Network Routes of client and see they are empty 4. Server-side: Deactivate and immediately activate a network route 5. Client: check Network Routes and observe they are now repropagated **Expected behavior** Network Routes to immediately propagate after reauthentication. **Are you using NetBird Cloud?** Self-hosted for testing purposes, might move to cloud in future for production **NetBird version** 0.29.4 behaviour also observed on 0.29.3 **NetBird status -dA output:** **Do you face any (non-mobile) client issues?** Please provide the file created by `netbird debug for 1m -AS`. We advise reviewing the anonymized files for any remaining PII. [netbird.debug.256237502.zip](https://github.com/user-attachments/files/17110882/netbird.debug.256237502.zip) **Screenshots** N/A **Additional context** N/A
saavagebueno added the windowsroutestriage-needed labels 2026-08-05 01:04:35 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#5683