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

Evaluate expanding group-based access control rules with source/destination port and protocol #306

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

Originally created by @toulatip8 on GitHub (Apr 6, 2023).

Is your feature request related to a problem? Please describe.

  • I'd like to be able to allow only specific traffic on a netbird group to expose only specific services (e.g. a group for FTP, one for RDP / VNC and so on). Currently, this needs to be configured locally per-peer, but a centralized solution manageable from netbird webui could be handy.

Describe the solution you'd like

  • As per title, the access control rules could be expanded with source/destination ports and protocol.

Describe alternatives you've considered

  • I have not investigated how they are implemented so far, so I cannot estimate the effort required or if this could be the correct way to implement this feature. Peer-based firewall configuration could also be a valid alternative / appreciated feature, but the initial idea was to expand rather than writing an entirely new feature, which could be more cost-effective if the changes are not too many.

Additional context

  • Firewall rules should only be related to netbird tunnel.
  • Rules should not be able to overwrite the peer's rules, otherwise hosts firewall could be compromised by malicious rules.

PS: if this feature is available already I deeply apologized, I must have missed it entirely

Originally created by @toulatip8 on GitHub (Apr 6, 2023). **Is your feature request related to a problem? Please describe.** - I'd like to be able to allow only specific traffic on a netbird group to expose only specific services (e.g. a group for FTP, one for RDP / VNC and so on). Currently, this needs to be configured locally per-peer, but a centralized solution manageable from netbird webui could be handy. **Describe the solution you'd like** - As per title, the access control rules could be expanded with source/destination ports and protocol. **Describe alternatives you've considered** - I have not investigated how they are implemented so far, so I cannot estimate the effort required or if this could be the correct way to implement this feature. Peer-based firewall configuration could also be a valid alternative / appreciated feature, but the initial idea was to expand rather than writing an entirely new feature, which could be more cost-effective if the changes are not too many. **Additional context** - Firewall rules should only be related to netbird tunnel. - Rules should not be able to overwrite the peer's rules, otherwise hosts firewall could be compromised by malicious rules. _PS: if this feature is available already I deeply apologized, I must have missed it entirely_
saavagebueno commented 2025-11-20 05:09:25 -05:00
Author
Owner
Copy Link

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

We've added support with version 0.21.0. see https://github.com/netbirdio/netbird/releases and https://docs.netbird.io/how-to/manage-network-access for more details.

@mlsmaycon commented on GitHub (Jun 16, 2023): We've added support with version 0.21.0. see https://github.com/netbirdio/netbird/releases and https://docs.netbird.io/how-to/manage-network-access for more details.
saavagebueno commented 2025-11-20 05:09:25 -05:00
Author
Owner
Copy Link

@toulatip8 commented on GitHub (Sep 17, 2023):

Thanks a lot, it's exactly the feature I was looking for. Really appreaciate that you managed to address also less visible issues among all the others, I'm closing the issue.

@toulatip8 commented on GitHub (Sep 17, 2023): Thanks a lot, it's exactly the feature I was looking for. Really appreaciate that you managed to address also less visible issues among all the others, I'm closing the issue.
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#306
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?