- tor-relays - lists.torproject.org

exitnodes blocking services
by not important 18 Jan '17

18 Jan '17

Hey all, Got a question here, I'm running an exit node from a home network that uses play station network, Facebook and a few other service. So my issue/question is why are these service getting blocked on my end? I'm assuming that my ip is getting blocked but wouldn't that mean that people using my exit node would be blocked to those websites as well? what can i do to resolve this issue? maybe I'm missing some technical aspect? thanks! -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQINBFh10ZkBEAC3QTfDVUmKlKl5JNvy7kHulRj7nXYeYEywyXo5zsYsvWeCRYit WqwOr8PgGVO+jmXSxkXxjnGvXF7Kr1qZRHy/1hJxwFztlsgzkYzJOQYqB5Wpgxgf tpkZmY/uOzg61ppvSF8OKteal+jZnPEwGtGr6MNEc4WZecE99NA3tQ9kiqr0wHJE UstgiFv1DV4ju/nqCoaplVCy2LVdTq/IPXXJPozUYYM4U5S6qNPWgg8NKUUAPkkZ kJrgd2PD0qayU5HxO9lIHlwt1f9dp0iwXafXF4DkivMmpipoKB7e6eS+LYYTHQVz rmn+Goco7m34TsBua0ltjY5KDz7Nlts5bOFOYgCLrnpJJggACPetCr1NFQVbkaLb qpZ8hRkuJl5fKR/55lhLMSC7Bh85b4UQioS83ChyyY3dgNuXzss41/gn7sp0VUuA oQg+YYia3vWmOaBSXlQmM8ukw9QcMiVje4qlUaZjsCcNKwRCEX6YvcY1X8Yzm6uv yycPvroTIiJE1YZOVRj2oGSqNftZWtTnebVEveIezF/tX7Tadf6xq6kaQdUZzbAv tX+O/jOTGfo/8XECXPrLiPXlwY3ZrloXMr1QSBJQxZoCkfuDsi9Lek3SvWmxrQuM 0q66bk4k7LrO7e0lNueLSmna4OZFih/FUFwAq+bH6SciF9eOxm6NOPrnXwARAQAB tC9mcmVkYSAoc3RyZW5ndGggaW4gbnVtYmVycykgPEZyZWRhQHNpZ2FpbnQub3Jn PokCNwQTAQgAIQUCWHXRmQIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRDi hi2oPd1kcz6hEACyDgzf+L0OpB9Znsx7EEt8N1/zGyzGQoL/MQVsxMiJl/J3f7zV p7EJ3u4PGlETZAHFc2mVWc9FZndPgJIHS491g8sglJqPLhe7c+GjbACCGeb8XtQr kMTkFl2xcM0fv6XQTkRoGlQrnVMlB35DbFgjk7You3X1eAH3ZYe1NzsSaek9qeol OqKSa/J2mNiwKtaSW/NY5cD2cScuu4pqVwNb6Ya1OamvrCobRvi9rnnwGT148rpe I9hDrK2q5n5sz3rzWi7IT0Yv3ao0JkjAZHGuHeLvJLzv3R29RleTITd728LEWbxk xVTvcgl4u7lrZuqmhcaB2xDYvHDLx2PKyDxRSW3R/oahTCMVm1gjYnIB+L1aHPMZ ulxpKK0rylp2sNGgG8Kr/aasDENNgoxo76+qvVixIJWXovJruvlCMHeyySE9Tn14 rOoQICuOaEiMkUqpnEWqyOEJQs2Ky8AeRiQLAj+Il3Ed0fG0qHxosuWm/EAztKWH 329XAaaILDMeqp5Y4niBRq3at7QKb3LABpDI8/wqn9n4y7koaLQGpwGQRkbJszgh JqGJ3Bwh4B4Absze4gzvCYyh3mt7dwgo6zvG1PJ8x1I/D+TtUkUdQBojXf5YteUY OTN9IPjXaBlm9hbO2D0fXWdaz9QJEh3nSSqWd9/FU9w+6ACZz8ZeJivRtrkCDQRY ddGZARAA3o4NQV87nvPVbPp8NzPqQoRt+TdDVzcq10fHHAs2vIlgNPqQmMLiw/a6 Nsx4oFXuaCdyvQ6QsWKTOH33Ui0q+SrCdr5vVUQT6OJgMt4dqWv39zSXZeDFuy9U bmsd1ym7MGcRgDrvMHYdiz7AP3C1zmaCrjB8yV4oARVwKOafD5VznJOtX17c08M8 x+EQzypwgGer0vT3OzeTbHqWd491IOfdD0ejbapTLkOMPblPriOwtkh+lcC9QXD+ cb7Y+/79KjEXFTXr97R66AXmlkeWSnqWqZbTWrwp5nn5OpkgnpXqSVynIafAwePg KZCsVSCwMeo4aguj8znyUCd60lbc/WPhXnjmYXBHYXsUf4OMCa8P/yBkiC6jyYA/ zHKeJZgR2Nlu945flszQjc115tVo1dWqdxmB3cq9TBVu+6Npzgz28TD/I6NUekyE Gv/ESwbI3b7vbW/dBDiL6r8aGYFTvW+EmfCajOjZHT93hiz83JIpHOrIhibnGiMA bja8Lk6s3WZ5LmA03T2PhKj3Mo0Rx8FXl/+7GU8H3mYHJwpHSSoBuvswDOH6SQVB Yb+ckBzloiQ+cccIWuDItskc0Jeq1MB+FPgCfscT5B5545euT8Sq0aNHs4D5gRey 1e0X8eCAXZsyuuXpnOL8+8ty3WjwMmR8mgtjL4wXxP3CXPnvYFkAEQEAAYkCHwQY AQgACQUCWHXRmQIbDAAKCRDihi2oPd1kc22EEACwfwplUbvVtflOh2MiOUWnXGHO xTff7RjITk0NpK/a4bPTKOWdWKenTePSy8UCYIUK2u8dH6RrAq7L/OpoysltvJi3 ktKpkjr5mpXtywd0HKOEWoHrIj+Z2ZDubDVe9/cPYBuZdzaqxQ+P+Dc3NNh53RCf iXxbftk1D86jjfKoBj1aGPEPUSQHpW1Iw/Kh5E+dKN02oALjUudyjfv2byJ+niqO qbkHgIuUsOTWaWKwgMqgTbjW4NeMj+7DJcskM8NUnBLjiT+WG1wW8Teom/PakD32 ZFt5bIO7xVE4NP9wiFxH/dlXuxQLyg0TON2xUrBtN+/LRGJVQvl6iglmf1KxAkv9 maSGBFXtZY5tyA2UBwFJZ2D6XjeaVdFfIfa5rcUY3PTwt8kECivr5AHN3qrz3wuS QkHb/HQm7SeMZs3h02VEfHhmGxv98TwRF1rSCXRBORLDnY7Bh5WTdaR9CoDTU0aw Bvo4vHH8EODU7bJwfCuaCprzIP/Vbl+PYxU5W180pd/XaQXk9XERcn86b9n9q4Ea 9+CqXIRGal/DLBZRjmq8xN33dHfMnbP+N2ik09Zz0zdZHVsCQRK3xFFIwK9OpFdx Xa/drJTa58B7rogm4DBXgI63hjDZN+FZTpxRpKWHstfStVYQk8Kfu2hir1e6FF2s /Ijrx6DPmuYb/0e0Kg===Fv5C -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQINBFh10ZkBEAC3QTfDVUmKlKl5JNvy7kHulRj7nXYeYEywyXo5zsYsvWeCRYit WqwOr8PgGVO+jmXSxkXxjnGvXF7Kr1qZRHy/1hJxwFztlsgzkYzJOQYqB5Wpgxgf tpkZmY/uOzg61ppvSF8OKteal+jZnPEwGtGr6MNEc4WZecE99NA3tQ9kiqr0wHJE UstgiFv1DV4ju/nqCoaplVCy2LVdTq/IPXXJPozUYYM4U5S6qNPWgg8NKUUAPkkZ kJrgd2PD0qayU5HxO9lIHlwt1f9dp0iwXafXF4DkivMmpipoKB7e6eS+LYYTHQVz rmn+Goco7m34TsBua0ltjY5KDz7Nlts5bOFOYgCLrnpJJggACPetCr1NFQVbkaLb qpZ8hRkuJl5fKR/55lhLMSC7Bh85b4UQioS83ChyyY3dgNuXzss41/gn7sp0VUuA oQg+YYia3vWmOaBSXlQmM8ukw9QcMiVje4qlUaZjsCcNKwRCEX6YvcY1X8Yzm6uv yycPvroTIiJE1YZOVRj2oGSqNftZWtTnebVEveIezF/tX7Tadf6xq6kaQdUZzbAv tX+O/jOTGfo/8XECXPrLiPXlwY3ZrloXMr1QSBJQxZoCkfuDsi9Lek3SvWmxrQuM 0q66bk4k7LrO7e0lNueLSmna4OZFih/FUFwAq+bH6SciF9eOxm6NOPrnXwARAQAB tC9mcmVkYSAoc3RyZW5ndGggaW4gbnVtYmVycykgPEZyZWRhQHNpZ2FpbnQub3Jn PokCNwQTAQgAIQUCWHXRmQIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRDi hi2oPd1kcz6hEACyDgzf+L0OpB9Znsx7EEt8N1/zGyzGQoL/MQVsxMiJl/J3f7zV p7EJ3u4PGlETZAHFc2mVWc9FZndPgJIHS491g8sglJqPLhe7c+GjbACCGeb8XtQr kMTkFl2xcM0fv6XQTkRoGlQrnVMlB35DbFgjk7You3X1eAH3ZYe1NzsSaek9qeol OqKSa/J2mNiwKtaSW/NY5cD2cScuu4pqVwNb6Ya1OamvrCobRvi9rnnwGT148rpe I9hDrK2q5n5sz3rzWi7IT0Yv3ao0JkjAZHGuHeLvJLzv3R29RleTITd728LEWbxk xVTvcgl4u7lrZuqmhcaB2xDYvHDLx2PKyDxRSW3R/oahTCMVm1gjYnIB+L1aHPMZ ulxpKK0rylp2sNGgG8Kr/aasDENNgoxo76+qvVixIJWXovJruvlCMHeyySE9Tn14 rOoQICuOaEiMkUqpnEWqyOEJQs2Ky8AeRiQLAj+Il3Ed0fG0qHxosuWm/EAztKWH 329XAaaILDMeqp5Y4niBRq3at7QKb3LABpDI8/wqn9n4y7koaLQGpwGQRkbJszgh JqGJ3Bwh4B4Absze4gzvCYyh3mt7dwgo6zvG1PJ8x1I/D+TtUkUdQBojXf5YteUY OTN9IPjXaBlm9hbO2D0fXWdaz9QJEh3nSSqWd9/FU9w+6ACZz8ZeJivRtrkCDQRY ddGZARAA3o4NQV87nvPVbPp8NzPqQoRt+TdDVzcq10fHHAs2vIlgNPqQmMLiw/a6 Nsx4oFXuaCdyvQ6QsWKTOH33Ui0q+SrCdr5vVUQT6OJgMt4dqWv39zSXZeDFuy9U bmsd1ym7MGcRgDrvMHYdiz7AP3C1zmaCrjB8yV4oARVwKOafD5VznJOtX17c08M8 x+EQzypwgGer0vT3OzeTbHqWd491IOfdD0ejbapTLkOMPblPriOwtkh+lcC9QXD+ cb7Y+/79KjEXFTXr97R66AXmlkeWSnqWqZbTWrwp5nn5OpkgnpXqSVynIafAwePg KZCsVSCwMeo4aguj8znyUCd60lbc/WPhXnjmYXBHYXsUf4OMCa8P/yBkiC6jyYA/ zHKeJZgR2Nlu945flszQjc115tVo1dWqdxmB3cq9TBVu+6Npzgz28TD/I6NUekyE Gv/ESwbI3b7vbW/dBDiL6r8aGYFTvW+EmfCajOjZHT93hiz83JIpHOrIhibnGiMA bja8Lk6s3WZ5LmA03T2PhKj3Mo0Rx8FXl/+7GU8H3mYHJwpHSSoBuvswDOH6SQVB Yb+ckBzloiQ+cccIWuDItskc0Jeq1MB+FPgCfscT5B5545euT8Sq0aNHs4D5gRey 1e0X8eCAXZsyuuXpnOL8+8ty3WjwMmR8mgtjL4wXxP3CXPnvYFkAEQEAAYkCHwQY AQgACQUCWHXRmQIbDAAKCRDihi2oPd1kc22EEACwfwplUbvVtflOh2MiOUWnXGHO xTff7RjITk0NpK/a4bPTKOWdWKenTePSy8UCYIUK2u8dH6RrAq7L/OpoysltvJi3 ktKpkjr5mpXtywd0HKOEWoHrIj+Z2ZDubDVe9/cPYBuZdzaqxQ+P+Dc3NNh53RCf iXxbftk1D86jjfKoBj1aGPEPUSQHpW1Iw/Kh5E+dKN02oALjUudyjfv2byJ+niqO qbkHgIuUsOTWaWKwgMqgTbjW4NeMj+7DJcskM8NUnBLjiT+WG1wW8Teom/PakD32 ZFt5bIO7xVE4NP9wiFxH/dlXuxQLyg0TON2xUrBtN+/LRGJVQvl6iglmf1KxAkv9 maSGBFXtZY5tyA2UBwFJZ2D6XjeaVdFfIfa5rcUY3PTwt8kECivr5AHN3qrz3wuS QkHb/HQm7SeMZs3h02VEfHhmGxv98TwRF1rSCXRBORLDnY7Bh5WTdaR9CoDTU0aw Bvo4vHH8EODU7bJwfCuaCprzIP/Vbl+PYxU5W180pd/XaQXk9XERcn86b9n9q4Ea 9+CqXIRGal/DLBZRjmq8xN33dHfMnbP+N2ik09Zz0zdZHVsCQRK3xFFIwK9OpFdx Xa/drJTa58B7rogm4DBXgI63hjDZN+FZTpxRpKWHstfStVYQk8Kfu2hir1e6FF2s /Ijrx6DPmuYb/0e0Kg===Fv5C -----END PGP PUBLIC KEY BLOCK-----

