Support Forum

safihre wrote: ↑September 9th, 2020, 3:35 pm I have identified the issue and working on a fix. For now I would suggest to downgrade to 3.0.2 untill we release Beta2.
With beta software there's always a risk, but thanks for reporting!

Was just about to report this.

Yet, rfc6724 says the exact same thing in address selection as its predecessor.
https://tools.ietf.org/html/rfc6724#section-10.2

RFC6555 only says IPv4 should be used when IPv6 is slow or fails.

https://tools.ietf.org/html/rfc3484#section-10.2

IPv6 first then IPv4. IPv6 is the priority.

All of the above.. Plus now you have 2 redundant options, as apparently they operate the same. both options use IPv4/IPv6 just the same. I have had to disable load balancing to get it to behave like a proper internet client, but i'm guessing that option doesn't have happy eyeballs at all currently o...

Ok true on on not switching if failing but .1 - .3 sec head start, but doesn't explain why its using both IPv4 and Ipv6 simultaneously. But It should pick one or the other, and in my case my IPv6 is working and is quick enough it should only be using IPv6. In beta 1 it did this correctly, IPv6 only ...

In beta 3, the load balancing option with happy eyeballs should be sticking to IPv6 only servers unless it fails to connect via Ipv6, correct? It should not be using IPv4 for the same server at the same time, right? The simple Load Balancing option, should simply be using IPv6 Only if IPv6 records a...

Awsome.

I believe they are two different issues, one just lead me to notice this one.

Even though your usenet server has 1 URL, it might have multiple IP's linked to that one (both IPv4 and IPv6) so that 1 URL might actually spread things over multiple servers. I am very well versed on DNS and the such, so I get that. The optimization's will use an algorithm called HappyEyeballs, si...

Turns out my other bug (http://forums.sabnzbd.org/viewtopic.php?f=11&t=19581) came to light because of this. Server load-balancing set to Allow with IPv6 Optimizations, caused issues with a Usenet server that has both IPv4 and IPv6 addresses (IPv6 was just added). Switching the setting to simply...

Priority 0 server, Set as Optional (all servers are set this way) has issues and Sab stops using it for 10min (this is correct)

But then priority 1, 2 or 3 server are then not used. so Sab just stops.

OK, that's fine.

Upgraded from 0.7.20 to 0.8.0 Alpha 1 on a Windows 2012 r2 system, simply closed sabnzbd unzipped into the directory and restarted, was presented with browser window for the setup. My sabnzbd.ini has been in the install directory for quite a few version now and all of the sudden it wont see it with ...

Also Looking for this, especially when adding new rejects or require rules.

Thanks..

You guys are awesome.