IPv6 multiple ULAs? #102
Description
Wiresock works very fine with following setup:
"Server":
MikroTik Router OS, NAT for IPv4 and IPv6
Client:
Windows 11, latest Wiresock, virtual adapter or PCAP mode, doesn't matter
The internal IPv6 address space behind the NAT is fd00:100::1/64 (MikroTik wg gateway) and fd00:100::10/64 (Win11 client).
This works fine as long as there is only ONE ULA on the clients physical WiFi adapter. If my home router assigns ULAs, DNS resolving via IPv6 (UDP) with fd00:100::1 as resolver stops working. If I remove the additional ULAs everything works fine again.
Stops working means: The DNS request reaches the MikroTik gateway and the answer leaves towards the wg tunnel. But this answer never reaches the nslookup.exe process which times out.
If I assign some non RFC address to my internal side, e.g. 2001:100:1 and 2001:100::10 everything works fine, even with a lot of ULAs.
Question:
Is this behavior with multiple ULAs to be expected?
If this so I'll try another solution.
If you think this might be a glitch in Wiresock I'll create and send you all required PCAPs and log files.
thx
Michael