In ~/Library/Application Support/sabnzb/logs/sabnzb.logs, all I see is: If I start Activity Monitor and Filter for SAB, I see the process starting and then stopping again after a few seconds away. (FWIW: not related to ) :~$ time python sab-test_ipv6.py it should be clear to SABnzbd users what is going on nothing alarming. the site owner should be OK with it's usage.So, if is not OK for this purpose, which FQDN to use? Requirements: MSFTNCSI stands for Microsoft Network Connectivity Status Indicator Used by Windows 7+ to determine if the IPv6 internet is working. That is bad SAB uses _EXTERNAL_IPV6 to determine if it should look up AAAA / IPv6 addresses at all. Maybe protects itself against connect() without a HTTP GET? See the proof below: on a working IPv6 connection, within 30 seconds, _EXTERNAL_IPV6 randomly reports True and False the nnect() times out on 6 seconds. We will not release a 1.0.2 if a 1.1.0 has already been released.Īs the subject says: test_ipv6() and thus _EXTERNAL_IPV6 is unreliable with (and ) 80 and 443.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |