SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-13 11:41:58 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Windows clients do not install the configured network routes received by the routing peers #675

New Issue
Closed
opened 2025-11-20 05:15:50 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:15:50 -05:00
Owner
Copy Link

Originally created by @sikz1 on GitHub (Mar 3, 2024).

Describe the problem

There are times when Windows (10 and 11) clients do not install a network route even though the routing peers are active and connected.

To Reproduce

netbird up -F -l debug

Expected behavior

The client connects and gets the network routes configured for the distribution group it belongs to.

Are you using NetBird Cloud?

No, self-hosted.

NetBird version

Netbird 0.26.2 client on Windows 10 and Windows 11.
Latest docker images for management, signal, dashboard and coturn.

Additional context

This is a redacted excerpt from the logs. The client seems to recognize the peers as active but when it comes to install the network route it doesn't because "no peers from the list [ ... ] are connected". The dashboard shows them as connected and the client itself can ping them.

2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection ODtmkq...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection RkGlyC...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection zTi4Aa...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection iNK5f9...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection AQit75...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection qqakhb...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection dn/HnX...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection kzowTU...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection yerMeJ...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection IEuf0M...
2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection 1G9dqR...
2024-03-01T17:19:59+01:00 DEBG client/internal/routemanager/client.go:284: received a new client network route update for 10.128.0.0/9
2024-03-01T17:19:59+01:00 DEBG client/internal/dns/service_memory.go:51: dns service listening on: 100.104.255.254
2024-03-01T17:19:59+01:00 WARN client/internal/routemanager/client.go:121: the network 10.128.0.0/9 has not been assigned a routing peer as no peers from the list [iNK5f9... kzowTU...] are currently connected

Originally created by @sikz1 on GitHub (Mar 3, 2024). **Describe the problem** There are times when Windows (10 and 11) clients do not install a network route even though the routing peers are active and connected. **To Reproduce** netbird up -F -l debug **Expected behavior** The client connects and gets the network routes configured for the distribution group it belongs to. **Are you using NetBird Cloud?** No, self-hosted. **NetBird version** Netbird 0.26.2 client on Windows 10 and Windows 11. Latest docker images for management, signal, dashboard and coturn. **Additional context** This is a redacted excerpt from the logs. The client seems to recognize the peers as active but when it comes to install the network route it doesn't because "no peers from the list [ ... ] are connected". The dashboard shows them as connected and the client itself can ping them. 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection ODtmkq... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection RkGlyC... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection zTi4Aa... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection iNK5f9... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection AQit75... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection qqakhb... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection dn/HnX... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection kzowTU... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection yerMeJ... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection IEuf0M... 2024-03-01T17:19:59+01:00 DEBG client/internal/engine.go:866: creating peer connection 1G9dqR... 2024-03-01T17:19:59+01:00 DEBG client/internal/routemanager/client.go:284: received a new client network route update for 10.128.0.0/9 2024-03-01T17:19:59+01:00 DEBG client/internal/dns/service_memory.go:51: dns service listening on: 100.104.255.254 2024-03-01T17:19:59+01:00 WARN client/internal/routemanager/client.go:121: the network 10.128.0.0/9 has not been assigned a routing peer as no peers from the list [iNK5f9... kzowTU...] are currently connected
saavagebueno added the triage-needed label 2025-11-20 05:15:50 -05:00
saavagebueno commented 2025-11-20 05:15:51 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Mar 3, 2024):

Does the peer also show connected in netbird status -d?

@lixmal commented on GitHub (Mar 3, 2024): Does the peer also show connected in `netbird status -d`?
saavagebueno commented 2025-11-20 05:15:51 -05:00
Author
Owner
Copy Link

@sikz1 commented on GitHub (Mar 6, 2024):

It actually wasn't. Apparently, netbird creates the connections upfront and then tries to bring them on later. Thus, when the message with the network routes is received, no peer is actually connected and a warning message is logged.

Going to close the issue, looks like this is normal behaviour.

@sikz1 commented on GitHub (Mar 6, 2024): It actually wasn't. Apparently, netbird creates the connections upfront and then tries to bring them on later. Thus, when the message with the network routes is received, no peer is actually connected and a warning message is logged. Going to close the issue, looks like this is normal behaviour.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#675
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?