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

[Tim Wilson-Brown - teor <teor2345@xxxxxxxxx>]

On 11 Oct 2015, at 22:27, nusenu <nusenu@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxx.

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

Isn't this a bug in TorCheck?

It assumes that every relay has its ORPort IP as its Exit IP (OutboundBindAddress), and most likely also assumes that each exit only has one IP.

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays