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

Override route if its already exists on the routing table of client #295

New Issue
Closed
opened 2025-11-20 05:09:16 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:09:16 -05:00
Owner
Copy Link

Originally created by @sachinpk on GitHub (Mar 15, 2023).

Is your feature request related to a problem? Please describe.
We have a bunch of hosts with a public and private network (174.20.0.0/16). We are using self-hosted Netbird and connected all hosts to it using the public network. Host A (174.20.0.2) is isolated from our network (174.20.0.0/16) due to some issues happened in the network. We have created a route on Netbird to route traffic to host A through another host B (174.20.0.3).The route that we have added to the Netbird is not getting applied on all hosts since the route to 174.20.0.0/16 is already there on all hosts.

When we inspected the logs on all hosts, we could see the following warning

level=warning msg="skipping adding a new route for network 174.20.0.2/32 because it already exists and is pointing to the non default gateway: 174.20.0.3" file="systemops.go:24"

Describe the solution you'd like
It would be better if there is an option to apply the route even though there is a route existing for subnet

Originally created by @sachinpk on GitHub (Mar 15, 2023). **Is your feature request related to a problem? Please describe.** We have a bunch of hosts with a public and private network (174.20.0.0/16). We are using self-hosted Netbird and connected all hosts to it using the public network. Host A (174.20.0.2) is isolated from our network (174.20.0.0/16) due to some issues happened in the network. We have created a route on Netbird to route traffic to host A through another host B (174.20.0.3).The route that we have added to the Netbird is not getting applied on all hosts since the route to 174.20.0.0/16 is already there on all hosts. When we inspected the logs on all hosts, we could see the following warning ``` level=warning msg="skipping adding a new route for network 174.20.0.2/32 because it already exists and is pointing to the non default gateway: 174.20.0.3" file="systemops.go:24" ``` **Describe the solution you'd like** It would be better if there is an option to apply the route even though there is a route existing for subnet
saavagebueno added the waiting-feedback label 2025-11-20 05:09:16 -05:00
saavagebueno commented 2025-11-20 05:09:17 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 19, 2023):

The PR #945 fixes it and it will be available in the next release.

@mlsmaycon commented on GitHub (Jun 19, 2023): The PR #945 fixes it and it will be available in the next release.
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 waiting-feedback
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#295
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?