[tor-relays] why are some exit IPs missing from Exit IP DB?
s7r at sky-ip.org
Sun Oct 11 22:45:36 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Don't know if we can call it a bug.
It appears to be working, real exit IP addresses are discovered.
Check for example:
Both exit with IP: 184.108.40.206
It actually works very good, when you connect to check.torproject.org
it says OK > you are using Tor.
Also, Exonerator (and onionoo) knows how to handle it too:
It will even return the results on atlas:
On 10/11/2015 2:27 PM, nusenu wrote:
>> Occasionally I run into a relay such as
>> Bywadu 5A0DE94C95E2276B4BAC974A7D8FC6463C4FE8A4
>> OR ip 220.127.116.11
>> exit ip 18.104.22.168
>> Where the egress/exit IP source address is not found in the Exit
>> DB, shows up negative on ExoneraTor. TorCheck in glaring unhappy
>> RED spits
>>>> Something Went Wrong! Tor is not working in this browser. For
>>>> assistance, please contact help at rt.torproject.org.
>> Does anyone know why this happens?
> Such "non declared" exit IP addresses (OR IP != exit IP) are found
> by exiting through every single exit relay to detect its exit IP.
> Since exits can change their exit IP address at any time the exit
> list can never be 100% accurate by design.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
-----END PGP SIGNATURE-----
More information about the tor-relays