netbird
netbird copied to clipboard
windows peer cannot be selected in Routing Peer
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.
Hello @wgetnz , that is the expected behavior. Network routes require a Linux node to route packets.
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?
@mlsmaycon, In the future, they will but we don't have an estimation when we will work on it yet.
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.
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.