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

macOS cannot connect to other peers in the local network after upgrade to 0.27 #782

New Issue
Closed
opened 2025-11-20 05:17:28 -05:00 by saavagebueno · 11 comments
saavagebueno commented 2025-11-20 05:17:28 -05:00
Owner
Copy Link

Originally created by @y1xia0w on GitHub (Apr 5, 2024).

Describe the problem

macOS CANNOT connect to other peers in the same local network after netbird up, but CAN connect to peers not in the same LAN.

I have machine A, B, and mac in the same LAN with the LAN IP as below, another machine C is in the office in another place, not in the same LAN.

A: 192.168.111.199
B: 192.168.111.190
mac: 192.168.111.10

Netbird 0.26.3 has been installed on A, B, and C (Machine A, B, and C are all running Ubuntu 22.04)
Netbird 0.27.1 installed on mac (Sonoma 14.4.1)

After running netbird up on mac, the mac cannot connect to A, B neither via LAN IP address nor netbird IP address, meanwhile it even cannot ping machine A, B. But, machine A and B could ping and connect to each other via both LAN IP and netbird IP properly as expected.

The behavior of the ping drop is as below. The left pane is the log on mac, the right pane is the log of mac pinging A. It seems only when mac runs the conn.go it can establish connection to peer A.

Screenshot 2024-04-05 at 10 38 12

However, after running netbird up on mac, the mac can connect to C which is not in the same LAN properly.

To Reproduce

Run command brew install netbird-ui on mac to install the netbird-ui.
Run command sudo apt install netbird on Ubuntu 22.04 to install netbird.
Run command netbird up on each machine and login via SSO.
Then, the connection between peers in the same LAN drops.

Expected behavior

Netbird on macOS can connect to peers in local network via both local IP address and netbird IP address.

Are you using NetBird Cloud?

Yes

NetBird version

macOS 0.27.1
others 0.26.3

NetBird status -d output:

Peers detail:
 A.netbird.cloud:
  NetBird IP: 100.99.*
  Public key: *
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): srflx/host
  ICE candidate endpoints (Local/Remote): WAN IP:1871/192.168.111.199:1871
  Last connection update: 2024-04-05 11:19:40
  Last WireGuard handshake: -
  Transfer status (received/sent) 148 B/388 B
  Quantum resistance: false
  Routes: -
  Latency: 4.34775ms

C.netbird.cloud:
  NetBird IP: 100.99.*
  Public key: *
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: true
  ICE candidate (Local/Remote): host/relay
  ICE candidate endpoints (Local/Remote): 192.168.111.10:51820/WAN IP:51820
  Last connection update: 2024-04-05 11:09:40
  Last WireGuard handshake: 2024-04-05 11:18:01
  Transfer status (received/sent) 492 B/1.6 KiB
  Quantum resistance: false
  Routes: -
  Latency: 162.714542ms

B.netbird.cloud:
  NetBird IP: 100.99.*
  Public key: *
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): host/host
  ICE candidate endpoints (Local/Remote): 192.168.111.10:51820/192.168.111.190:51820
  Last connection update: 2024-04-05 11:22:52
  Last WireGuard handshake: -
  Transfer status (received/sent) 148 B/388 B
  Quantum resistance: false
  Routes: -
  Latency: 6.517333ms

Daemon version: 0.27.1
CLI version: 0.27.1
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays:
  [stun:stun.netbird.io:5555] is Available
  [turns:turn.netbird.io:443?transport=tcp] is Available
