macOS cannot ping self on 0.28.6

[zacharyptt]

I cannot not ping self netbird ip like #1806

device: Apple M1 Max macOS: Sonoma 14.5（23F79）

To Reproduce

install newest pkg and connect ping self netbird ip

Expected behavior

can ping self ip

Are you using NetBird Cloud?

Yes.

NetBird version

0.28.6

NetBird status -d output:

Peers detail:
OS: darwin/arm64
Daemon version: 0.28.6
CLI version: 0.28.6
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: rddemac-studio.netbird.cloud
NetBird IP: 100.72.90.30/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 0/0 Connected

PING 100.72.90.30 (100.72.90.30): 56 data bytes
Request timeout for icmp_seq 0

[MaxwellJK]

same issue here

[vinkdong]

same issue here

+1

[lixmal]

What is the use case for pinging the own IP? macOS doesn't support this for the utun interface, we'd have to handle this in Netbird specially

[vinkdong]

In my scenario, for debugging purposes, we start a Springbot service locally that registers with a microservice deployed in a Kubernetes cluster. The registration uses the Netbird IP to allow other online services to access the local service. Sometimes, when the local service needs to access its own features, it also makes HTTP calls to its own Netbird IP.

[nazarewk]

Hello @zacharyptt,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

[xiongyw]

I encountered the issue today (I am new to netbird, trying to figure out if i can replace zerotier with it)...btw, this is not a critical issue for me. some info below

mbp:~ bruin$ netbird status
OS: darwin/amd64
Daemon version: 0.45.2
CLI version: 0.45.2
Management: Connected
Signal: Connected
Relays: 3/3 Available
Nameservers: 0/0 Available
FQDN: mbp.netbird.cloud
NetBird IP: 100.102.196.96/16
Interface type: Userspace
Quantum resistance: false
Lazy connection: false
Networks: -
Forwarding rules: 0
Peers count: 6/6 Connected

mbp:~ bruin$ ping 100.102.196.96
PING 100.102.196.96 (100.102.196.96): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 100.102.196.96 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

mbp:~ bruin$ uname -a
Darwin mbp 22.6.0 Darwin Kernel Version 22.6.0: Thu Mar  6 21:52:09 PST 2025; root:xnu-8796.141.3.711.5~1/RELEASE_X86_64 x86_64

[LinusOssmann]

Here on v0.57.0 and this still seems to be an issue on macOS. Is there anything planned related to fixing this issue yet? Or is this more of a user issue? I do not have the issue on windows or linux machines. Just seems to be macOS causing issues here.