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

Request to Add Command to Directly Move NetBird Interface to Network Namespace (netnsnetns) #2471

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

Originally created by @daifeilail on GitHub (Nov 17, 2025).

Description:
In NetBird 0.59, I encountered an issue where I cannot move the WireGuard interface into a custom network namespace (). Earlier versions of NetBird supported using standard Linux commands (e.g., ) to move the interface into a network namespace, providing more flexible network configuration. However, with the latest version, a network check has been introduced that prevents this operation from succeeding.wt0netnsip link set
To simplify network configuration in containerized platforms like Docker and Kubernetes, I propose adding a command to NetBird that would allow users to directly move the interface or other NetBird interfaces into a specified network namespace, enabling more flexible and precise network isolation configurations.netnswt0
Steps to Reproduce:
Use NetBird 0.59 version and enable NetBird on the host.
Create a new network namespace using the command .ip netns add
Attempt to move the interface into the new namespace using .wt0ip link set wt0 netns
The operation fails, and the interface cannot be moved into the namespace.
Expected Behavior:
Introduce a command that allows users to directly move the interface or other NetBird interfaces into a specified network namespace. This would simplify network configuration and provide more flexible network isolation and management in containerized environments like Docker and Kubernetes.netnswt0
Actual Behavior:
The current network check mechanism in NetBird prevents the interface from being moved into a custom network namespace, preventing network isolation or special routing configurations in containerized environments.wt0
Suggested Improvement:
Add netns Command: A command that allows users to move the interface (or other NetBird interfaces) into a specified network namespace. Example command: wt0netbird netns move wt0
Support Containerized Environments: Specifically for Docker and Kubernetes, allowing users to move the NetBird interface into a container’s network namespace, making network configuration and m

Originally created by @daifeilail on GitHub (Nov 17, 2025). Description: In NetBird 0.59, I encountered an issue where I cannot move the WireGuard interface into a custom network namespace (). Earlier versions of NetBird supported using standard Linux commands (e.g., ) to move the interface into a network namespace, providing more flexible network configuration. However, with the latest version, a network check has been introduced that prevents this operation from succeeding.wt0netnsip link set To simplify network configuration in containerized platforms like Docker and Kubernetes, I propose adding a command to NetBird that would allow users to directly move the interface or other NetBird interfaces into a specified network namespace, enabling more flexible and precise network isolation configurations.netnswt0 Steps to Reproduce: Use NetBird 0.59 version and enable NetBird on the host. Create a new network namespace using the command .ip netns add <netns-name> Attempt to move the interface into the new namespace using .wt0ip link set wt0 netns <netns-name> The operation fails, and the interface cannot be moved into the namespace. Expected Behavior: Introduce a command that allows users to directly move the interface or other NetBird interfaces into a specified network namespace. This would simplify network configuration and provide more flexible network isolation and management in containerized environments like Docker and Kubernetes.netnswt0 Actual Behavior: The current network check mechanism in NetBird prevents the interface from being moved into a custom network namespace, preventing network isolation or special routing configurations in containerized environments.wt0 Suggested Improvement: Add netns Command: A command that allows users to move the interface (or other NetBird interfaces) into a specified network namespace. Example command: wt0netbird netns move wt0 <netns-name> Support Containerized Environments: Specifically for Docker and Kubernetes, allowing users to move the NetBird interface into a container’s network namespace, making network configuration and m
saavagebueno added the feature-request label 2025-11-20 07:10:11 -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#2471
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?