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

policies seem to have no effect #1858

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

Originally created by @amjelnes on GitHub (May 2, 2025).

Describe the problem

Policies seem to have no effect when limiting access on different ports and protocols

To Reproduce

Steps to reproduce the behavior:
Create policies fx. group clients -> Exit node UDP/53
Disable all other policies and ping a device on exit nodes network, ping will respond from the device, likewise external websites can still be browsed, even though no other traffic than UDP/53 should be allowed.

Expected behavior

Would expect that ping would not respond and that no websites could be browsed

Are you using NetBird Cloud?

Self hosted

NetBird version

latest per 2nd may 2025 16:16 CEST

Is any other VPN software installed?
no

Debug output

To help us resolve the problem, please attach the following debug output

netbird status -dA

As well as the file created by

netbird debug for 1m -AS

We advise reviewing the anonymized output for any remaining personal information.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • [x ] Checked for newer NetBird versions
  • [x ] Searched for similar issues on GitHub (including closed ones)
  • [ x] Restarted the NetBird client
  • [ x] Disabled other VPN software
  • [x ] Checked firewall settings

nbstatus.txt
netbird.debug.2759613363.zip
Image

Originally created by @amjelnes on GitHub (May 2, 2025). **Describe the problem** Policies seem to have no effect when limiting access on different ports and protocols **To Reproduce** Steps to reproduce the behavior: Create policies fx. group clients -> Exit node UDP/53 Disable all other policies and ping a device on exit nodes network, ping will respond from the device, likewise external websites can still be browsed, even though no other traffic than UDP/53 should be allowed. **Expected behavior** Would expect that ping would not respond and that no websites could be browsed **Are you using NetBird Cloud?** Self hosted **NetBird version** latest per 2nd may 2025 16:16 CEST **Is any other VPN software installed?** no **Debug output** To help us resolve the problem, please attach the following debug output netbird status -dA As well as the file created by netbird debug for 1m -AS We advise reviewing the anonymized output for any remaining personal information. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [x ] Checked for newer NetBird versions - [x ] Searched for similar issues on GitHub (including closed ones) - [ x] Restarted the NetBird client - [ x] Disabled other VPN software - [x ] Checked firewall settings [nbstatus.txt](https://github.com/user-attachments/files/20014115/nbstatus.txt) [netbird.debug.2759613363.zip](https://github.com/user-attachments/files/20014114/netbird.debug.2759613363.zip) ![Image](https://github.com/user-attachments/assets/d08ff18a-0b72-4955-b6a5-bf79ec04ee04)
saavagebueno added the triage-needed label 2025-11-20 06:08:05 -05:00
saavagebueno commented 2025-11-20 06:08:06 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (May 2, 2025):

Have you assigned an access control group to the exit node route in network routes? Otherwise, all access will be allowed by default.
This group can be distinct from the group the exit node peer is in.

@lixmal commented on GitHub (May 2, 2025): Have you assigned an access control group to the exit node route in network routes? Otherwise, all access will be allowed by default. This group can be distinct from the group the exit node peer is in.
saavagebueno commented 2025-11-20 06:08:06 -05:00
Author
Owner
Copy Link

@amjelnes commented on GitHub (May 2, 2025):

Have you assigned an access control group to the exit node route in network routes? Otherwise, all access will be allowed by default. This group can be distinct from the group the exit node peer is in.
No wasn't aware of that, done now, but I'm confused:
I have 1 exit node this is the only member of a group called exit
I have a number of clients these are only member of a group called clients

I have now added client group to access control groups in exit node route in network routes, also client group is added to distribution groups in the same network route .

I can still ping the local device even though only UDP/53 is active.

If I then enable 80,443,53 I can't browse websites, but I can still ping the local device.

If I then add Exit group to Access control policies Groups in the network routes for the exit node I can browse and ping (ping policy disabled, only ports 80,443,53 enabled)

If I remove Exit group from access control policy and add it to distribution groups I can't browse websites but can still ping.

In other words pinging local device seems indifferent to policies

@amjelnes commented on GitHub (May 2, 2025): > Have you assigned an access control group to the exit node route in network routes? Otherwise, all access will be allowed by default. This group can be distinct from the group the exit node peer is in. No wasn't aware of that, done now, but I'm confused: I have 1 exit node this is the only member of a group called exit I have a number of clients these are only member of a group called clients I have now added client group to access control groups in exit node route in network routes, also client group is added to distribution groups in the same network route . I can still ping the local device even though only UDP/53 is active. If I then enable 80,443,53 I can't browse websites, but I can still ping the local device. If I then add Exit group to Access control policies Groups in the network routes for the exit node I can browse and ping (ping policy disabled, only ports 80,443,53 enabled) If I remove Exit group from access control policy and add it to distribution groups I can't browse websites but can still ping. In other words pinging local device seems indifferent to policies
saavagebueno commented 2025-11-20 06:08:06 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (May 2, 2025):

It's not quite clear to me.

Just to clarify, the setup should be roughly:

Clients group contains your windows client only
EXIT contains only the exit node peer

In Network routes:

Distribution group is Clients
Access control group is EXIT

Policies are fine so far.

In other words pinging local device seems indifferent to policies

What IP is that? Do you have any routes on the client that bypass the exit node route?

Can you create a debug bundle on the exit node?

@lixmal commented on GitHub (May 2, 2025): It's not quite clear to me. Just to clarify, the setup should be roughly: `Clients` group contains your windows client only `EXIT` contains only the exit node peer In Network routes: Distribution group is `Clients` Access control group is `EXIT` Policies are fine so far. >In other words pinging local device seems indifferent to policies What IP is that? Do you have any routes on the client that bypass the exit node route? Can you create a debug bundle on the exit node?
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#1858
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?