We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Since the original thread got closed, I just figured it was worth for me to share that I found the cause some 2 months later in order to have it written on the record, and it turned out it was on my end. 😓
I've been running a DNS server on my PC (with the AdGuard Home backend), and it turned out that in its YAML settings there was a setting called "use dns64" (Presumably intended by that backend's devs as a nickname for NAT64) to true broke a lot of the internet except in web browsers. Setting it to false seems to have made SDI Origin work correctly on IPv6 again.
A dns server. Is it also a vpn? That explains why I was never able to reproduce it, why it's a problem only for a few people. If not AdGuard then something similar.
It's not a VPN on my end, at least. It's a relatively simple but customisable DNS server; reminiscent of Pi-hole but much better (Many more settings and much better syntax support for adblock entries).
and it's blocking ipv6 torrents? or is that a byproduct of a broken ipv6 dns server?
Essentially there was a bug where a setting that claimed to enable NAT64, instead made the 64:ff9b resolvements of NAT64 results the end destination, instead of discarding those resolvements or processing them any further, affecting at least 2 of the 4 torrent addresses, and likely other important addresses too.
https://github.com/AdguardTeam/AdGuardHome/issues/7898 contains most of the details, and the eventual fix method for it.
