tor-relays February 2017

tor-relays@lists.torproject.org

65 participants
37 discussions

assign_to_cpuworker failed
by diffusae 07 Feb '17

07 Feb '17

Hello! What does this warning mean? "Jan 13 09:31:49.000 [warn] assign_to_cpuworker failed. Ignoring." Do I need to reduce the number of connection to the relay or could I ignore this message? Regards,

5 21

no ipv6 traffic from/to relays ?
by Toralf Förster 07 Feb '17

07 Feb '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Switching from 0.2.9.9 to 0.3.0.3-alpha now let 1/3 of my outgoing network traffic to exit ports (of my Tor exit relay) being ipv6. OTOH there's more or less no ipv6 traffic from/to other relays. Is this (another ipv6) bug/issue in Tor or just expected ? - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAliWTYAXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U7R/QD+Nr4q1CHmhVKgrUrqSp/fEXCEnLnpSfO+njxRdnICbOIA+wSwB02bIOgB mWS13po62pXdO8r3QJiiz5Q7G8ryvtkt =1Mzz -----END PGP SIGNATURE-----

4 8

Re: [tor-relays] [OrNetRadar] AS: "2267921 ONTARIO LTD" - Linux (6)
by nusenu 06 Feb '17

06 Feb '17

> New relays added on 2017-02-01 in AS "2267921 ONTARIO LTD" > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | CC | ORp | Dirp |Version | ContactInfo | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 |01:02:35| 64.137.243.13 | ca | 9001 | 9030 |0.2.8.8 | noah.holland(a)aol.com | phenomenamomentaryh | 1 > 1 | 0 |02:24:58| 64.137.172.121 | ca | 9001 | 9030 |0.2.8.8 | enriquehanson56(a)gmail.com | UwFrNxQgYtBeMv | 1 > 1 | 0 |04:10:09| 45.62.244.240 | ca | 9001 | 9030 |0.2.8.8 | kmjapiji(a)mail.com | 9U5Cs7gu3XTORY | 1 > 1 | 0 |04:17:13| 45.62.252.66 | ca | 9001 | 9030 |0.2.8.8 | jjzwpy(a)yahoo.com | 8z4w2t6qteADFfb6 | 1 > 1 | 0 |12:45:39| 64.137.197.233 | ca | 9001 | 9030 |0.2.8.8 | malvina.maybury(a)gmail.com | CHWMSRVU | 1 > 1 | 0 |13:20:17| 64.137.189.77 | ca | 9001 | 9030 |0.2.8.8 | pwcrack(a)pwcrack.com | CACpwcrackgnt4 | 1 > Fingerprints: > FCAA8608123018476C576AE44AFBC2367D3333AB,653BDEEB516FD16917A45A2DD44272F59C765EF5,82B6083CA4FCC777320CE03EA45BB9380A45A4E7,9D0CBF2C789B9C88F1FE403DA3D5B849B182EAD4,56879AF8A29B1354ED751B26E2D4D3F3C44F2096,FA94C4060AD0BBE913676F090F6BA6706B97F205 > someone trying hard to look different? :)

1 0

Re: [tor-relays] Squalala tor relays: please update 'MyFamily' in your torrc
by nusenu 06 Feb '17

06 Feb '17

Hi BPM Squalala, thanks for adding two more relays, please do not forget to update your MyFamily setting. thanks, nusenu https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… +---------------------+-------------+--------------+ | first_seen | nickname | eFamilyCount | +---------------------+-------------+--------------+ | 2016-09-18 12:00:00 | RedOctober | 3 | | 2016-09-29 16:00:00 | 5OfNovember | 3 | | 2016-12-07 22:00:00 | May68 | 3 | | 2017-02-02 16:00:00 | 9OfDecember | NULL | | 2017-02-03 19:00:00 | 14OfJuly | NULL | +---------------------+-------------+--------------+

1 0

Problem upgrading Tor to 0.2.9.9 on Raspbian (Debian Jessie)
by fr33d0m4all 03 Feb '17

03 Feb '17

Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie): # apt list --upgradable -a Listing... Done tor-geoipdb/stable 0.2.9.9-1~d80.jessie+1 all [upgradable from: 0.2.9.8-2~d80.jessie+1] tor-geoipdb/now 0.2.9.8-2~d80.jessie+1 all [installed,upgradable to: 0.2.9.9-1~d80.jessie+1] tor-geoipdb/stable 0.2.5.12-4 all tor-geoipdb package could be upgrade but the tor package on which it depends is not available: # apt install tor-geoipdb Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: tor-geoipdb : Depends: tor (>= 0.2.9.9-1~d80.jessie+1) but 0.2.9.8-2~d80.jessie+1 is to be installed E: Unable to correct problems, you have held broken packages. Thank you in advance for any answer, Fr33d0m4All -- _____________________________________________________________ PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4 IRC Nick: fr33d0m4all (OFTC & Freenode) _____________________________________________________________

4 4

Minimum port 80 and 443 exit policy
by Mass Tor 03 Feb '17

03 Feb '17

Hey all, I was wondering what the minimum exit policy was (wrt port 80 and 443) for a Tor exit relay. I cant find any documentation about the minimum exit policy. Is it possible to have an exit relay exit only to a /16 or a /8 on port 80 and 443? I've tried having an exit policy that allows exiting to just a /16 on port 80 and 443 and it seems to not stick. Best

4 3

blazingvpn tor relays: please specify 'MyFamily' in your torrc
by nusenu 01 Feb '17

01 Feb '17

Hi blazingvpn tor relay operator, thanks for adding 4 more 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 +------------+-----------------+----------------+ | first_seen | IP | eMyFamilyCount | +------------+-----------------+----------------+ | 2016-12-17 | 163.172.190.249 | NULL | | 2016-12-31 | 108.61.128.176 | NULL | | 2016-12-31 | 51.15.47.106 | NULL | | 2016-12-31 | 51.15.58.152 | NULL | | 2017-01-06 | 185.163.45.249 | NULL | +------------+-----------------+----------------+

6 19

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays February 2017