[GH-ISSUE #2742] Routes disappear after short time #6083

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

Originally created by @xan-it on GitHub (Oct 15, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2742

Describe the problem

We use selfhosted netbird installation. We have one PC that is behaving strangely:
After connecting to netbird, all the routes (or the one we select with the UI) are available and listed by the command "route print". We can ping private IPs from the remote site. After a while (<5 min) the routes disappear in the "route print" command and we can't ping the IPs anymore. After a restart of the netbird service the routes reappear for the next short period. A "netbird status -d" shows all remote peers as connected.

To Reproduce

Steps to reproduce the behavior:

  1. connecting to netbird
  2. use command "route print" to see network routes
  3. do a "ping -t" to an IP on the remote site
  4. after a while the ping does not work anymore
  5. check with "route print". The routes are disappeared

Expected behavior

the routes should not disappear after a while.

Are you using NetBird Cloud?

selfhosted version

NetBird version

server 0.29.3
client: we have testet it with 0.29.3 and 0.30.1

NetBird status -dA output:

Peers detail:
dxx-pve1.netbird.selfhosted:
NetBird IP: 100.97.19.116
Public key: Y5PDJ/o0hVszK+fjm9d6P8mhvYz/jTMTn7s6KFtfrnM=
Status: Connected
-- detail --
Connection type: P2P
ICE candidate (Local/Remote): host/srflx
ICE candidate endpoints (Local/Remote): 192.168.21.1:51820/198.51.100.0:51820
Relay server address: rels://netbird.anon-k3E3o.domain:443
Last connection update: 6 minutes, 17 seconds ago
Last WireGuard handshake: 10 seconds ago
Transfer status (received/sent) 17.2 KiB/17.8 KiB
Quantum resistance: false
Routes: 192.168.100.0/24
Latency: 41.0731ms

OS: windows/amd64
Daemon version: 0.30.1
CLI version: 0.30.1
Management: Connected to https://netbird.anon-k3E3o.domain:443
Signal: Connected to https://netbird.anon-k3E3o.domain:443
Relays:
[stun:netbird.anon-k3E3o.domain:3478] is Available
[turn:netbird.anon-k3E3o.domain:3478?transport=udp] is Available
[rels://netbird.anon-k3E3o.domain:443] is Available
Nameservers:
[192.168.100.102:53] for [anon-2wYrW.domain, domapor.k.anon-2wYrW.domain] is Available
FQDN: wh-pc633.netbird.selfhosted
NetBird IP: 100.97.138.222/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected

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

here are the relevant part of the debug log:
2024-10-16T12:04:49+02:00 INFO client/internal/dns/host_windows.go:149: added 3 match domains to the state. Domain list: [.anon-Ws4WY.domain .domapor.k.anon-Ws4WY.domain .netbird.selfhosted]
2024-10-16T12:04:49+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.selfhosted]
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface
2024-10-16T12:09:47+02:00 DEBG client/internal/peer/conn_monitor.go:131: Gathering ICE candidates
2024-10-16T12:09:47+02:00 DEBG client/internal/engine.go:1308: received management probe request, healthy: true

Screenshots

Additional context

Originally created by @xan-it on GitHub (Oct 15, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2742 **Describe the problem** We use selfhosted netbird installation. We have one PC that is behaving strangely: After connecting to netbird, all the routes (or the one we select with the UI) are available and listed by the command "route print". We can ping private IPs from the remote site. After a while (<5 min) the routes disappear in the "route print" command and we can't ping the IPs anymore. After a restart of the netbird service the routes reappear for the next short period. A "netbird status -d" shows all remote peers as connected. **To Reproduce** Steps to reproduce the behavior: 1. connecting to netbird 2. use command "route print" to see network routes 3. do a "ping -t" to an IP on the remote site 4. after a while the ping does not work anymore 5. check with "route print". The routes are disappeared **Expected behavior** the routes should not disappear after a while. **Are you using NetBird Cloud?** selfhosted version **NetBird version** server `0.29.3` client: we have testet it with 0.29.3 and 0.30.1 **NetBird status -dA output:** Peers detail: dxx-pve1.netbird.selfhosted: NetBird IP: 100.97.19.116 Public key: Y5PDJ/o0hVszK+fjm9d6P8mhvYz/jTMTn7s6KFtfrnM= Status: Connected -- detail -- Connection type: P2P ICE candidate (Local/Remote): host/srflx ICE candidate endpoints (Local/Remote): 192.168.21.1:51820/198.51.100.0:51820 Relay server address: rels://netbird.anon-k3E3o.domain:443 Last connection update: 6 minutes, 17 seconds ago Last WireGuard handshake: 10 seconds ago Transfer status (received/sent) 17.2 KiB/17.8 KiB Quantum resistance: false Routes: 192.168.100.0/24 Latency: 41.0731ms OS: windows/amd64 Daemon version: 0.30.1 CLI version: 0.30.1 Management: Connected to https://netbird.anon-k3E3o.domain:443 Signal: Connected to https://netbird.anon-k3E3o.domain:443 Relays: [stun:netbird.anon-k3E3o.domain:3478] is Available [turn:netbird.anon-k3E3o.domain:3478?transport=udp] is Available [rels://netbird.anon-k3E3o.domain:443] is Available Nameservers: [192.168.100.102:53] for [anon-2wYrW.domain, domapor.k.anon-2wYrW.domain] is Available FQDN: wh-pc633.netbird.selfhosted NetBird IP: 100.97.138.222/16 Interface type: Userspace Quantum resistance: false Routes: - Peers count: 1/1 Connected **Do you face any (non-mobile) client issues?** here are the relevant part of the debug log: 2024-10-16T12:04:49+02:00 INFO client/internal/dns/host_windows.go:149: added 3 match domains to the state. Domain list: [.anon-Ws4WY.domain .domapor.k.anon-Ws4WY.domain .netbird.selfhosted] 2024-10-16T12:04:49+02:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.selfhosted] 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:08:15+02:00 ERRO client/internal/routemanager/systemops/systemops_windows.go:198: Failed to parse route update: get interface name: route ip+net: no such network interface 2024-10-16T12:09:47+02:00 DEBG client/internal/peer/conn_monitor.go:131: Gathering ICE candidates 2024-10-16T12:09:47+02:00 DEBG client/internal/engine.go:1308: received management probe request, healthy: true **Screenshots** **Additional context**
saavagebueno added the waiting-feedbacktriage-needed labels 2026-08-05 01:06:36 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6083