SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-01 19:52:38 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Name based routes are ignored with client 0.36.x on MacOS #1580

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

Originally created by @samroweemployinc on GitHub (Jan 30, 2025).

We're running 0.36.5 on the coordinator and peers and if our MacOS users upgrade to 0.36.x they're no longer able to use name based routes. We haven't converted to Networks yet. Downgrading to 0.34.1 restores the functionality. Our peers aren't publicly available, so the connections are all relayed. Linux 0.36.5 clients seem to work fine.

To Reproduce

Steps to reproduce the behavior:

  1. Create a name-based-route
  2. Use 0.36.x on MacOS and try to go to that route. We've used a homebrew-installed tcptraceroute to test the path. After downgrading to 0.34.1 the traceroute will go over Netbird.

Expected behavior

Name-based routes should continue to function.

Are you using NetBird Cloud?

Self-hosted

NetBird version

On the clients: 0.36.5 and 0.36.3 were tested.
On the peers and coordinator: 0.36.5

Originally created by @samroweemployinc on GitHub (Jan 30, 2025). We're running 0.36.5 on the coordinator and peers and if our MacOS users upgrade to 0.36.x they're no longer able to use name based routes. We haven't converted to Networks yet. Downgrading to 0.34.1 restores the functionality. Our peers aren't publicly available, so the connections are all relayed. Linux 0.36.5 clients seem to work fine. **To Reproduce** Steps to reproduce the behavior: 1. Create a name-based-route 2. Use 0.36.x on MacOS and try to go to that route. We've used a homebrew-installed `tcptraceroute` to test the path. After downgrading to 0.34.1 the traceroute will go over Netbird. **Expected behavior** Name-based routes should continue to function. **Are you using NetBird Cloud?** Self-hosted **NetBird version** On the clients: 0.36.5 and 0.36.3 were tested. On the peers and coordinator: 0.36.5
saavagebueno added the triage-needed label 2025-11-20 05:33:13 -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 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#1580
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?