8 10

Good Bad ISP - update required
by Petrusko 18 Jan '17

18 Jan '17

Hey, Sorry to disturb about that... I'm trying to find a way to update/add informations on this page : https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs I have mailed a vps provider about running Tor relays on their DC, and there's no problem about running it. About exit node, it can be (like others) more dangerous if they have a lot of abuse mails (for sure it can be solved, but I'm not an expert with that :p) So it's possible to update informations on this page... If there's a mail address to inform ? Or here on this mailing list ?... Thx :) -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5

1 0

Some problems with new Exit Node
by Alan 17 Jan '17

17 Jan '17

So I bit the bullet and started running an Exit Node (Andromeda), still early days with a few problems, namely:- # It hasn't been given a Stable flag yet. # Some problem with dns resulting in [WARN] eventdns: All nameservers have failed - i've switched the dns to 8.8.8.8, only seen that error once since # The Consensus Weight was gaining nicely and reached over 7,000 but now has dive bombed to just 20, with that the speed dropped from ~50mbps to ~5mbps https://atlas.torproject.org/#details/FDB4FC238F13E7FEC99D025DB8B89A636EFC1… Is this all normal or something i've overlooked? Alan

4 4

Uptime missing from Arm
by Alan 17 Jan '17

17 Jan '17

I have 3 relays running but on Arm only one shows the uptime. Also the Averages it keeps are way off. Alan.

11 27

FW: What's a "useful" mailing list contributor? (was Re: What's a "useful" relay?)
by Rana 17 Jan '17

