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

Add Windows Peer Support for Exit Node Functionality #1756

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

Originally created by @fr58386612 on GitHub (Mar 25, 2025).

Description:
As a NetBird user managing hybrid network environments, I propose adding ​Exit Node support for Windows Peers. Currently, Linux-based peers can be configured as exit nodes, but Windows users lack this capability despite being a significant user base.

Use Case:

Allow Windows devices (e.g., office PCs/cloud servers) to route traffic for remote peers
Enable Windows-specific network configurations (e.g., Active Directory integration)
Provide parity with Linux/macOS exit node features

Originally created by @fr58386612 on GitHub (Mar 25, 2025). Description: As a NetBird user managing hybrid network environments, I propose adding ​Exit Node support for Windows Peers. Currently, Linux-based peers can be configured as exit nodes, but Windows users lack this capability despite being a significant user base. Use Case: Allow Windows devices (e.g., office PCs/cloud servers) to route traffic for remote peers Enable Windows-specific network configurations (e.g., Active Directory integration) Provide parity with Linux/macOS exit node features
saavagebueno added the feature-request label 2025-11-20 06:06:08 -05:00
saavagebueno commented 2025-11-20 06:06:10 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Mar 26, 2025):

Allow Windows devices (e.g., office PCs/cloud servers) to route traffic for remote peers

While a lot of end-users are running Windows indeed, Exit Nodes are not considered a good or even valid use for end-users' machines. Why would you run your whole Internet access through a partially available machine that can be turned off at any time?

Most of the servers (and even home routers) are running either Linux or BSD derivatives,

  • it pretty low effort to spin one up for free, be it a cloud VM or a local hypervisor VM,

It would require in-depth Windows networking knowledge, which is pretty scarce outside the enterprise IT department settings. MacOS is highly utilized by network engineers, and it's networking model is similar to other BSDs and Linux, so it was relatively low-effort to support routing there.

Enable Windows-specific network configurations (e.g., Active Directory integration)

This sounds like a separate enterprise-specific feature.

Could you tell me more about what you are trying to achieve here?

@nazarewk commented on GitHub (Mar 26, 2025): > Allow Windows devices (e.g., office PCs/cloud servers) to route traffic for remote peers While a lot of end-users are running Windows indeed, Exit Nodes are not considered a good or even valid use for end-users' machines. Why would you run your whole Internet access through a partially available machine that can be turned off at any time? Most of the servers (and even home routers) are running either Linux or BSD derivatives, - it pretty low effort to spin one up for free, be it a cloud VM or a local hypervisor VM, ~It would require in-depth Windows networking knowledge, which is pretty scarce outside the enterprise IT department settings. MacOS is highly utilized by network engineers, and it's networking model is similar to other BSDs and Linux, so it was relatively low-effort to support routing there.~ > Enable Windows-specific network configurations (e.g., Active Directory integration) This sounds like a separate enterprise-specific feature. --- Could you tell me more about what you are trying to achieve here?
saavagebueno commented 2025-11-20 06:06:10 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Mar 26, 2025):

Seems like I was mistaken: all supported operating systems are already capable of functioning as routers and Exit Nodes for a while already. The documentation was updated ~3 weeks ago https://github.com/netbirdio/docs/pull/284/files

I have created myself a reminder to verify and clean up the docs mentioning Linux-only limitations of routing.

Can I help you with anything else? Please consider closing the issue if not :)

@nazarewk commented on GitHub (Mar 26, 2025): Seems like I was mistaken: all supported operating systems are already capable of functioning as routers and Exit Nodes for a while already. The documentation was updated ~3 weeks ago https://github.com/netbirdio/docs/pull/284/files I have created myself a reminder to verify and clean up the docs mentioning Linux-only limitations of routing. Can I help you with anything else? Please consider closing the issue if not :)
saavagebueno commented 2025-11-20 06:06:10 -05:00
Author
Owner
Copy Link

@fr58386612 commented on GitHub (Mar 27, 2025):

Image
The reason I need to use Windows as an exit router is that, for example, my clients require my assistance in troubleshooting certain devices within their local area network (LAN). Since these clients exclusively use Windows systems, it becomes necessary to configure Windows as the exit router or a proxy for the subnet to facilitate this process. I believe there are likely many others with similar needs.

@fr58386612 commented on GitHub (Mar 27, 2025): ![Image](https://github.com/user-attachments/assets/41288f5d-f4bd-49f4-aeb2-321b24393cec) The reason I need to use Windows as an exit router is that, for example, my clients require my assistance in troubleshooting certain devices within their local area network (LAN). Since these clients exclusively use Windows systems, it becomes necessary to configure Windows as the exit router or a proxy for the subnet to facilitate this process. I believe there are likely many others with similar needs.
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#1756
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?