Nameservers:
FQDN: mac.netbird.cloud
NetBird IP: 100.99.*
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 4/7 Connected

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Originally created by @y1xia0w on GitHub (Apr 5, 2024). **Describe the problem** macOS CANNOT connect to other peers in the same local network after `netbird up`, but CAN connect to peers not in the same LAN. I have machine A, B, and mac in the same LAN with the LAN IP as below, another machine C is in the office in another place, not in the same LAN. ``` A: 192.168.111.199 B: 192.168.111.190 mac: 192.168.111.10 ``` Netbird 0.26.3 has been installed on A, B, and C (Machine A, B, and C are all running Ubuntu 22.04) Netbird 0.27.1 installed on mac (Sonoma 14.4.1) After running `netbird up` on mac, the mac cannot connect to A, B neither via LAN IP address nor netbird IP address, meanwhile it even cannot ping machine A, B. But, machine A and B could ping and connect to each other via both LAN IP and netbird IP properly as expected. The behavior of the ping drop is as below. The left pane is the log on mac, the right pane is the log of mac pinging A. It seems only when mac runs the `conn.go` it can establish connection to peer A. <img width="1484" alt="Screenshot 2024-04-05 at 10 38 12" src="https://github.com/netbirdio/netbird/assets/50680028/a05303ec-16db-4653-bbd6-16ef0611acb4"> However, after running `netbird up` on mac, the mac can connect to C which is not in the same LAN properly. **To Reproduce** Run command `brew install netbird-ui` on mac to install the netbird-ui. Run command `sudo apt install netbird` on Ubuntu 22.04 to install netbird. Run command `netbird up` on each machine and login via SSO. Then, the connection between peers in the same LAN drops. **Expected behavior** Netbird on macOS can connect to peers in local network via both local IP address and netbird IP address. **Are you using NetBird Cloud?** Yes **NetBird version** macOS `0.27.1` others `0.26.3` **NetBird status -d output:** ``` Peers detail: A.netbird.cloud: NetBird IP: 100.99.* Public key: * Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): srflx/host ICE candidate endpoints (Local/Remote): WAN IP:1871/192.168.111.199:1871 Last connection update: 2024-04-05 11:19:40 Last WireGuard handshake: - Transfer status (received/sent) 148 B/388 B Quantum resistance: false Routes: - Latency: 4.34775ms C.netbird.cloud: NetBird IP: 100.99.* Public key: * Status: Connected -- detail -- Connection type: Relayed Direct: true ICE candidate (Local/Remote): host/relay ICE candidate endpoints (Local/Remote): 192.168.111.10:51820/WAN IP:51820 Last connection update: 2024-04-05 11:09:40 Last WireGuard handshake: 2024-04-05 11:18:01 Transfer status (received/sent) 492 B/1.6 KiB Quantum resistance: false Routes: - Latency: 162.714542ms B.netbird.cloud: NetBird IP: 100.99.* Public key: * Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): host/host ICE candidate endpoints (Local/Remote): 192.168.111.10:51820/192.168.111.190:51820 Last connection update: 2024-04-05 11:22:52 Last WireGuard handshake: - Transfer status (received/sent) 148 B/388 B Quantum resistance: false Routes: - Latency: 6.517333ms Daemon version: 0.27.1 CLI version: 0.27.1 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Available [turns:turn.netbird.io:443?transport=tcp] is Available Nameservers: FQDN: mac.netbird.cloud NetBird IP: 100.99.* Interface type: Userspace Quantum resistance: false Routes: - Peers count: 4/7 Connected ``` **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
saavagebueno added the agent label 2025-11-20 05:17:28 -05:00
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@y1xia0w commented on GitHub (Apr 5, 2024):

Downgrade to netbird 0.26.3 using the previous brew formula won't have this connection issue for mac. However, both 0.27.0 and 0.27.1 have the issue.

@y1xia0w commented on GitHub (Apr 5, 2024): Downgrade to netbird 0.26.3 using [the previous brew formula](https://github.com/netbirdio/homebrew-tap/tree/47c294b9fedc64d0d676d707ffef106ff5463fd1) won't have this connection issue for mac. However, both 0.27.0 and 0.27.1 have the issue.
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@pappz commented on GitHub (Apr 8, 2024):

Hello!

Thank you for the detailed report. We localized the root cause of the issue and we are working on the solution.

@pappz commented on GitHub (Apr 8, 2024): Hello! Thank you for the detailed report. We localized the root cause of the issue and we are working on the solution.
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@bhavitsharma commented on GitHub (Apr 8, 2024):

I ran into a problem that sounds a lot like yours. I've got three devices connected to the same "netbird network," and one of them is an SSH server. For some reason, only one device on my network was able to connect to that server.

I tried using ping and traceroute to reach the server's DNS name and IP address, but it didn't work (nslookup was working).
So, I decided to downgrade to version 0.26.6, and now all my devices can reach the SSH server in my netbird network.

@bhavitsharma commented on GitHub (Apr 8, 2024): I ran into a problem that sounds a lot like yours. I've got three devices connected to the same "netbird network," and one of them is an SSH server. For some reason, only one device on my network was able to connect to that server. I tried using ping and traceroute to reach the server's DNS name and IP address, but it didn't work (nslookup was working). So, I decided to downgrade to version 0.26.6, and now all my devices can reach the SSH server in my netbird network.
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Apr 10, 2024):

@y1xia0w @bhavitsharma can you test if this was fixed with 0.27.2?

@lixmal commented on GitHub (Apr 10, 2024): @y1xia0w @bhavitsharma can you test if this was fixed with `0.27.2`?
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@bhavitsharma commented on GitHub (Apr 10, 2024):

@y1xia0w @bhavitsharma can you test if this was fixed with 0.27.2?

Thanks, I'll be able to test once it's in nixpkgs.