17 Jan '17

Wow. I offer to maintain a FAQ for small relays and in return I get this. Unsubscribed. On 3 Jan 2017, at 17:57, Rana <ranaventures(a)gmail.com <mailto:ranaventures@gmail.com> > wrote: @teor I hereby volunteer to maintain a FAQ for operators of small relays (or noob operators). Which means I would be watching this list, generating the Q&A and from time to time alerting this list to the appearance of new questions and answers, to allow knowledgeable people to do quality control. And/or inviting people to convert their answers on this list to the FAQ answers. This would relieve them from answering the same question over and over again and reduce the influx of questions from noobs (like myself J). I believe this would also strengthen the community and reduce the frustration of small relay operators and – who knows? – even lead to advancements in Tor design to make better use of them. I would appreciate that, but please learn some mailing list etiquette first. Otherwise, your contributions may be ignored by many people on the list. Some examples: * make sure each email adds something valuable to the conversation * structure your emails well: * learn how to bottom-post, even if your email client doesn't support it * learn how to quote others' emails to provide context to your response * try to write succinctly * keep the volume of your emails down: * write one response to a thread each day * search for similar threads before starting a new one * wait until an active thread is finished before starting a new one Caveat: I need someone (Tor project people) to create the Wiki on the site and let me admin it. Demonstrate you can do the things above, and I'll gladly set this up for you. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org _____

