On 22 Jan 2018, at 04:13, Toralf Förster <toralf.foerster@gmx.de> wrote:

On 01/16/2018 11:15 PM, teor wrote:
Hi,

On 17 Jan 2018, at 08:31, Toralf Förster <toralf.foerster@gmx.de
<mailto:toralf.foerster@gmx.de>> wrote:

I do wonder why
   $> scripts/maint/updateFallbackDirs.py check_existing
tells
   $> WARNING::1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA not a
candidate: changed address/port recently (2017-10-22 07:00:00)

But 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA didn't changed it
address/port since end of 2016.

We use Onionoo data this check, and it gives that date for
last_changed_address_or_port:

https://onionoo.torproject.org/details?limit=1&search=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA


Well, followup question:

Today I got
   $> cd ~/devel/tor; ./scripts/maint/updateFallbackDirs.py check_existing

Please don't run this script more than once a day.
It puts some load on Onionoo and the fallbacks.

   ...
   $> WARNING::Excluding 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA: in neither blacklist nor whitelist.
which let me wonder because
   $> git grep 1AF72E8906E6C
gives
   $> scripts/maint/fallback.whitelist:5.9.158.75:80 orport=443 id=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA ipv6=[2a01:4f8:190:514a::2]:443

Doesn't the "WARNING" refer to the file fallback.whitelist ?

In check_existing mode, the whitelist is fallback_dirs.inc.
In the default mode, the whitelist is fallback.whitelist.

We should change that message:
https://trac.torproject.org/projects/tor/ticket/24953

T