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

Routing Peers do not configure Input rules when overlapping with routed network range #2353

New Issue
Open
opened 2025-11-20 07:08:26 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 07:08:26 -05:00
Owner
Copy Link

Originally created by @Blackclaws on GitHub (Oct 8, 2025).

Describe the problem

When routing a network via a routing peer that includes the routing peers ip address, no input rules are being generated for access to that routing peer hence traffic to it is dropped.

To Reproduce

  1. Create network with routing peer (for example at 10.10.10.100
  2. Allow access to whole network range (for example 10.10.10.0/24)
  3. Expect that you're able to reach 10.10.10.100 through routing peer
  4. Notice that you're not

Expected behavior

Routing peer itself is accesible

Are you using NetBird Cloud?

No

NetBird version

0.59.3

If you need the debug bundle I can share it but I think its pretty clear.

Originally created by @Blackclaws on GitHub (Oct 8, 2025). **Describe the problem** When routing a network via a routing peer that includes the routing peers ip address, no input rules are being generated for access to that routing peer hence traffic to it is dropped. **To Reproduce** 1. Create network with routing peer (for example at 10.10.10.100 2. Allow access to whole network range (for example 10.10.10.0/24) 3. Expect that you're able to reach 10.10.10.100 through routing peer 4. Notice that you're not **Expected behavior** Routing peer itself is accesible **Are you using NetBird Cloud?** No **NetBird version** 0.59.3 If you need the debug bundle I can share it but I think its pretty clear.
saavagebueno added the triage-needed label 2025-11-20 07:08:26 -05:00
saavagebueno commented 2025-11-20 07:08:27 -05:00
Author
Owner
Copy Link

@pkarc commented on GitHub (Oct 8, 2025):

related https://github.com/netbirdio/netbird/issues/4258

@pkarc commented on GitHub (Oct 8, 2025): related https://github.com/netbirdio/netbird/issues/4258
saavagebueno commented 2025-11-20 07:08:28 -05:00
Author
Owner
Copy Link

@Blackclaws commented on GitHub (Oct 8, 2025):

That network access page should get merged sooner rather than later. However I wonder why there isn't simply an input rule created for the destination ip on the routing peer that overlaps with the subnet. It shouldn't be that difficult to create that rule clientside on the routing peer when the routing rule is received. I would consider this unexpected behaviour and the fact that a whole page needs to be created to talk about that makes that clear. I would rather say a fix could be to add a toggle to the routing peer: "Allow access to routing peer itself" that could help here.

@Blackclaws commented on GitHub (Oct 8, 2025): That network access page should get merged sooner rather than later. However I wonder why there isn't simply an input rule created for the destination ip on the routing peer that overlaps with the subnet. It shouldn't be that difficult to create that rule clientside on the routing peer when the routing rule is received. I would consider this unexpected behaviour and the fact that a whole page needs to be created to talk about _that_ makes that clear. I would rather say a fix could be to add a toggle to the routing peer: "Allow access to routing peer itself" that could help here.
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#2353
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?