7 6

assign_to_cpuworker failed
by Felix 16 Jan '17

16 Jan '17

Hi diffusae > The only warning I have found close to it: > > "Jan 13 11:08:46.000 [warn] Your system clock just jumped 216 seconds > forward; assuming established circuits no longer work" > > That could be due to the IPv4 autodetection? Maybe I should explicitly > set the Address option in torrc? There was similar on 027 but more massive including * assign_to_cpuworker failed * Your system clock just jumped * stalling for seconds Which is resolved since 0289. 'Address' was key. https:// trac.torproject.org/projects/tor/ticket/20423#comment:27 -- imho - like always

2 1

(no subject)
by mario matko 15 Jan '17

15 Jan '17

mario

1 0

Entry relay still the same after months?weeks/
by je suis 15 Jan '17

15 Jan '17

Hello everyone And my apologies if this turns out to be a simple, obvious answer, but ever since two(?) upgrades back, my entry relay never changed. I manually deleted Browser/TorBrowser/Data/Tor/state and only then it changed. As of the last delete, it never changed, not with "New identity" or with "New Tor circuit for this site". Is this an intended behaviour? Thank you in advance, Vlad

2 2

torworld relays in entry and exit position
by nusenu 14 Jan '17

14 Jan '17

Hi torworld, thanks for joining the tor network with your relays! You are operating entry and exit relays without proper 'MyFamily' configuration, this can be dangerous for tor clients because they might choose you as entry _and_ exit relay, please help protect tor clients by properly specifying the MyFamily configuration in your torrc files. If you need any help please let us know. https://www.torworld.org/ https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… https://lists.riseup.net/www/arc/ornetradar/2016-10/msg00101.html kind regards, nusenu https://github.com/nusenu/ansible-relayor

