[GH-ISSUE #1248] windows peer cannot be selected in Routing Peer #1968

Closed
opened 2026-08-05 00:44:46 -04:00 by saavagebueno · 12 comments
Owner

Originally created by @wgetnz on GitHub (Oct 25, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1248

My English is not very good. I found that when adding Network Routes, Windows client peers cannot be selected in Routing Peer, but Linux clients can.

Originally created by @wgetnz on GitHub (Oct 25, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1248 My English is not very good. I found that when adding Network Routes, Windows client peers cannot be selected in Routing Peer, but Linux clients can.
saavagebueno added the feature-requestwindows labels 2026-08-05 00:44:46 -04:00
Author
Owner

@mlsmaycon commented on GitHub (Oct 25, 2023):

Hello @wgetnz , that is the expected behavior. Network routes require a Linux node to route packets.

<!-- gh-comment-id:1778686311 --> @mlsmaycon commented on GitHub (Oct 25, 2023): Hello @wgetnz , that is the expected behavior. Network routes require a Linux node to route packets.
Author
Owner

@wgetnz commented on GitHub (Oct 25, 2023):

Hello @wgetnz , that is the expected behavior. Network routes require a Linux node to route packets.

In other words, Windows nodes will not be able to become routing nodes in the future?

<!-- gh-comment-id:1778935444 --> @wgetnz commented on GitHub (Oct 25, 2023): > Hello @wgetnz , that is the expected behavior. Network routes require a Linux node to route packets. In other words, Windows nodes will not be able to become routing nodes in the future?
Author
Owner

@mlsmaycon commented on GitHub (Oct 25, 2023):

@mlsmaycon, In the future, they will but we don't have an estimation when we will work on it yet.

<!-- gh-comment-id:1778944823 --> @mlsmaycon commented on GitHub (Oct 25, 2023): @mlsmaycon, In the future, they will but we don't have an estimation when we will work on it yet.
Author
Owner

@grahamIT commented on GitHub (Jan 17, 2024):

Does anyone have alternatives to this? I right now I am looking into just using Nginx Streams to forward traffic but I have a feeling there much be an easier way.

<!-- gh-comment-id:1896501633 --> @grahamIT commented on GitHub (Jan 17, 2024): Does anyone have alternatives to this? I right now I am looking into just using Nginx Streams to forward traffic but I have a feeling there much be an easier way.
Author
Owner

@wgetnz commented on GitHub (May 3, 2024):

Does anyone have alternatives to this? I right now I am looking into just using Nginx Streams to forward traffic but I have a feeling there much be an easier way.

I am currently using headscale, but it does not have webui. Netbird has webui but does not support Windows Routing, which makes me very distressed.

<!-- gh-comment-id:2092903564 --> @wgetnz commented on GitHub (May 3, 2024): > Does anyone have alternatives to this? I right now I am looking into just using Nginx Streams to forward traffic but I have a feeling there much be an easier way. I am currently using headscale, but it does not have webui. Netbird has webui but does not support Windows Routing, which makes me very distressed.
Author
Owner

@Rob787 commented on GitHub (Oct 16, 2024):

+1 for this feature to use on some Windows Servers

<!-- gh-comment-id:2416391986 --> @Rob787 commented on GitHub (Oct 16, 2024): +1 for this feature to use on some Windows Servers
Author
Owner

@bscheewe commented on GitHub (Feb 5, 2025):

This is the only reason we cancelled our trial. Once Windows devices can be routing peers we can move our customers to Netbird.

<!-- gh-comment-id:2636965858 --> @bscheewe commented on GitHub (Feb 5, 2025): This is the only reason we cancelled our trial. Once Windows devices can be routing peers we can move our customers to Netbird.
Author
Owner

@wgetnz commented on GitHub (Feb 5, 2025):

This is the only reason we cancelled our trial. Once Windows devices can be routing peers we can move our customers to Netbird.

+1

<!-- gh-comment-id:2637005448 --> @wgetnz commented on GitHub (Feb 5, 2025): > This is the only reason we cancelled our trial. Once Windows devices can be routing peers we can move our customers to Netbird. +1
Author
Owner

@lixmal commented on GitHub (Feb 21, 2025):

Released in v0.36.6

<!-- gh-comment-id:2674083231 --> @lixmal commented on GitHub (Feb 21, 2025): Released in v0.36.6
Author
Owner

@Sympatron commented on GitHub (Feb 21, 2025):

I can't find this in the release notes. Is it this PR: #3134?

<!-- gh-comment-id:2674366506 --> @Sympatron commented on GitHub (Feb 21, 2025): I can't find this in the release notes. Is it this PR: #3134?
Author
Owner

@lixmal commented on GitHub (Feb 21, 2025):

Yes

<!-- gh-comment-id:2674368965 --> @lixmal commented on GitHub (Feb 21, 2025): Yes
Author
Owner

@bscheewe commented on GitHub (Feb 26, 2025):

This is great news! I just tested it out and I'm super impressed. I'm going to start talking to my customers about migrating to Netbird.

<!-- gh-comment-id:2686754820 --> @bscheewe commented on GitHub (Feb 26, 2025): This is great news! I just tested it out and I'm super impressed. I'm going to start talking to my customers about migrating to Netbird.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#1968