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

after netbird up, can not conntecting to the nodes in same LAN #825

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

Originally created by @hurricane1026 on GitHub (Apr 24, 2024).

╰─λ netbird status                                                                                          0 (5.701s) < 02:11:44
Daemon version: 0.27.1
CLI version: 0.27.3
Management: Disconnected
Signal: Disconnected
Relays: 3/3 Available
Nameservers: 0/0 Available
FQDN:
NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Routes: -
Peers count: 0/0 Connected

Other status is Same As the Issue #1806

And, I install the netbird with homebrew, the daemon version is 0.27.1 is the root cause, I guess.
I download 0.27.2 manaully, and uninstall homebrew version, then it works well.

Originally created by @hurricane1026 on GitHub (Apr 24, 2024). ``` ╰─λ netbird status 0 (5.701s) < 02:11:44 Daemon version: 0.27.1 CLI version: 0.27.3 Management: Disconnected Signal: Disconnected Relays: 3/3 Available Nameservers: 0/0 Available FQDN: NetBird IP: N/A Interface type: N/A Quantum resistance: false Routes: - Peers count: 0/0 Connected ``` Other status is Same As the Issue #1806 And, I install the netbird with homebrew, the daemon version is 0.27.1 is the root cause, I guess. I download 0.27.2 manaully, and uninstall homebrew version, then it works well.
saavagebueno added the triage-needed label 2025-11-20 05:18:04 -05:00
saavagebueno commented 2025-11-20 05:18:04 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 24, 2024):

I wonder why the daemon version is 0.27.1, I guess the version is buggy for routing in same LAN.

@hurricane1026 commented on GitHub (Apr 24, 2024): I wonder why the daemon version is 0.27.1, I guess the version is buggy for routing in same LAN.
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 24, 2024):

this is my linux servers
netbird status' output:

~> netbird status
Daemon version: 0.27.3
CLI version: 0.27.3
Management: Connected
Signal: Connected
Relays: 3/3 Available
Nameservers: 0/0 Available
FQDN: leopard.stdb.node
NetBird IP: 100.102.178.139/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 6/48 Connected
hurricane@leopard ~>
@hurricane1026 commented on GitHub (Apr 24, 2024): this is my linux servers netbird status' output: ``` ~> netbird status Daemon version: 0.27.3 CLI version: 0.27.3 Management: Connected Signal: Connected Relays: 3/3 Available Nameservers: 0/0 Available FQDN: leopard.stdb.node NetBird IP: 100.102.178.139/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 6/48 Connected hurricane@leopard ~> ```
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 24, 2024):

I guess the bug is a result of incorrect packaging.

@hurricane1026 commented on GitHub (Apr 24, 2024): I guess the bug is a result of incorrect packaging.
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@taylorwilsdon commented on GitHub (Apr 24, 2024):

I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? netbird up

Management: Disconnected
Signal: Disconnected
Peers count: 0/0 Connected
@taylorwilsdon commented on GitHub (Apr 24, 2024): I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? `netbird up` ``` Management: Disconnected Signal: Disconnected Peers count: 0/0 Connected ```
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 24, 2024):

I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? netbird up


Management: Disconnected

Signal: Disconnected

Peers count: 0/0 Connected

if I make netbird up, my proxy is broken, then I can not post my issue to github, so I said my status is same as #1806

@hurricane1026 commented on GitHub (Apr 24, 2024): > I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? `netbird up` > > > > ``` > > Management: Disconnected > > Signal: Disconnected > > Peers count: 0/0 Connected > > ``` if I make netbird up, my proxy is broken, then I can not post my issue to github, so I said my status is same as #1806
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 24, 2024):

I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? netbird up

Management: Disconnected
Signal: Disconnected
Peers count: 0/0 Connected

Please read my post again carefully, I add some more details.

@hurricane1026 commented on GitHub (Apr 24, 2024): > I don't see any bug, you're just not connected - your initial netbird status shows a mismatched daemon and cli version (should have both on the same) but you're not seeing anything because you aren't connected at all and don't have a netbird IP or any peers. Have you confirmed that the /etc/netbird/config.json has the appropriate values for your deployment and that you've even attempted to connect? `netbird up` > > ``` > Management: Disconnected > Signal: Disconnected > Peers count: 0/0 Connected > ``` Please read my post again carefully, I add some more details.
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@jiangslee commented on GitHub (Apr 25, 2024):

The strange thing is that daemon version is still 0.27.1

╰─λ netbird status                                                                                          0 (5.701s) < 02:11:44
Daemon version: 0.27.1
CLI version: 0.27.3

And, I install the netbird with homebrew, the daemon version is 0.27.1 is the root cause, I guess.
I download 0.27.2 manaully, and uninstall homebrew version, then it works well.
@jiangslee commented on GitHub (Apr 25, 2024): The strange thing is that daemon version is still 0.27.1 ``` ╰─λ netbird status 0 (5.701s) < 02:11:44 Daemon version: 0.27.1 CLI version: 0.27.3 And, I install the netbird with homebrew, the daemon version is 0.27.1 is the root cause, I guess. I download 0.27.2 manaully, and uninstall homebrew version, then it works well. ```
saavagebueno commented 2025-11-20 05:18:05 -05:00
Author
Owner
Copy Link

@hurricane1026 commented on GitHub (Apr 25, 2024):

maybe "brew update" didn't kill daemon, and complete the replacement?

@hurricane1026 commented on GitHub (Apr 25, 2024): maybe "brew update" didn't kill daemon, and complete the replacement?
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#825
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?