[tor-project] scanning for partition in the presumed tor relay mesh network
nusenu-lists at riseup.net
Wed Oct 18 11:03:00 UTC 2017
thank you for doing and sharing this.
> The other failure in this approach to scanning is that it uses a fixed
> set of relays... and therefore the Tor consensus file used will become
> old and contain relays no longer in the consensus well before the scan
> is complete.
> Show me all the tor relays that failed ALL of their circuit builds:
> echo "select first_hop,count(first_hop) from scan_log where status = 'failure' group by second_hop;" | sqlite3 scan2.db | grep 99
Since you mention the design problem of potentially including relays
that are no longer in consensus: Did you review the list of relays
failing _ALL_ circuits against the consensus to check if they just went
offline (or reset their uptime) during the scan? How much time did the
scan take? How much time is usually between each of these 99 attempts?
Can I download your raw scan results (logs with timestamps) somewhere so
I could check if these 'failed ALL circuits' relays reset their uptime
or went offline during the scan?
Did you also play with teor's scanner?
I've started a related (but more long-term) thread on tor-dev on
collecting this kind of data:
related trac tickets:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the tor-project