[tor-relays] why are some exit IPs missing from Exit IP DB?
s7r at sky-ip.org
Sun Oct 11 23:23:00 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
I know those aren't related to the relay in your report, I only
provided them as an example that it works sometimes (the relay in your
report is in the same datacenter with the ones in my example so the
networking setup could be similar). Sorry if the email looked like I
misread the post. As I said, maybe this is just the limitation of the
exit-list by its design.
Good that you've opened a ticket on trac - maybe there's something we
can do about it.
On 10/12/2015 1:53 AM, starlight.2015q3 at binnacle.cx wrote:
> You are checking the wrong IP and not reading the post.
> At 01:45 10/12/2015 +0300, s7r wrote:
>> Check for example: PrivacyRepublic0001 18.104.22.168
> At 13:29 10/8/2015 -0400, starlight.2015q3 at binnacle.cx wrote:
>> Occasionally I run into a relay such as
>> Bywadu 5A0DE94C95E2276B4BAC974A7D8FC6463C4FE8A4 OR ip
>> 22.214.171.124 exit ip 126.96.36.199
>> Where the egress/exit IP source address is not found in the Exit
>> DB, shows up negative on ExoneraTor.
>> MANY EXIT NODES HAVE IPS THAT DIFFER FROM THE OR IP AND WORK
>> FINE. . .
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
-----END PGP SIGNATURE-----
More information about the tor-relays