tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

IPv6 - status
by Marcin Gondek 12 Sep '14

12 Sep '14

Hi, What is the current state of IPv6? ==cut== Relays to relays Relays talk to other relays. The work with relays talking to other relays over IPv6 has not been started. ==cut== Is there any plans to start? How I can help? ==cut== Directory authorities on IPv6 Clients and relays talk to directory authorities. The work with making directory authorities reachable over IPv6 has not been started. This work will be tracked in #6027. ==cut== Same as above? Clue is when it will be possible to run pure IPv6 relay/guard. Regards, -- Marcin Gondek / Drixter http://fido.e-utp.net/ AS56662

3 4

Re: [tor-relays] boost CPU on a Tor relay
by Harold Naparst 09 Sep '14

09 Sep '14

I'll just throw in my datapoint on this subject because it might be of interest. My relay (torpoint) is currently advertising a bandwidth of 58 MB/s according to Globe. Arm reports that it is pushing 50 MB/s and has 12,500 open clients. It has a Xeon E3/1220 with 8 GB ram. The load average is 0.75, and the four cores are at about 20-25% each. About 2GB of ram is being used. On the whole, this relay is probably bandwidth constrained. The ISP guarantees 150 Mbps, but I sometimes get more, like now.

1 0

Gentoo overlay
by Harold Naparst 09 Sep '14

09 Sep '14

Sorry Jeremy, I didn't realize you were a Gentoo dev. I have added the comment to the Gentoo bug discussion per your wishes.

1 0

Re: [tor-relays] enable-ec_nistp_64_gcc_128
by Harold Naparst 09 Sep '14

09 Sep '14

I thought about this also, but I decided not to do it. Gentoo has clearly decided not to include the Elliptic Curve algorithms until they can get confirmation that it works on all archs. Funtoo has taken the opposite position. >From the looks of the Gentoo thread, they should add the flag in the near future, and I think it would be more diplomatic to just let the process play out. My hope is that a Google search would lead most people to this post. I just created the ebuild in my overlay because I wanted it now and I thought some other enthusiasts would also want it now. I hope it works for you, and would be interested if it makes a difference. > Thanks for your contribution, can you also add some note to the > underlying bug report https://bugs.gentoo.org/469976 so others may see > it easier? > -Jeremy > On Mon, Sep 8, 2014 at 2:52 PM, Harold Naparst <harold(a)alum.mit.edu> wrote: >> If you want a version of openssl compiled with the >> enable-ec_nistp_64_gcc_128 option and you are using Gentoo Linux, >> you can grab it from my overlay:

1 0

enable-ec_nistp_64_gcc_128
by Harold Naparst 09 Sep '14

09 Sep '14

If you want a version of openssl compiled with the enable-ec_nistp_64_gcc_128 option and you are using Gentoo Linux, you can grab it from my overlay: layman -f layman -a hnaparst emerge openssl The new flag "nist" is turned on by default. I have 1.0.1i and 1.0.2_beta2 in the overlay. Hope it helps.

2 1

TTTT
by Sebastian Urbach 08 Sep '14

08 Sep '14

Dear list members, Just a quick update regarding TTTT: Currently we are working on a technical paper based on the so far collected data. ETA is roughly 4 weeks from now on. The paper is going to hit this list asap. -- Mit freundlichen Grüssen / Sincerely yours Sebastian Urbach ---------------------------------------------- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. ---------------------------------------------- Benjamin Franklin (1706 - 1790), Inventor, journalist, printer, diplomat and statesman

1 0

Handshake flood now on NTor
by Jobiwan Kenobi 08 Sep '14

08 Sep '14

Hi, For about 15 hours straight, my relay was being hammered by connections/handshakes. I see lots of these: Sep 02 01:03:02.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [70638 similar message(s) suppressed in last 60 seconds] Numbers vary between 30000 and 80000 per 60 seconds. Also the occasional clock jump message and other performance related messages, and of course, _lots_ of unsuccessful handshakes: Sep 01 22:31:26.000 [notice] Circuit handshake stats since last time: 5038/5038 TAP, 17771/17773 NTor. Sep 02 04:31:26.000 [notice] Circuit handshake stats since last time: 3100/3484 TAP, 465565/5417818 NTor. Sep 02 10:31:26.000 [notice] Circuit handshake stats since last time: 3139/4249 TAP, 679872/8244698 NTor. Sep 02 16:31:26.000 [notice] Circuit handshake stats since last time: 3884/5294 TAP, 502835/10443735 NTor. It is a low spec machine. I've been through episodes like this before, but this time it's different: - They are NTor handshakes, where before they would be TAP handshakes. - The amount of up and down traffic is pretty balanced, where before I would get much more down than up during these floods. - In case it matters: I am now running 0.2.4.23, before I was on 0.2.4.18-RC It stopped about 4 hours ago. Running normal now. -Job

3 3

fingerprint info propogation
by jason＠icetor.is 07 Sep '14

07 Sep '14

Sorry if asked before, made a stupid oversight restarting one of my exits yesterday, had duplicated the fingerprint file from another node. Changed the file to the correct nickname today (I know nicknames are depreciated now) and reset tor, how long will it take this change to propogate to the network? -Jason

4 4

TOR exit notice (not USA)
by Christian Gagneraud 06 Sep '14

06 Sep '14

Hi there, I've just installed the tor-exit-notice.html (from contrib/) on my exit node, and read it carefully. I think this is great to have such a text, but 2 paragraphs are USA specific, the one about ECPA and the following one about DMCA. I would like to know if anyone knows about equivalent text for the European Union, Germany, France and New Zealand (I'm French, I'm a New Zealand resident and I run a TOR exit node on a server located in Germany) Thanks, Chris

4 4

Time information
by Marcin Gondek 05 Sep '14

05 Sep '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just looking on the logs and see: ==cut== Sep 02 21:03:54.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:443. It seems that our clock is behind by 1 hours, 24 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:04.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is ahead by 1 hours, 4 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:08.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is ahead by 3 hours, 35 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:06:58.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 5 hours, 58 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:08:53.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 1 hours, 54 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:10:49.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:9001. It seems that our clock is behind by 5 hours, 55 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:11:51.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:8443. It seems that our clock is ahead by 1 hours, 26 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. Sep 02 21:11:52.000 [info] channel_tls_process_netinfo_cell(): Received NETINFO cell with skewed time from server at x.x.x.x:449. It seems that our clock is ahead by 1 hours, 19 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings. ==cut== Should I worry about it? Logs seems to little strange and looks that other servers provide it's local time without any timezone. [root@fido tor]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +x.x.x.x .PPS. 1 u 11 64 377 15.026 2.142 3.279 +x.x.x.x .PPS. 1 u 26 64 377 8.315 2.734 4.281 +x.x.x.x .PPS. 1 u 2 64 377 6.511 0.973 3.214 *x.x.x.x .PPS. 1 u 60 64 377 6.395 2.162 1.869 oGPS_NMEA(0) .GPS. 0 l 15 16 377 0.000 0.014 0.009 And server is a part of ntppool - valid. Regards, - -- Marcin Gondek / Drixter http://fido.e-utp.net/ AS56662 -----BEGIN PGP SIGNATURE----- Version: Outlook Privacy Plugin iGkEARECACkFAlQGGCoiHE1hcmNpbiBHb25kZWsgPGRyaXh0ZXJAZS11dHAubmV0 PgAKCRCBZoxYcbpnGhhSAJ0RENGRgehGCb/9m/P2lTHR/2k+kACgwOIXsUNHS6FW 1AOwVQoeTwSPCO0= =OYl2 -----END PGP SIGNATURE-----

6 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays