[tor-relays] why are some exit IPs missing from Exit IP DB?

[s7r]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Don't know if we can call it a bug.
It appears to be working, real exit IP addresses are discovered.

Check for example:
PrivacyRepublic0001 178.32.181.96
PrivacyRepublic0002 178.32.181.97
Both exit with IP: 37.187.129.166

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:
https://exonerator.torproject.org/?ip=37.187.129.166&timestamp=2015-10-10

It will even return the results on atlas:
http://atlas777hhh7mcs7.onion/#search/37.187.129.166

On 10/11/2015 2:27 PM, nusenu wrote:
>> Occasionally I run into a relay such as
>> 
>> Bywadu 5A0DE94C95E2276B4BAC974A7D8FC6463C4FE8A4
>> 
>> OR ip 178.33.157.6
>> 
>> exit ip 31.7.58.37
>> 
>> 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.
> 
> https://collector.torproject.org/formats.html#exit-lists
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJWGuaQAAoJEIN/pSyBJlsRgLUH/14pO7pF0KTV7o8Mr4uBYc5R
VB8L59oMNxkwMn+3TcQHOp3ILR0iEIEH1p6CWdzL2mcrhQ6Nar6DMbStJl9A7Czg
+Ad7y2luQI54CzYs2tBlGUSrD1RNjUTbcTJFSekvLskYK0vpMYjkQfAWeMUJvce6
PECJ2omhlxlCgO1cdaL7yBu/F3t/6+paVF0tOezTTr4G3FGx3sQl21hdnadmKhHT
9hn03JJTH7XbLtHutkEpKULNHrwiwQ78Hvrk1wbvaXyE3o8DHR7v8vf/N4sizhxR
zGXzhWv2vPSHrTrjkUZLG+va17bN/9cNtl1X7KQ5udblx8A/KpDPjCj/MGVTOyY=
=BXoQ
-----END PGP SIGNATURE-----