1 1

Exit filtering Necto3 93.115.95.204
by Geoff Down 13 Jan '17

13 Jan '17

Would the operator of the above mentioned exit please remove OpenDNS 'Malicious URL' filtering. Thanks, GD (PS having a .onion contact address doesn't work, I think....) -- http://www.fastmail.com - Same, same, but different...

3 2

All I want for Chrismas is a bloody t-shirt
by I 11 Jan '17

11 Jan '17

9 19

Re: [tor-relays] How can we trust the guards?
by Rana 10 Jan '17

10 Jan '17

@Aeris I do not see how Sybil attacks relate to my question. The adversary will simply set up new nodes, without messing with attacking identities of existing ones. As to the rest of it, let us calculate. Assuming that the adversary wants to control 4000 nodes for 3 years, the 70d startup period is irrelevant and negligible. Assuming further that operating the relays will cost the adversary $20/month each, the total "investment" required would be 20x12x3x4000=less than $3million That’s $1million a year to control most of the Tor nodes., You call this "costly"? This amount is a joke, a trifle, petty cash for any US or Russian government agency. FIFTY times this amount is STILL petty cash, so in case you think $20/month is not enough to run a relay, make it $1000 a month. So I repeat - how is this prevented?

11 30

Re: [tor-relays] What's a "useful" relay?
by Rana 10 Jan '17

10 Jan '17

@Ivan >Some best practices definitely would be awesome to have about running on common (embedded) hardware. Clear notification like "your Commodore 64 is to slow to be a good relay" would also be useful. I agree about the need for guidelines but I disagree about the content of the guidelines that are needed. The data I see so far, including your report of a Pi with 7000 connections, is a clear indication that minimal hardware capabilities are NOT the guidelines that are needed (unless a relay with 7000 connections is still considered "harmful" or "useless"). My own Pi-based relay https://atlas.torproject.org/#details/707A9A3358E0D8653089AF32A097570A96400… has just reached 1300 connections; CPU utilization: practically zero; memory utilization: 14.5%. The increase from 500 to 1300 connections required memory utilization increase of just 2%, from 12.5% to 14.5%. Clearly, hardware of the $35 Pi has absolutely nothing to do with residential relays being useful or not, save the (recently reported here) anomaly of an operator who has symmetric BW of 160 mbps to the home. So guidelines on hardware are evidently not needed for "normal" residential ISP bandwidth: it has been amply demonstrated that even a dirt cheap Pi is not the bottleneck, no need to spend further effort on this until the REAL bottleneck is resolved: the network. To continue the story, the above relay of mine with 1300 connections has consensus BW rating of 38 (thirty eight). Why? Who knows. I get zero feedback on the reason for this. To further continue the story, my 2nd relay https://atlas.torproject.org/#details/31B8C4C4F1C78F923BD906769297B15A428C4… that currently has about the same Atlas-measured BW as the first relay (132 vs 153 KB/s) and is based on exactly the same hardware and software, is clinically dead with almost no connections and BW rating of 13. Why? Who knows. What is needed is a standardized feedback on WHY the relay has such a low rating. This could cause at least part of the operators to take care of the bottleneck (eg moving the relay to another location, or abandoning the home relay and replacing it with a hosted one). And if the home relay is indeed as harmful as some people here think, the recommendation should be issued to shut it down, instead of leaving it hanging there doing nothing or even harming Tor. Such feedback could significantly improve the quality and effectiveness of Tor. Based on the discussion here, the people who run Dirauths and bwauths know very well (or at least can easily find out) the reasons for relays getting low rating - why not automate the communication of the reasons to relay operators in clear, unequivocal and actionable terms? I get the feeling that people are trying to be "politically correct" here and it's a pity (although they DO respond fully and frankly when asked a direct question). Rana

2 3

Disparity between download and upload traffic
by Gage Parrott 10 Jan '17

10 Jan '17

Morning, everyone, I recently migrated my bridge relay over to a VM and everything seems to be working fine except for one oddity. I consistently see lines like this in tor's log file on the new machine: Dec 25 23:48:14.000 [notice] Heartbeat: Tor's uptime is 4 days 5:59 hours, with 43 circuits open. I've sent 1.78 GB and received 28.37 GB. Dec 25 23:48:14.000 [notice] Heartbeat: In the last 6 hours, I have seen 2 unique clients. Dec 26 05:48:14.000 [notice] Heartbeat: Tor's uptime is 4 days 11:59 hours, with 105 circuits open. I've sent 1.87 GB and received 29.24 GB. Dec 26 05:48:14.000 [notice] Heartbeat: In the last 6 hours, I have seen 2 unique clients. Notice the amount of data sent and received. Can anyone think of why there would be such a large discrepancy between the amount of traffic downloaded versus uploaded? This behavior persists after reboots, as well. I thought maybe it was downloading a ton of directory data, but is there really a GB's worth of directory data to download every six hours?? Also, the logs on my old machine (pre-migration, one line pasted below for reference) indicated that nearly the same amount of data was being sent as was being received. Any ideas on why would this have changed? Dec 07 06:02:03.000 [notice] Heartbeat: Tor's uptime is 4 days 6:12 hours, with 78 circuits open. I've sent 33.71 GB and received 33.47 GB. Any help is greatly appreciated. Thanks a bunch and merry Christmas! gp

2 3

Re: [tor-relays] Call for Tor Fallback Directories
by l3thal 09 Jan '17

09 Jan '17

please add my relays as fallback mirrors, thanks On Dec 4, 2016 5:45 AM, "teor" <teor2345(a)gmail.com> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Tor Relay Operator, Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0] These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release. Fallbacks need to have: - - the same IP address(es) and ports for the next 2 years, - - the same relay identity key for the next 2 years, - - good uptime (at least 95%), and - - good bandwidth and network connectivity (we estimate an extra 25GB per month). Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it. We are keeping the fallback lists from the last release[1][2]. So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.) In a week or two, I will run a script to select the hard-coded list for the release. If you're interested, here's some background to this request: The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7]. [0]: https://trac.torproject.org/projects/tor/wiki/doc/ FallbackDirectoryMirrors [1]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.whitelist [2]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.blacklist [3]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04 [4]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04.log [5]: https://trac.torproject.org/projects/tor/wiki/doc/ UpdatingFallbackDirectoryMirrors [6]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/ updateFallbackDirs.py [7]: https://trac.torproject.org/projects/tor/ticket/18828 T - -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org - ------------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYQ+laAAoJEEUMun+WjwlLXd8QAMVKWrGW+N5ij5/1k1AEDQpC qMK3C3stukeuHYqLEU3GnhJFU/CWMp+iThRNueC5I96MEpcioJDQaCDK6aGEvTY3 efPnYwOJcgE7v4up+JSFWUlO4HcF5Fu5cSVl710JjRiHuZAyLOQw0rWEMzfp0OQp sZLgijbtCUCcels7IS+bE89y4KKQvLu5lz+H7cPIcsx4TJ4QHd5LbWuvtNIHE2lW zA3LlrYsO4vtrFs/0kBWku1u7l1ZhD0Un/lwY7JWaxGmwm9C6kJDFwBFCGYRlakF VLfsoVSgcdjQPkZV9jeL0X+9Wn9L6zZ5JNhM5lhYYpGVD+Rl/apPfhxHI5aOTsGe WRcDjxvgUdMD//xnk2XTmnzKCNUNMyUKGSL8Y7Fadp7+dLLkWlovEp6iOnyAffh1 ZnrV7dhRgH3NcgACDpQ2rAqVzUnhdn1//bcD1MlXjObxvZD1Io1zp7CDQHnG6IaG ydc+3qoqUoII0JQFxrRCFi2cH/E8+3x0+7fC0g91irdGG+Pcosf7IFPJvFsdilCg rN4n6Ohmm1L3KQVWLG7TcvEAcjIeyMurhCvK042Q/X7HYenVS3wVxawd8dnb/rOl 0ItMUsXBKgLVcZXhzUTOB+pNaX8aFj1sJnCB2LRDT8s8a2+zESufNxjgGYZ3Nduk FziDqhHJs7MXyX0HPJPH =omox -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Running a relay with low transfer limits
by ike 09 Jan '17

