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

Issue: Newer NetBird Version (0.57.0) Fails to Display Peer Latency, While Older Version (0.55.1) Works Normally #2281

New Issue
Open
opened 2025-11-20 07:06:57 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:06:57 -05:00
Owner
Copy Link

Originally created by @1350962574 on GitHub (Sep 14, 2025).

Originally assigned to: @pappz on GitHub.

Issue: NetBird 0.57.0 Fails to Display Peer Latency (Shows 0s), While 0.55.1 Works Normally

Describe the problem

When using NetBird client version 0.57.0 on a macOS (arm64) device, executing netbird status --yaml --filter-by-status connected | grep latency returns latency: 0s for all connected peers, preventing visibility of actual network latency between peers. In contrast, NetBird version 0.55.1 on a Linux (arm64) device correctly outputs realistic latency values (e.g., 23.654929ms, 20.460773ms) when running the same command. This confirms the latency reporting issue is specific to the 0.57.0 version.

To Reproduce

Steps to reproduce the behavior:

  1. Install NetBird 0.57.0 on a macOS (arm64) device.
  2. Ensure the device connects to the NetBird network (verify via netbird status showing "Peers count: X/Y Connected" where X > 0).
  3. Run the terminal command: netbird status --yaml --filter-by-status connected | grep latency.
  4. Observe that all latency entries return latency: 0s (no valid millisecond values).
  5. For comparison: Install NetBird 0.55.1 on a Linux (arm64) device, repeat steps 2–3, and confirm non-zero, realistic latency values are displayed.

Expected behavior

When executing netbird status --yaml --filter-by-status connected | grep latency on NetBird 0.57.0, the output should show actual, non-zero latency values (in milliseconds) for each connected peer—consistent with the correct behavior of the 0.55.1 version.

Are you using NetBird Cloud?

The control plane type (NetBird Cloud / self-hosted) is consistent across both versions (no changes made between tests; specific type not modified).

NetBird version

  • Affected device (macOS arm64): 0.57.0 (Daemon: 0.57.0, CLI: 0.57.0)
  • Working device (Linux arm64): 0.55.1 (Daemon: 0.55.1, CLI: 0.55.1)

Is any other VPN software installed?

No other VPN software is installed on either the macOS (0.57.0) or Linux (0.55.1) device.

Debug output

1. Anonymized netbird status -dA Output

macOS (0.57.0, affected):

bash

admin@MacBookAir ~ % netbird version
0.57.0
admin@MacBookAir ~ % 
admin@MacBookAir ~ % netbird status 
OS: darwin/arm64
Daemon version: 0.57.0
CLI version: 0.57.0
Profile: default
Management: Connected
Signal: Connected
Relays: 2/2 Available
Nameservers: 0/0 Available
FQDN: macbookair.sdw.local
NetBird IP: 100.119.215.29/16
Interface type: Userspace
Quantum resistance: false
Lazy connection: false
Networks: -
Forwarding rules: 0
Peers count: 19/32 Connected
admin@MacBookAir ~ % netbird status  --yaml  --filter-by-status connected   |grep   latency
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
          latency: 0s
admin@MacBookAir ~ %

bash

root@rock3399:~# netbird version
0.55.1
root@rock3399:~# 
root@rock3399:~# netbird status 
OS: linux/arm64
Daemon version: 0.55.1
CLI version: 0.55.1
Profile: default
Management: Connected
Signal: Connected
Relays: 2/2 Available
Nameservers: 0/0 Available
FQDN: bangongshi-rk3399.sdw.local
NetBird IP: 100.119.220.134/16
Interface type: Kernel
Quantum resistance: false
Lazy connection: false
Networks: 172.16.1.0/24
Forwarding rules: 0
Peers count: 20/32 Connected
root@rock3399:~# netbird status  --yaml  --filter-by-status connected   |grep   latency
          latency: 23.654929ms
          latency: 0s
          latency: 20.460773ms
          latency: 7.930408ms
          latency: 6.414854ms
          latency: 33.279605ms
          latency: 22.269879ms
          latency: 27.234765ms
          latency: 37.4718ms
          latency: 35.476475ms
          latency: 45.428375ms
          latency: 27.401896ms
          latency: 4.147356ms
          latency: 0s
          latency: 19.966171ms
          latency: 8.115039ms
          latency: 8.669518ms
          latency: 7.750152ms
          latency: 31.0254ms
          latency: 49.285802ms
root@rock3399:~#

Screenshots

Not applicable (issue manifests in text-based CLI output; relevant logs are provided above).

Additional context

  • The macOS 0.57.0 device uses the Userspace interface type, while the Linux 0.55.1 device uses Kernel—this difference is unlikely to cause latency reporting failure (latency should be measurable regardless of interface type).
  • Both devices are on the same NetBird network with similar peer connectivity (19/32 vs. 20/32 connected), ruling out network isolation or peer reachability issues.
  • No changes to firewall settings, network environment, or NetBird configuration were made between testing the two versions.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions (0.57.0 is the latest as of testing)
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client (multiple times on macOS 0.57.0)
  • Disabled other VPN software (no other VPNs installed)
  • Checked firewall settings (no blocks on NetBird traffic)
