netbird icon indicating copy to clipboard operation
netbird copied to clipboard

windows peer cannot be selected in Routing Peer

Open wgetnz opened this issue 1 year ago • 6 comments

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.

wgetnz avatar Oct 25 '23 06:10 wgetnz

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

mlsmaycon avatar Oct 25 '23 07:10 mlsmaycon

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?

wgetnz avatar Oct 25 '23 10:10 wgetnz

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

mlsmaycon avatar Oct 25 '23 10:10 mlsmaycon

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.

grahamIT avatar Jan 17 '24 19:01 grahamIT

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.

wgetnz avatar May 03 '24 12:05 wgetnz