yggdrasil-network / yggdrasil-go

An experiment in scalable routing as an encrypted IPv6 overlay network

Home Page:https://yggdrasil-network.github.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

win10

babut85 opened this issue · comments

i think that recently some update was in win10, which blocks work with deprecated networks. it looks(on obsd router with yggdrasil) something like this:
from win10 in lan:
-# ping 222:a8e4:50cd:55c:788e:b0a5:4e2f:a92c
rule 14/(match) [uid 0, pid 65591] pass in on vport0: 302:e594:4a01:512a::20 > ff02::1:ff2f:a92c: icmp6: neighbor sol: who has 222:a8e4:50cd:55c:788e:b0a5:4e2f:a92c(src lladdr: 44:8a:5b:a2:18:59) [icmp6 cksum ok] (len 32, hlim 255)
..and "host unreachable"
but there are no problems with the /64 network that is directly on the windows interface, even if it's from 200/7. and there are no problems with other white ipv6 addresses. but other networks from 200/7 cause such the problem. but if win10 is replaced with the same obsd(for example, run obsd on win10 in a virtual machine), then there is no problem.
does anyone know what's going on and how to fix it? in theory(if really is that the evil empire has blocked deprecated networks), it should break not only in a situation where win10 acts as a client in lan, but also when yggdrasil is launched directly on win10