Originally created by @1350962574 on GitHub (Sep 14, 2025). Originally assigned to: @pappz on GitHub. # Issue: NetBird 0.57.0 Fails to Display Peer Latency (Shows 0s), While 0.55.1 Works Normally ## **Describe the problem** When using NetBird client version **0.57.0** on a macOS (arm64) device, executing `netbird status --yaml --filter-by-status connected | grep latency` returns `latency: 0s` for all connected peers, preventing visibility of actual network latency between peers. In contrast, NetBird version **0.55.1** on a Linux (arm64) device correctly outputs realistic latency values (e.g., `23.654929ms`, `20.460773ms`) when running the same command. This confirms the latency reporting issue is specific to the 0.57.0 version. ## **To Reproduce** Steps to reproduce the behavior: 1. Install NetBird **0.57.0** on a macOS (arm64) device. 2. Ensure the device connects to the NetBird network (verify via `netbird status` showing "Peers count: X/Y Connected" where X > 0). 3. Run the terminal command: `netbird status --yaml --filter-by-status connected | grep latency`. 4. Observe that all latency entries return `latency: 0s` (no valid millisecond values). 5. For comparison: Install NetBird **0.55.1** on a Linux (arm64) device, repeat steps 2–3, and confirm non-zero, realistic latency values are displayed. ## **Expected behavior** When executing `netbird status --yaml --filter-by-status connected | grep latency` on NetBird 0.57.0, the output should show actual, non-zero latency values (in milliseconds) for each connected peer—consistent with the correct behavior of the 0.55.1 version. ## **Are you using NetBird Cloud?** The control plane type (NetBird Cloud / self-hosted) is consistent across both versions (no changes made between tests; specific type not modified). ## **NetBird version** * Affected device (macOS arm64): `0.57.0` (Daemon: 0.57.0, CLI: 0.57.0) * Working device (Linux arm64): `0.55.1` (Daemon: 0.55.1, CLI: 0.55.1) ## **Is any other VPN software installed?** No other VPN software is installed on either the macOS (0.57.0) or Linux (0.55.1) device. ## **Debug output** ### 1. Anonymized `netbird status -dA` Output #### macOS (0.57.0, affected): bash ```bash admin@MacBookAir ~ % netbird version 0.57.0 admin@MacBookAir ~ % admin@MacBookAir ~ % netbird status OS: darwin/arm64 Daemon version: 0.57.0 CLI version: 0.57.0 Profile: default Management: Connected Signal: Connected Relays: 2/2 Available Nameservers: 0/0 Available FQDN: macbookair.sdw.local NetBird IP: 100.119.215.29/16 Interface type: Userspace Quantum resistance: false Lazy connection: false Networks: - Forwarding rules: 0 Peers count: 19/32 Connected admin@MacBookAir ~ % netbird status --yaml --filter-by-status connected |grep latency latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s latency: 0s admin@MacBookAir ~ % ``` bash ```bash root@rock3399:~# netbird version 0.55.1 root@rock3399:~# root@rock3399:~# netbird status OS: linux/arm64 Daemon version: 0.55.1 CLI version: 0.55.1 Profile: default Management: Connected Signal: Connected Relays: 2/2 Available Nameservers: 0/0 Available FQDN: bangongshi-rk3399.sdw.local NetBird IP: 100.119.220.134/16 Interface type: Kernel Quantum resistance: false Lazy connection: false Networks: 172.16.1.0/24 Forwarding rules: 0 Peers count: 20/32 Connected root@rock3399:~# netbird status --yaml --filter-by-status connected |grep latency latency: 23.654929ms latency: 0s latency: 20.460773ms latency: 7.930408ms latency: 6.414854ms latency: 33.279605ms latency: 22.269879ms latency: 27.234765ms latency: 37.4718ms latency: 35.476475ms latency: 45.428375ms latency: 27.401896ms latency: 4.147356ms latency: 0s latency: 19.966171ms latency: 8.115039ms latency: 8.669518ms latency: 7.750152ms latency: 31.0254ms latency: 49.285802ms root@rock3399:~# ``` ## **Screenshots** Not applicable (issue manifests in text-based CLI output; relevant logs are provided above). ## **Additional context** * The macOS 0.57.0 device uses the **Userspace** interface type, while the Linux 0.55.1 device uses **Kernel**—this difference is unlikely to cause latency reporting failure (latency should be measurable regardless of interface type). * Both devices are on the same NetBird network with similar peer connectivity (19/32 vs. 20/32 connected), ruling out network isolation or peer reachability issues. * No changes to firewall settings, network environment, or NetBird configuration were made between testing the two versions. ## **Have you tried these troubleshooting steps?** * [X] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) * [X] Checked for newer NetBird versions (0.57.0 is the latest as of testing) * [X] Searched for similar issues on GitHub (including closed ones) * [X] Restarted the NetBird client (multiple times on macOS 0.57.0) * [X] Disabled other VPN software (no other VPNs installed) * [X] Checked firewall settings (no blocks on NetBird traffic)
saavagebueno added the bugpeer-managementclient labels 2025-11-20 07:06:57 -05:00
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 bug client peer-management
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#2281
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?