We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
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.
In my case std::bad_cast exception crashes of SDI and SDIO were connected to using Cloudflare's DNS64 (2606:4700:4700::64). After switching to normal IPv6 Cloudflare DNS (2606:4700:4700::1111) the problem was gone immediately.
Thank @dandelionsprout for the hint!
got this error today after a few months of not using. had to update the app to latest, same issue/error with both SDI-Lite 1.26.0 (R2600)(not sure if this relates to your work) and SDIO 1.17.5. i saw in the other threads that you were looking for works/does not work. downloading drivers directly from the list works. error occurs and app crashes only when attempting to download the indexes. since the error was only occurring when attempting to download i did not attempt an app install after download. i have not attempted to change any files or settings.
WIN11 25H2
I had the same problem and resolved it by disabling ISATAP on gpedit. I wonder what exactly made this bug on my computer......
To be specific, I adjusted several settings in "IPv6translation" on gpedit (they used to be "not configured"), and the bug disappeared. And then I reverted the adjustions, but the bug never repeats again. I don't know why......
*By the way, the texts in most themes are too hard to distinguish from the background color, could somebody kindly improve the themes...
Besides, I edited the registry. (but the bug continued until I adjusted settings on gpedit.)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
"DisabledComponents"=dword:00000020
I am not in the same league as you guys are. I had the same issue, but tried the old "just restart your computer" hopeful thinking, and it worked. Worth a try, worked for me...
I just updated the system and the problem repeats. This time I disabled teredo tunneling pseudo-interface and the problem solved. Then I re-enabled it but the problem didn't repeat.
netsh interface teredo set state disabled
netsh interface teredo set state type=natawareclient
First of all, thanks to Glenn for the great program! I've been using it for many years without issue. After not checking for driver updates for some months on my main PC I also ran into this std::bad_cast error when trying to download Indexes. Tried updating to latest SDIO version, rebooting PC, rebooting wireless router, and changing DNS resolvers and the error persisted. What I found worked for me is temporarily disabling NAT6 on my router. So the problem does seem to be IPV6 related. Enabling NAT6 again on my router allows my web browser to pass IPV6 connectivity on the test-ipv6.com site. Without NAT6 the test will fail. Hope this helps someone who may be having this issue.
