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

iptables user chain #2119

New Issue
Open
opened 2025-11-20 07:04:10 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:04:10 -05:00
Owner
Copy Link

Originally created by @AbsurdlySuspicious on GitHub (Jul 28, 2025).

Is your feature request related to a problem? Please describe.
Netbird client overrides beginning of INPUT chain (iptables-legacy) and does not allow to reliably insert rules with -i wt0 before netbird rules to harden security of peers (refer to #683) aside from netbird policies.

Describe the solution you'd like
Implement NETBIRD_INPUT_USER, NETBIRD_FORWARD_USER chains similar to DOCKER_USER chain. They should be created empty if they do not exist (and shouldn't be touched at all if they exist), and should be jumped to in first rule injected into built-in input or forward chains. User will then DROP/REJECT unwanted packets in these chains, or RETURN whitelisted packets just like in docker.

Describe alternatives you've considered

Continuously monitoring iptables rules and inserting my own on any changes. This approach is not very reliable and in worst case will create a delay before applying necessary DROP rules allowing attacker to access private services right after policies change if they manage to hack netbird management server.

Additional context
Netbird self-hosted 0.51.2

Originally created by @AbsurdlySuspicious on GitHub (Jul 28, 2025). **Is your feature request related to a problem? Please describe.** Netbird client overrides beginning of INPUT chain (iptables-legacy) and does not allow to reliably insert rules with `-i wt0` before netbird rules to harden security of peers (refer to #683) aside from netbird policies. **Describe the solution you'd like** Implement NETBIRD_INPUT_USER, NETBIRD_FORWARD_USER chains similar to DOCKER_USER chain. They should be created empty if they do not exist (and shouldn't be touched at all if they exist), and should be jumped to in first rule injected into built-in input or forward chains. User will then DROP/REJECT unwanted packets in these chains, or RETURN whitelisted packets just like in docker. **Describe alternatives you've considered** Continuously monitoring iptables rules and inserting my own on any changes. This approach is not very reliable and in worst case will create a delay before applying necessary DROP rules allowing attacker to access private services right after policies change if they manage to hack netbird management server. **Additional context** Netbird self-hosted 0.51.2
saavagebueno added the feature-request label 2025-11-20 07:04:10 -05:00
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 feature-request
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#2119
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?