SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-02 20:22:23 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Windows client connection breaks every ten seconds because of a detected network change #1133

New Issue
Closed
opened 2025-11-20 05:24:35 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:24:35 -05:00
Owner
Copy Link

Originally created by @trgaming on GitHub (Aug 5, 2024).

Describe the problem

The connection from a Windows client is not working properly. The client connects and soon after looses its connection because of a detected network change.

Expected behavior

The wrong network change is not detected.

Are you using NetBird Cloud?

selfhosted

NetBird version

0.28.7

Additional context

The connections gets broken because a network change is detected. The interface "LAN-Verbindung* 3" is the Microsoft Wi-Fi Direct Virtual Adapter which is repsonsible for wifi sharing. I do not understand why Netbird detects this interface for the gateway 10.0.0.1.

I tried to uninstall this interface and then the connnection works perfectly fine but windows installs this device again at the next startup.

netbird up --network-monitor=false solves the problem as well.

route print output:
Schnittstellenliste
13...30 e1 71 27 6a f2 ......Realtek PCIe FE Family Controller #2
2...2a 56 5a 44 66 1b ......Microsoft Wi-Fi Direct Virtual Adapter
4...28 56 5a 44 66 1b ......Microsoft Wi-Fi Direct Virtual Adapter #2
17...28 56 5a 44 66 1b ......Realtek RTL8723BE 802.11 bgn Wi-Fi Adapter
1...........................Software Loopback Interface 1

2024-08-05T21:52:24+02:00 DEBG [nameservers: [{100.123.250.18 udp 53}]] client/internal/dns/server.go:548: reactivate temporary disabled nameserver group
2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:111: configured 100.123.255.254:53 as main DNS forwarder for this peer
2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.intern.anon-cjTcc.domain]
2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [intern.anon-cjTcc.domain]
2024-08-05T21:52:25+02:00 INFO client/internal/dns/upstream.go:252: upstreams [100.123.250.18:54] are responsive again. Adding them back to system
2024-08-05T21:52:25+02:00 DEBG [nameservers: [{100.123.250.18 udp 54}]] client/internal/dns/server.go:548: reactivate temporary disabled nameserver group
2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:111: configured 100.123.255.254:53 as main DNS forwarder for this peer
2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:149: added 2 match domains to the state. Domain list: [.wawi-srv.anon-LiZOa.domain .intern.anon-cjTcc.domain]
2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [intern.anon-cjTcc.domain]
2024-08-05T21:52:30+02:00 DEBG client/internal/engine.go:1429: received management probe request, healthy: true
2024-08-05T21:52:30+02:00 DEBG client/internal/engine.go:1421: received signal probe request, healthy: true
2024-08-05T21:52:31+02:00 DEBG util/net/dialer_nonios.go:114: Dialer resolved IPs for nw.anon-cjTcc.domain:3478: [{198.51.100.3 }]
2024-08-05T21:52:31+02:00 DEBG client/internal/relay/relay.go:66: stun probe received address from stun:nw.anon-cjTcc.domain:3478: 198.51.100.4:49223
2024-08-05T21:52:31+02:00 INFO client/internal/networkmonitor/monitor_windows.go:159: network monitor: default route for 10.0.0.1 (LAN-Verbindung* 3) is gone or changed
2024-08-05T21:52:32+02:00 INFO client/internal/engine.go:1520: Network monitor detected network change, restarting engine
2024-08-05T21:52:32+02:00 INFO client/internal/engine.go:252: Network monitor: stopped