09 Jan '17

Hi folks, Is there a generally accepted recommendation for how to set up a relay on a server with a fast connection but limited monthly transfers, say less than 100GB each way per month? Having done a bit of reading it seems daily limits are the way to go but I've found contradictory information regarding also limiting the bandwidth. Should I keep the relay accepting traffic (albeit slowly) for most of the day, allow a fast connection but for a very limited period every 24 hours or something in between. Thanks, Ike

8 9

Some thoughts from a tor bridge op
by a tor op 08 Jan '17

08 Jan '17

Hi I am a TOR bridge operator running a bridge with 8 Mbps advertised BW and having obfs4 installed. Been up a year or so on this install. I'll put a few misc thoughts out here, only been lurking on list earlier. I have been thinking a little about how useful this system is (MY bridge that is), in part since I haven't seen so much traffic lately. The latest few months I have seen some 1-4 (concurrent?) users according to Atlas whereas I had up to 10 during a year ago. There is also a count in tor log abut how many clients that have been seen in the latest hours etc. I then had a drop til nil due to not being updated when Lucky removed his Bridge Authority I think, or related to some other more or less related technical issue. What is a normal figure on this, anybody know? The thing is, in tor log it is reported that all is fine and that connectivity is ok. In Atlas these flags are reported: Fast Guard HSDir Running Stable V2Dir However, I have been thinking about a few other issues too though. One is, I noted that my provider gives this particular VPS a private IP address and traffic is NATed to the VPS according to info in the control panel. I do see a few GBs being pushed every other day so I guess things are kind of working, though. Is there something I may need to edit in config? Specifically the "OR Adresses" being mentioned on Atlas page contains a port that is not opened in local FW on server. Still it works and gets some client traffic(?) In torrc I some time earlier put in "ExtORPort auto" and also another port that is opened in FW using "ORPort". I also have the "ServerTransportListenAddr obfs4" with "0.0.0.0" and yet another port that is not being opened in FW, in the file. There are a few technicalities that might need some clearer explanation in manual/man/how-to I think. One thing I am thinking of is whether this private address and NATting issue makes the system not perform as I intend (although I do see some traffic as mentioned). Just a few thoughts. Any comments appreciated. A TOR bridge op

