onionoo: bug in family set detection?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, by comparing different methodologies of "parsing" myfamily data I stumbled upon differences between onionoo and compass. After manual review I assume there is a bug in onionoo (or onionoo has a different opinion on what families actually are) Example: According to onionoo, torpidsDEevanzo [1] is part of a family with 38 members. It lists torpidsFRonline [2] as one of its members, that implies that torpidsFRonline lists torpidsDEevanzo as one of its members as well, but torpidsDEevanzo does _not_ list torpidsFRonline (according to onionoo data). grep 'fingerprint":"0C77421C890D16B6D201283A2' details.json|grep 5510FC1736B16D46D3F2DDA5011995C478D42594 (no result) Is this a bug? thanks [1] https://atlas.torproject.org/#details/5510FC1736B16D46D3F2DDA5011995C478D425... [2] https://atlas.torproject.org/#details/0C77421C890D16B6D201283A2244F43DF5BC89... -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVbLCAAAoJEFv7XvVCELh0bxkP/1Ep/fhLMhHGIgYnVzEj+xyJ Sb4gqUBuwLckcXLAYGoKZkIeHNS4TFLBidKxuP54bvSLgqPgpsy+OzLiaUk8AYyP Ea2tTmDqcjWy2v/cpP43M3Vh+TpPBTMenNajKwe9Moz63pMpo0V9HLnBjCwBN+Mh 1vGFJw/ov4wmQO3J5OOEABdVt8RTmqCWJBVbz1NmKWNEpxa5sbPS+6tNEvBLbsaL XmtoPcdyAl+14QQk1GSq4Px49K4MFEcRuCN2r1bzRv2WaPgRmFUtrK9JCDwwLlV5 aSrBU7S2M5gn6KowkEZllniZ7n5Ze3SiifqJEPm3hyIUXczveR02LHk++lEXneQE pqxDX6PPnVIt7lm1JW5Svr82boYTC1LQ9xHyF9LStBfYvgWSD5TrDeNaIe8+mka3 OrJ6r0hxMB1IRUaxouI/IGMZLmwj2lqifBeaNccsz876oJ2W6SZu6JPVvNstf7lc TnesBplpAprekofUb3DaGeM80Pa/NmuRjga5F+H6HLH3qE8AxeGKzSQDKYLuRlaM GdZY/bMN/6JGhoHCvYIT8NMNGMYfMPE7UWiHtX+1dezIwyYtwnHxiAcRl/e73TuI cmtzvIiKA9Z1sM2FX8mhaRi6r6TOBdvovSTkKtxkXHk2qT1Sf/oPtvlGtzTlrVp7 uFFgl0Sg++eiHAd1VG58 =D6Qh -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 https://trac.torproject.org/projects/tor/ticket/16276 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVbiccAAoJEFv7XvVCELh0/rUP/i7Q/cZwYaklkvHAaqmsDffK x8J77/21/5ppN1kyPd8jI7M8ktOC+1uqhV4mlf5CyidKR+2kAhhPYjfX57xQ1sbv OJwDq33EbQiTk/ed3DLQdQpbrt7fqaAzZi3+q2NIKMx2/GFRs6Sxnp7D9b69TEt3 WgW2sEuAuexl//HU01dKxPXp6+5EiW6UBz0eUJcTz4WUf/+CltRBg4sbBXImls3w J5mLqMNwyrRT/StTZB5oSMHsOfxQGgGGJppT0l91onQLzpM1A38ZtgN2zs5tD6T9 OSl7hwhUJHaWR3mg9vDywXO0CQ8tTadfZLGtDU0q5H88vU00jTRW1XA7bKLxtLqY INu9APIjnOhaatVTRGhJMMvP/Vuk6OE/L9n2FBw5FAPxmJ3Tn0+NwElamYizq7o8 AMNpWcfjHxAiH7R9PEuhwYyNktlBz3Swm4uNFvSGPaJsm99lxJLmd7ko9qrxd5Cm WcmQvPpfXN9Ym5iTWlMpu17MLmBGb2YgshFv+fTViCY1JwaEqAlTP+5/m2XmnM2x 8CZgNHjL1C7QWffx6AQYqcoAP183ClR3MD9poan7LMYfaqxXIbLceCzMOKeu9Ptt KPAdPAvACngB9kz43oQeJanE/nmjW90j/hr5oPezL57ayJEvpRiT+cmkkRTT2RvB Aj2Q3IqrXhOzTJkR+N94 =pTF3 -----END PGP SIGNATURE-----
Hello, DirAuth's can cache multiple versions of the descriptor and serve what appears to be the newest in a given consensus interval. This coupled with routers publishing descriptors at least every 18 hours, but potentially sooner. What you describe doesn't appear to be a bug in Onionoo because a consensus exists for which the family is declared as you describe in the last known good descriptor. At the moment you describe Atlas doesn't show: [1] last published 2015-06-02 17:44:27 (and [2] may still have entered hibernate) [2] last published 2015-06-02 09:40:45 (and [1] may not be running, or have a last known good descriptor at DirAuths) This doesn't take into account the possibility of a router hibernating (info not always available) at times between consensus taken or valid. A router can be running but unavailable due to accounting. This looks like a result of cached descriptors or router accounting. The data provided to Onionoo from metrics-lib appears accurate as far as network status. At least that's how it looks from a preliminary glance at the data and spec--although please do your own verification. --leeroy
participants (2)
-
l.m -
nusenu