Originally created by @trgaming on GitHub (Aug 5, 2024). **Describe the problem** The connection from a Windows client is not working properly. The client connects and soon after looses its connection because of a detected network change. **Expected behavior** The wrong network change is not detected. **Are you using NetBird Cloud?** selfhosted **NetBird version** `0.28.7` **Additional context** The connections gets broken because a network change is detected. The interface "LAN-Verbindung* 3" is the Microsoft Wi-Fi Direct Virtual Adapter which is repsonsible for wifi sharing. I do not understand why Netbird detects this interface for the gateway 10.0.0.1. I tried to uninstall this interface and then the connnection works perfectly fine but windows installs this device again at the next startup. `netbird up --network-monitor=false` solves the problem as well. `route print` output: Schnittstellenliste 13...30 e1 71 27 6a f2 ......Realtek PCIe FE Family Controller #2 2...2a 56 5a 44 66 1b ......Microsoft Wi-Fi Direct Virtual Adapter 4...28 56 5a 44 66 1b ......Microsoft Wi-Fi Direct Virtual Adapter #2 17...28 56 5a 44 66 1b ......Realtek RTL8723BE 802.11 bgn Wi-Fi Adapter 1...........................Software Loopback Interface 1 2024-08-05T21:52:24+02:00 DEBG [nameservers: [{100.123.250.18 udp 53}]] client/internal/dns/server.go:548: reactivate temporary disabled nameserver group 2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:111: configured 100.123.255.254:53 as main DNS forwarder for this peer 2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.intern.anon-cjTcc.domain] 2024-08-05T21:52:24+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [intern.anon-cjTcc.domain] 2024-08-05T21:52:25+02:00 INFO client/internal/dns/upstream.go:252: upstreams [100.123.250.18:54] are responsive again. Adding them back to system 2024-08-05T21:52:25+02:00 DEBG [nameservers: [{100.123.250.18 udp 54}]] client/internal/dns/server.go:548: reactivate temporary disabled nameserver group 2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:111: configured 100.123.255.254:53 as main DNS forwarder for this peer 2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:149: added 2 match domains to the state. Domain list: [.wawi-srv.anon-LiZOa.domain .intern.anon-cjTcc.domain] 2024-08-05T21:52:25+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [intern.anon-cjTcc.domain] 2024-08-05T21:52:30+02:00 DEBG client/internal/engine.go:1429: received management probe request, healthy: true 2024-08-05T21:52:30+02:00 DEBG client/internal/engine.go:1421: received signal probe request, healthy: true 2024-08-05T21:52:31+02:00 DEBG util/net/dialer_nonios.go:114: Dialer resolved IPs for nw.anon-cjTcc.domain:3478: [{198.51.100.3 }] 2024-08-05T21:52:31+02:00 DEBG client/internal/relay/relay.go:66: stun probe received address from stun:nw.anon-cjTcc.domain:3478: 198.51.100.4:49223 2024-08-05T21:52:31+02:00 INFO client/internal/networkmonitor/monitor_windows.go:159: network monitor: default route for 10.0.0.1 (LAN-Verbindung* 3) is gone or changed 2024-08-05T21:52:32+02:00 INFO client/internal/engine.go:1520: Network monitor detected network change, restarting engine 2024-08-05T21:52:32+02:00 INFO client/internal/engine.go:252: Network monitor: stopped
saavagebueno added the clientwindowsnetworking labels 2025-11-20 05:24:35 -05:00
saavagebueno commented 2025-11-20 05:24:36 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Aug 5, 2024):

Hi @trgaming,

thanks for the report.
It seems the default route that points to the virtual interface doesn't turn up when retrieving routes via the windows API, hence a change is detected. We'll work on a fix soon.

@lixmal commented on GitHub (Aug 5, 2024): Hi @trgaming, thanks for the report. It seems the default route that points to the virtual interface doesn't turn up when retrieving routes via the windows API, hence a change is detected. We'll work on a fix soon.
saavagebueno commented 2025-11-20 05:24:36 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Aug 19, 2024):

Hi @trgaming, @Takalele,

can you test the network monitor change from https://github.com/netbirdio/netbird/pull/2450?

  1. Grab the binary archive from https://github.com/netbirdio/netbird/actions/runs/10459247214/artifacts/1829061085
  2. Extract windows-packages.zip
netbird service stop
netbird service uninstall

  1. Move netbird.exe from the zip archive to %PROGRAMFILES%/Netbird

netbird service install
netbird service start
netbird down
netbird up --network-monitor=true
@lixmal commented on GitHub (Aug 19, 2024): Hi @trgaming, @Takalele, can you test the network monitor change from https://github.com/netbirdio/netbird/pull/2450? 1. Grab the binary archive from https://github.com/netbirdio/netbird/actions/runs/10459247214/artifacts/1829061085 2. Extract `windows-packages.zip` 3. ``` netbird service stop netbird service uninstall ``` 4. Move `netbird.exe` from the zip archive to `%PROGRAMFILES%/Netbird` 5. ``` netbird service install netbird service start netbird down netbird up --network-monitor=true ```
saavagebueno commented 2025-11-20 05:24:36 -05:00
Author
Owner
Copy Link

@trgaming commented on GitHub (Aug 20, 2024):

Hi @lixmal ,

Thanks for your reply.

I already tried to but your link gives me a 404 status from GitHub. Please check if the link is still active.

Thanks and best regards
Tim

@trgaming commented on GitHub (Aug 20, 2024): Hi @lixmal , Thanks for your reply. I already tried to but your link gives me a 404 status from GitHub. Please check if the link is still active. Thanks and best regards Tim
saavagebueno commented 2025-11-20 05:24:37 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Aug 20, 2024):

Hello @trgaming you can try this new build link now: https://github.com/netbirdio/netbird/actions/runs/10475047026/artifacts/1833430698

You will need to be authenticated to Github to download it.

@mlsmaycon commented on GitHub (Aug 20, 2024): Hello @trgaming you can try this new build link now: https://github.com/netbirdio/netbird/actions/runs/10475047026/artifacts/1833430698 You will need to be authenticated to Github to download it.
saavagebueno commented 2025-11-20 05:24:37 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Aug 20, 2024):

@trgaming, let us know if you have had the chance to evaluate this.

@mlsmaycon commented on GitHub (Aug 20, 2024): @trgaming, let us know if you have had the chance to evaluate this.
saavagebueno commented 2025-11-20 05:24:37 -05:00
Author
Owner
Copy Link

@Takalele commented on GitHub (Aug 20, 2024):

@lixmal @mlsmaycon

It works, the connection is stable.

netbird up --network-monitor=true
Please do the SSO login in your browser.

Connected

netbird status
OS: windows/amd64
Daemon version: 0.28.7-SNAPSHOT-4fc79ab0
CLI version: 0.28.7-SNAPSHOT-4fc79ab0
Management: Connected
Signal: Connected
Relays: 2/2 Available
Nameservers: 1/1 Available
FQDN: voyager-1.netbird.selfhosted
NetBird IP: 100.105.102.132/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 2/2 Connected

BR
Takalele

@Takalele commented on GitHub (Aug 20, 2024): @lixmal @mlsmaycon It works, the connection is stable. ``` netbird up --network-monitor=true Please do the SSO login in your browser. Connected netbird status OS: windows/amd64 Daemon version: 0.28.7-SNAPSHOT-4fc79ab0 CLI version: 0.28.7-SNAPSHOT-4fc79ab0 Management: Connected Signal: Connected Relays: 2/2 Available Nameservers: 1/1 Available FQDN: voyager-1.netbird.selfhosted NetBird IP: 100.105.102.132/16 Interface type: Userspace Quantum resistance: false Routes: - Peers count: 2/2 Connected ``` BR Takalele
saavagebueno commented 2025-11-20 05:24:37 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Aug 20, 2024):

Great, thanks for the feedback. This fix will come in the next release. From tonight.

@mlsmaycon commented on GitHub (Aug 20, 2024): Great, thanks for the feedback. This fix will come in the next release. From tonight.
saavagebueno commented 2025-11-20 05:24:37 -05:00
Author
Owner
Copy Link

@trgaming commented on GitHub (Aug 30, 2024):

Hi @mlsmaycon,
sorry, I was not able to test because I had no access to the device (it is a pc at a warehouse).

I updated to 0.28.9 and the issue seems to be gone after setting network monitor to true again.

Thanks for the quick solution.

@trgaming commented on GitHub (Aug 30, 2024): Hi @mlsmaycon, sorry, I was not able to test because I had no access to the device (it is a pc at a warehouse). I updated to 0.28.9 and the issue seems to be gone after setting network monitor to true again. Thanks for the quick solution.
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 client networking windows
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#1133
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?