search

slackhq / nebula

A scalable overlay networking tool with a focus on performance, simplicity and security
MIT License
14.33k stars 963 forks source link

Wintun changes do not work on v1.5.2 #661

Closed chirayu-patel closed 2 years ago

chirayu-patel commented 2 years ago

I downloaded the latest windows release v1.5.2 and tried running the normal command but I get the message : "Failed to get a tun/tap device". The exact same way if I run v1.5.0, it works

Has something changed between the 2 versions ?

chirayu-patel commented 2 years ago

Hi,

Can anyone please check if there is a similar observation OR I am doing something wrong

nbrownus commented 2 years ago

Mind posting the entire log line? Are you using unsafe_routes?

chirayu-patel commented 2 years ago

Following is the full message :

C:\Users\world_q2kuhnd\ray\e91505f6-b4d0-41b0-bf5a-29a61196d6c1\695f5209-0848-4747-85fb-9bc57c5769f8>nebula.exe -config 99861bac-e47b-4b15-830e-1a09eb3b22df.config.yaml time="2022-04-20T23:03:38+05:30" level=debug msg="Trusted CA fingerprints" fingerprints="[73e8ac87ccb65a00ba19edb83b1f7dc2061356b53468903da9660db5329528cd]" time="2022-04-20T23:03:38+05:30" level=debug msg="Client nebula certificate" cert="NebulaCertificate {\n\tDetails {\n\t\tName: testelectrono\n\t\tIps: [\n\t\t\t192.168.100.7/24\n\t\t]\n\t\tSubnets: []\n\t\tGroups: []\n\t\tNot before: 2022-04-14 23:39:18 +0530 IST\n\t\tNot After: 2046-11-18 13:39:18 +0530 IST\n\t\tIs CA: false\n\t\tIssuer: 73e8ac87ccb65a00ba19edb83b1f7dc2061356b53468903da9660db5329528cd\n\t\tPublic key: 0c82773dc48125f9bbda86431b7126da47cbaea8edd938ca403a7162445b8f52\n\t}\n\tFingerprint: ab05a9c0129b57bc3aa2094377f2783ca798490569025c1cafb4d51203a04307\n\tSignature: b63eb0647300772646d786fad82895db524c122231bd4762ffe2fecda79fccf55fbae21572b3411bb53bbafce0691ec4c46c7c008964aad7f8e6a9297ac3ed0c\n}" time="2022-04-20T23:03:38+05:30" level=info msg="Firewall rule added" firewallRule="map[caName: caSha: direction:outgoing endPort:0 groups:[] host:any ip: proto:0 startPort:0]" time="2022-04-20T23:03:38+05:30" level=info msg="Firewall rule added" firewallRule="map[caName: caSha: direction:incoming endPort:0 groups:[] host:any ip: proto:0 startPort:0]" time="2022-04-20T23:03:38+05:30" level=info msg="Firewall started" firewallHash=21716b47a7a140e448077fe66c31b4b42f232e996818d7dd1c6c4991e066dbdb time="2022-04-20T23:03:38+05:30" level=error msg="Failed to get a tun/tap device" error="route MTU not supported in Windows"

wadey commented 2 years ago

This was fixed with #648 , but is currently unreleased. Stick on v1.5.0 until we can tag the next release which should be in the next few weeks.

chirayu-patel commented 2 years ago

And yes the config had unsafe routes but as soon as i removed it, it started working.. has something changed in this version related to unsafe routes ?