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

Do not break connection to node if destination network is routed. #488

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

Originally created by @psuet on GitHub (Oct 29, 2023).

Is your feature request related to a problem? Please describe.
When specifying a network route that overlaps with the IP of a (Routing-)Peer the Network and (Routing-)Peer become unreachable.

Example:
My notebook is somewhere random in the world and want to reach my firewalled public ip corporate / educational network at 1.1.0.0/16.
My Routing-Peer is also in this subnet at 1.1.53.45.

If I specify 1.1.0.0/16 as Network Route, the Routing Peer becomes unreachable once my notebook got provisioned.

Describe the solution you'd like
Exclude IPs for directly connected Peers in the routing table

-or-

Provide an automatic more specific route for the direct connection to the peer.

Note: This works somehow magically out-of-the box with the official Wireguard Client under Windows
https://git.zx2c4.com/wireguard-windows/about/docs/netquirk.md

Describe alternatives you've considered
Alternatively there are some possible backend changes:

It would be nice to be able to specify excluded IPs/Ranges in a network range when adding them via the Web Interface

-or-

Be able to specify multiple Network Ranges per Network Route

(similar to the capabilites of https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/)

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @psuet on GitHub (Oct 29, 2023). **Is your feature request related to a problem? Please describe.** When specifying a network route that overlaps with the IP of a (Routing-)Peer the Network *and* (Routing-)Peer become unreachable. Example: My notebook is somewhere random in the world and want to reach my firewalled public ip corporate / educational network at 1.1.0.0/16. My Routing-Peer is also in this subnet at 1.1.53.45. If I specify 1.1.0.0/16 as Network Route, the Routing Peer becomes unreachable once my notebook got provisioned. **Describe the solution you'd like** Exclude IPs for directly connected Peers in the routing table -or- Provide an automatic more specific route for the direct connection to the peer. Note: This works somehow magically out-of-the box with the official Wireguard Client under Windows https://git.zx2c4.com/wireguard-windows/about/docs/netquirk.md **Describe alternatives you've considered** Alternatively there are some possible backend changes: It would be nice to be able to specify excluded IPs/Ranges in a network range when adding them via the Web Interface -or- Be able to specify multiple Network Ranges per Network Route (similar to the capabilites of https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator/) **Additional context** Add any other context or screenshots about the feature request here.
saavagebueno commented 2025-11-20 05:12:17 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 29, 2023):

Hello, @psuet thanks for reporting the issue. We will work on a solution for this case.

@mlsmaycon commented on GitHub (Oct 29, 2023): Hello, @psuet thanks for reporting the issue. We will work on a solution for this case.
saavagebueno commented 2025-11-20 05:12:17 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Feb 21, 2025):

This has been fixed since at least v0.27.0

@lixmal commented on GitHub (Feb 21, 2025): This has been fixed since at least v0.27.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
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#488
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?