@bhavitsharma commented on GitHub (Apr 10, 2024): > @y1xia0w @bhavitsharma can you test if this was fixed with `0.27.2`? Thanks, I'll be able to test once it's in nixpkgs.
saavagebueno commented 2025-11-20 05:17:29 -05:00
Author
Owner
Copy Link

@y1xia0w commented on GitHub (Apr 10, 2024):

@y1xia0w @bhavitsharma can you test if this was fixed with 0.27.2?

Hi @lixmal, thank you very much for the quick fix.
I can confirm this is fixed on macOS with 0.27.2 installed with brew.

@y1xia0w commented on GitHub (Apr 10, 2024): > @y1xia0w @bhavitsharma can you test if this was fixed with `0.27.2`? Hi @lixmal, thank you very much for the quick fix. I can confirm this is fixed on macOS with `0.27.2` installed with `brew`.
saavagebueno commented 2025-11-20 05:17:30 -05:00
Author
Owner
Copy Link

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

Can not connect to same LAN with 0.27.3, again

@hurricane1026 commented on GitHub (Apr 24, 2024): Can not connect to same LAN with 0.27.3, again
saavagebueno commented 2025-11-20 05:17:30 -05:00
Author
Owner
Copy Link

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

Can not connect to same LAN with 0.27.3, again

Can you open a new bug report with attached details, please? @hurricane1026

@lixmal commented on GitHub (Apr 24, 2024): > Can not connect to same LAN with 0.27.3, again Can you open a new bug report with attached details, please? @hurricane1026
saavagebueno commented 2025-11-20 05:17:30 -05:00
Author
Owner
Copy Link

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

Can not connect to same LAN with 0.27.3, again

Can you open a new bug report with attached details, please? @hurricane1026

please check #1889

@hurricane1026 commented on GitHub (Apr 24, 2024): > > Can not connect to same LAN with 0.27.3, again > > Can you open a new bug report with attached details, please? @hurricane1026 please check #1889
saavagebueno commented 2025-11-20 05:17:30 -05:00
Author
Owner
Copy Link

@zacharyptt commented on GitHub (Jul 31, 2024):

I have same issues on 0.28.6
macOS: Sonoma 14.5
device: Apple M1 Max

netbird status       

OS: darwin/arm64
Daemon version: 0.28.6
CLI version: 0.28.6
Management: Connected
Signal: Connected
Relays: 2/2 Available
Nameservers: 0/0 Available
FQDN: rddemac-studio.netbird.cloud
NetBird IP: 100.72.90.30/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected

ping 100.72.90.30

PING 100.72.90.30 (100.72.90.30): 56 data bytes
Request timeout for icmp_seq 0
@zacharyptt commented on GitHub (Jul 31, 2024): I have same issues on 0.28.6 macOS: Sonoma 14.5 device: Apple M1 Max ``` netbird status OS: darwin/arm64 Daemon version: 0.28.6 CLI version: 0.28.6 Management: Connected Signal: Connected Relays: 2/2 Available Nameservers: 0/0 Available FQDN: rddemac-studio.netbird.cloud NetBird IP: 100.72.90.30/16 Interface type: Userspace Quantum resistance: false Routes: - Peers count: 1/1 Connected ``` ``` ping 100.72.90.30 PING 100.72.90.30 (100.72.90.30): 56 data bytes Request timeout for icmp_seq 0 ```
saavagebueno commented 2025-11-20 05:17:30 -05:00
Author
Owner
Copy Link

@ecoprintec commented on GitHub (Dec 27, 2024):

I have same issues on 0.35.1
macOS: Sequoia 15.2
device: Apple M1

netbird status 

OS: darwin/arm64
Daemon version: 0.35.1
CLI version: 0.35.1
Management: Connected
Signal: Connected
Relays: 3/3 Available
Nameservers: 0/0 Available
FQDN: mac-mini.netbird.selfhosted
NetBird IP: 100.69.178.54/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Networks: -
Peers count: 3/8 Connected

ping 100.69.178.54

PING 100.69.178.54 (100.69.178.54): 56 data bytes
Request timeout for icmp_seq 0
@ecoprintec commented on GitHub (Dec 27, 2024): I have same issues on 0.35.1 macOS: Sequoia 15.2 device: Apple M1 ```bash netbird status OS: darwin/arm64 Daemon version: 0.35.1 CLI version: 0.35.1 Management: Connected Signal: Connected Relays: 3/3 Available Nameservers: 0/0 Available FQDN: mac-mini.netbird.selfhosted NetBird IP: 100.69.178.54/16 Interface type: Userspace Quantum resistance: false Routes: - Networks: - Peers count: 3/8 Connected ``` ```bash ping 100.69.178.54 PING 100.69.178.54 (100.69.178.54): 56 data bytes Request timeout for icmp_seq 0 ```
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 agent
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#782
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?