Fwd: netbackup.gs tor relays: please specify 'MyFamily' in your torrc
Hi nusenu, Ok, i edited the torrc-file and added all Fingerprints from my Nodes to "MyFamily", i also corrected the Contact Info. But now, it just shows "alleged Family Member" at Atlas. What's wrong? Should be effective Member wright? Thanks allot for looking for a safe Tor-Network and have a great Day On Thu, Jan 26, 2017 at 6:01 PM, nusenu <nusenu@openmailbox.org> wrote:
Hi netbackup.gs,
thanks for adding OpenBSD tor relays to the network!
Please do not forget to set the MyFamily parameter in your torrc configuration to tell clients your relays belong to a single operator.
If you need help with the MyFamily option let us know.
thanks, nusenu PS: something went wrong with your ContactInfo string on your new relays.
https://github.com/nusenu/ansible-relayor
+-------------+-----------------------------------+----------------+ | nickname | contact | eMyFamilyCount | +-------------+-----------------------------------+----------------+ | OpenBSD0rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD1rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD2rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD2rel | netbackup(dot)gs(at)gmail(dot)com | NULL | | OpenBSD3rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD4rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD5rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD6rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD7rel | (dot)(at)gmail(dot)com | NULL | | OpenBSD8rel | (dot)(at)gmail(dot)com | NULL | +-------------+-----------------------------------+----------------+
Hi nusenu,
Ok, i edited the torrc-file and added all Fingerprints from my Nodes to "MyFamily", i also corrected the Contact Info. But now, it just shows "alleged Family Member" at Atlas. What's wrong? Should be effective Member wright?
Each relay needs to have it's torrc file updated with the MyFamily, this way they corroborate each other. These are the MyFamily lines from my 3 relays:- from torrc on E856ABA2020AA9C483CC2D9B4C878D8D948B0887 MyFamily $38B330302F1FB79ED11A468FC9DEA8960B842B57,$FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC from torrc on FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC MyFamily $E856ABA2020AA9C483CC2D9B4C878D8D948B0887,$38B330302F1FB79ED11A468FC9DEA8960B842B57 from torrc on 38B330302F1FB79ED11A468FC9DEA8960B842B57 MyFamily $E856ABA2020AA9C483CC2D9B4C878D8D948B0887,$FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC Alan
Thank Alan, I did that, all Fingerprints in every torrc of every node, but i looks like Atlas has a temporary Problem (Backend Error). As i understood you can put every Fingerprint (also from the running Node) in it, the fingerprint of the running node is filtered out, witch makes deployment easier. Will check it tomorrow again. Thanks for your help, Have a great Day On Fri, Jan 27, 2017 at 7:22 PM, Alan <tor-relay@clutterbuck.uk> wrote:
Hi nusenu,
Ok, i edited the torrc-file and added all Fingerprints from my Nodes to "MyFamily", i also corrected the Contact Info. But now, it just shows "alleged Family Member" at Atlas. What's wrong? Should be effective Member wright?
Each relay needs to have it's torrc file updated with the MyFamily, this way they corroborate each other.
These are the MyFamily lines from my 3 relays:-
from torrc on E856ABA2020AA9C483CC2D9B4C878D8D948B0887 MyFamily $38B330302F1FB79ED11A468FC9DEA8960B842B57,$FDB4FC238F13E7FEC99D025DB8B89A 636EFC1EBC
from torrc on FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC MyFamily $E856ABA2020AA9C483CC2D9B4C878D8D948B0887,$38B330302F1FB79ED11A468FC9DEA8 960B842B57
from torrc on 38B330302F1FB79ED11A468FC9DEA8960B842B57 MyFamily $E856ABA2020AA9C483CC2D9B4C878D8D948B0887,$FDB4FC238F13E7FEC99D025DB8B89A 636EFC1EBC
Alan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi netbackup.gs, thanks for adjusting your config files. netbackup.gs:
I did that, all Fingerprints in every torrc of every node, but i looks like Atlas has a temporary Problem (Backend Error).
onionoo (atlas' data source) usually updates once an hour but currently is a bit behind, so if you changed+reloaded your torrc files after 2017-01-27 13:00 we might just wait until onionoo catches up again. Currently onionoo provides a view of the network from 2017-01-27 13:00. Maybe it would make sense to add that timestamp to the atlas pages. Just found the relevant (old) trac entry which had activity just today: https://trac.torproject.org/projects/tor/ticket/9814#comment:18
I did that, all Fingerprints in every torrc of every node, but i looks like Atlas has a temporary Problem (Backend Error).
onionoo (atlas' data source) usually updates once an hour but currently is a bit behind, so if you changed+reloaded your torrc files after 2017-01-27 13:00 we might just wait until onionoo catches up again.
https://onionoo.torproject.org is still behind but if you use the second atlas/onionoo instance you can see that your config is fine, thanks for updating it so quickly. https://atlas.thecthulhu.com/#search/OpenBSD https://onionoo.thecthulhu.com/details?search=OpenBSD +------------+-------------+----------------+ | first_seen | nickname | eMyFamilyCount | +------------+-------------+----------------+ | 2016-09-13 | OpenBSD0rel | 9.0000 | | 2016-09-13 | OpenBSD1rel | 9.0000 | | 2017-01-25 | OpenBSD2rel | 9.0000 | | 2016-09-13 | OpenBSD3rel | 9.0000 | | 2017-01-25 | OpenBSD4rel | 9.0000 | | 2017-01-25 | OpenBSD5rel | 9.0000 | | 2017-01-25 | OpenBSD6rel | 9.0000 | | 2017-01-25 | OpenBSD7rel | 9.0000 | | 2017-01-25 | OpenBSD8rel | 9.0000 | +------------+-------------+----------------+
It looks like Atlas i working normal again. All my nodes are now shown as effective FamilyMember. Many thanks at Nusenu an Alan for giving me a helping Hand, On Sat, Jan 28, 2017 at 10:06 AM, nusenu <nusenu@openmailbox.org> wrote:
I did that, all Fingerprints in every torrc of every node, but i looks like Atlas has a temporary Problem (Backend Error).
onionoo (atlas' data source) usually updates once an hour but currently is a bit behind, so if you changed+reloaded your torrc files after 2017-01-27 13:00 we might just wait until onionoo catches up again.
https://onionoo.torproject.org is still behind but if you use the second atlas/onionoo instance you can see that your config is fine, thanks for updating it so quickly.
https://atlas.thecthulhu.com/#search/OpenBSD https://onionoo.thecthulhu.com/details?search=OpenBSD
+------------+-------------+----------------+ | first_seen | nickname | eMyFamilyCount | +------------+-------------+----------------+ | 2016-09-13 | OpenBSD0rel | 9.0000 | | 2016-09-13 | OpenBSD1rel | 9.0000 | | 2017-01-25 | OpenBSD2rel | 9.0000 | | 2016-09-13 | OpenBSD3rel | 9.0000 | | 2017-01-25 | OpenBSD4rel | 9.0000 | | 2017-01-25 | OpenBSD5rel | 9.0000 | | 2017-01-25 | OpenBSD6rel | 9.0000 | | 2017-01-25 | OpenBSD7rel | 9.0000 | | 2017-01-25 | OpenBSD8rel | 9.0000 | +------------+-------------+----------------+
participants (3)
-
Alan -
netbackup.gs -
nusenu