1 0

TOR Relay performance issue
by Thomas Maurice 08 Jan '17

08 Jan '17

Hello all ! o/ It seems I am running into a performance issue with my relay, and I am not able to troubleshoot it, so I hope someone could point out something obvious I am missing! (for information, the relay is a 2vCPU, 2G RAM VM running on Scaleway) From what I observe from the graphs, my maximal CPU usage ceils at ~60%, and the load ceils at 1 eventhough the TOR daemon is aware I have 2 cores available, and I set the NumCPUs configuration option accordingly) First I tought that the network did not want to send me more traffic, but my graphs are way too regular to make this eventuality plausible, so I am pretty convinced that it is due to a lack of optimization on my side. (link to my graphs for reference http://www.noelshack.com/2017-01-1483803911-constancesurvingt.png this is a 1 hour snapshot, but it has been this constant for at least one day) My first hypothesis was that the daemon is running out of file descriptors, so I raised the limit that was in the defaults (doubled it actually, by editing /etc/init.d/tor like a pig, to test), but I did not observe any change in Grafana. It is supposed to be caped at 20MBps, and 25MBps burst so I doubt the limitation I am observing is enforced by the node itself. If anyone had any pointers I would be grateful! Cheers! -- Thomas

4 4

c23088def3e324089ed7bbe4b00082b251c06026
by mario 07 Jan '17

07 Jan '17

1 0

Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors
by Kurt Besig 06 Jan '17

06 Jan '17

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay to start unless I sudo. When I attempt to start tor as a non-privileged user I get a permissions error: Opening Jan 05 18:33:35.929 [notice] Opening OR listener on 0.0.0.0:443 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:443: Permission denied Jan 05 18:33:35.930 [notice] Opening Directory listener on 0.0.0.0:80 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:80: Permission denied Ideas on best method to bind these ports to tor on startup as non-root? Thanks

5 5

Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors
by Kurt Besig 05 Jan '17

05 Jan '17

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay to start unless I sudo. When I attempt to start tor as a non-privileged user I get a permissions error: Opening Jan 05 18:33:35.929 [notice] Opening OR listener on 0.0.0.0:443 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:443: Permission denied Jan 05 18:33:35.930 [notice] Opening Directory listener on 0.0.0.0:80 Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:80: Permission denied Ideas on best method to bind these ports to tor on startup as non-root? Thanks sorry for the dup..

1 0

Faravahar acting up again / "Bad Gateway" while uploading descriptor
by anondroid 05 Jan '17

05 Jan '17

I just set up a handful of new relays, and all of them have something like the following in their logs: [WARN] http status 502 ("Bad Gateway") reason unexpected while uploading descriptor to server '154.35.175.225:80' [WARN] Received http status code 502 ("Bad Gateway") from server '154.35.175.225:80' while fetching... This appears to be related to the authority Faravahar. I know this has happened before but I wanted to make sure the proper people were aware of the issue. Thanks.

4 4

zwiebeln@online.de relays: MyFamily update required (was: [OrNetRadar] Contact: "<zwiebeln at online de>")
by nusenu 05 Jan '17

05 Jan '17

Hi zwiebeln, thanks for running so many tor exit instances and adding so many yesterday. Please do not forget to add your new relays to your MyFamily, your "old" relays had a proper MyFamily configuration. thanks, nusenu https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… +---------------------+-----------------+---------------+------+ | first_seen | IP | MyFamilyCount | exit | +---------------------+-----------------+---------------+------+ | 2016-04-11 21:00:00 | 178.17.170.179 | 25.0000 | 1 | | 2016-05-14 15:00:00 | 195.123.209.184 | 25.0000 | 1 | | 2016-07-03 15:00:00 | 178.17.170.179 | 25.0000 | 1 | | 2016-08-28 12:00:00 | 37.157.193.161 | 25.0000 | 1 | | 2016-09-10 14:00:00 | 37.157.193.161 | 25.0000 | 1 | | 2016-09-16 21:00:00 | 89.221.209.100 | 25.0000 | 1 | | 2016-09-18 12:00:00 | 37.157.196.97 | 25.0000 | 1 | | 2016-09-27 10:00:00 | 37.157.196.97 | 25.0000 | 1 | | 2016-09-27 10:00:00 | 89.221.209.100 | 25.0000 | 1 | | 2016-11-12 21:00:00 | 144.217.60.211 | 25.0000 | 1 | | 2016-11-12 23:00:00 | 213.32.55.239 | 25.0000 | 1 | | 2016-11-14 12:00:00 | 149.202.238.204 | 25.0000 | 1 | | 2016-11-15 15:00:00 | 144.217.60.239 | 25.0000 | 1 | | 2016-11-15 15:00:00 | 158.58.170.150 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.212 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.27 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.212 | 25.0000 | 1 | | 2016-11-28 17:00:00 | 178.17.170.27 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 51.15.53.83 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 46.182.18.29 | 25.0000 | 1 | | 2016-12-05 16:00:00 | 51.15.53.83 | 25.0000 | 1 | | 2016-12-05 17:00:00 | 46.182.18.29 | 25.0000 | 1 | | 2016-12-05 17:00:00 | 46.182.18.214 | NULL | 1 | | 2016-12-16 20:00:00 | 88.151.99.224 | NULL | 1 | | 2016-12-18 18:00:00 | 185.14.29.129 | NULL | 0 | | 2016-12-18 22:00:00 | 149.202.238.204 | NULL | 0 | | 2016-12-18 22:00:00 | 144.217.60.239 | NULL | 0 | | 2016-12-18 22:00:00 | 144.217.60.211 | NULL | 0 | | 2016-12-18 22:00:00 | 213.32.55.239 | NULL | 0 | | 2016-12-18 23:00:00 | 158.58.170.150 | NULL | 0 | +---------------------+-----------------+---------------+------+ ornetradar(a)riseup.net: > 2016-12-18 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | AS | CC | ORp | Dirp | OS | Version | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 | 21:41:51 | 149.202.238.204 | OVH SAS | fr | 444 | 81 | Linux | 0.2.8.11 | alsaceonionb | 1 > 1 | 0 | 21:26:02 | 144.217.60.239 | OVH SAS | ca | 444 | 81 | Linux | 0.2.8.11 | quebeconionb | 1 > 1 | 0 | 21:31:09 | 144.217.60.211 | OVH SAS | ca | 444 | 81 | Linux | 0.2.8.11 | montrealonionb | 1 > 1 | 0 | 21:36:53 | 213.32.55.239 | OVH SAS | fr | 444 | 81 | Linux | 0.2.8.11 | strasbourgonionb | 1 > 1 | 0 | 22:24:55 | 158.58.170.150 | Seflow S.N.C. D | it | 444 | 81 | Linux | 0.2.8.11 | milanoonionb | 1 > 1 | 0 | 17:42:44 | 185.14.29.129 | Serverius Holdi | nl | 9001 | 9030 | FreeBSD | 0.2.8.11 | humboldt | 1

2 5

Current pluggable transport recommendation
by Alexander Dietrich 05 Jan '17

05 Jan '17

Hi, the obfs2 pluggable transport was deprecated a while ago since it was easy to detect, but obfs3 was still considered safe, IIRC. Has anything changed here? I was just wondering if new bridges should only run obfs4, or if it's fine to run obfs3 at the same time. Best regards, Alexander -- PGP Key: https://dietrich.cx/pgp | 0x52FA4EE1722D54EB

2 1

High conntrack session count
by Sec INT 04 Jan '17

04 Jan '17

Hi Just had an issue on a 60mbps exit where conntrack sessions went over the usual 30000 limit - is this possible for a normal operating exit relay? Is there any default limit set on this or indeed is there a setting intorrc to control the number of sessions? Cheers Mark B Snaptor.co.uk (non commercial)

2 2