- tor-relays - lists.torproject.org

Fw: Undelivered Mail Returned to Sender
by syrus f 05 Nov '12

05 Nov '12

hello dear sir/madam I download tor (vidalia) on 05 Nov 2012 and I am in IRAN would you please tell me how remove problem step by step.

1 0

Status of NumCPUs >2 in 0.2.3.x?
by Steve Snyder 05 Nov '12

05 Nov '12

In the Tor v0.2.2.x series it was said that it was pointless to set NumCPUs to a value greater than 2. Due to poor scaling, I guess. Is that still the case with v0.2.3.24+ ? Would NumCPUs value of 4 or 8 (on systems with that many CPU cores) actually provide any benefit over a value of 2? Thanks.

2 1

Map of Tor Relays updated
by Moritz Bartl 28 Oct '12

28 Oct '12

Hi, I updated my small Python script that visualize Tor relays on Google Maps/Earth and OpenStreetMap. You can see the results generated today here: - All relays (2668): http://maps.burningsilicon.net/index.php?url=https%3A%2F%2Fwww.torservers.n… http://maps.google.com/maps?q=http:%2F%2Fwww.torservers.net%2Fmisc%2Ftormap… - Exits only (786 plus 153 "fast" exits >2MB/s) http://maps.burningsilicon.net/index.php?url=https%3A%2F%2Fwww.torservers.n… http://maps.google.com/maps?q=http:%2F%2Fwww.torservers.net%2Fmisc%2Ftormap… - Screenshot Exits only: https://www.torservers.net/misc/tormap/tormap.png - Download KML, eg. for use in Google Earth (works best): https://www.torservers.net/misc/tormap/tormap.kml https://www.torservers.net/misc/tormap/tormap-exitsonly.kml - Script: https://github.com/moba/tormap Colors: Red: Exits >2MB/s, Green: Exits <2MB/s, Yellow Star: Stable middle nodes >2MB/s, Yellow: Stable middle nodes <2MB/s, White: Other (unstable) I used the Maxmind GeoIP CityLite database. The markers might give a false impression of accuracy. Most IPs can only be tracked to city level (or even region), ie. the markers are somewhat near, not necessarily at the real location of the relay. -- Moritz Bartl https://www.torservers.net/

2 1

How to diagnose lack of traffic on bridge?
by Steve Snyder 27 Oct '12

27 Oct '12

I have a bridge that gets no traffic. I don't mean "hardly any" traffic; I mean none. The contents of bridge-stats are always empty except for the date, which advances once per day. In the state file the last date, apart from daily accounting entries, is a EntryGuardAddedBy entry from 09 Sep 2012. Yeah, that's six weeks ago. The log file contains only a weekly notice of log file rotation and a daily notice of bandwidth self-test. I never see errors or even warnings in the log. My bridge is not unstable. It has been running continuously for the last 25 days, which is pretty typical for this bridge. I understand that bridges can be identified and their IP addresses blocked. But I am not lacking traffic just from China, or just from Iran, or just from any other entity. It doesn't seem likely that my IP address has been blacklisted by *everybody*. I am also aware that the bridge authorities seem to favor handing out some addresses more than others. Really, though, this IP address is never given out at all? What are the odds of that? On the rare occasions that I restart the bridge, I see in the log that my ORPort is reachable from outside and that my server descriptor is being published. That's nice. Also, I am running the current stable version of Tor, so it is not a matter of obsolete software. How can I diagnose the failure of my bridge to garner any traffic? Thanks.

4 5

Need help: High capacity exit relay does not get traffic
by tor-admin 25 Oct '12

25 Oct '12

Hi, I am operating two 1 GBit/s servers which host 7 exit nodes. One server is located in GB with torland1 https://atlas.torproject.org/#details/4E377F91D326552AAE818D5A17BC3EF79639C… torland2 https://atlas.torproject.org/#details/332895D092C2524A3CDE8F6E1498FFE665EBF… torland1 is configured to run at maximum bandwidth, torland2 runs trottled to ensure not to exceed the 100TB contractual traffic limit. The nodes on this server get traffic as expected and are at the top of the Blutmagie Tor Status http://torstatus.blutmagie.de/index.php?SR=Bandwidth&SO=Desc. The second server is located in RO and hosts torland3 https://atlas.torproject.org/#details/E5DB403858511BB166405E4C43776D933A7B8… torland4 https://atlas.torproject.org/#details/E0D2F8B2A18516A5C935477B06048D7BD2E7E… torland5 https://atlas.torproject.org/#details/D2F1745C11843BC5AF09CB9D4027AD2BE5F1B… torland6 https://atlas.torproject.org/#details/43F9022028F8AB0F7420F702CB079DF0CA0C8… The configuration for the GB and RO nodes is: Nickname TorLandX ORPort 443 DirPort 80 Address a.b.c.d ORListenAddress a.b.c.d DirListenAddress a.b.c.d OutboundBindAddress a.b.c.d RelayBandwidthRate 30 MBytes # max 30 RelayBandwidthBurst 100 MBytes # max 100 MaxOnionsPending 250 NumCPUs 4 On both servers AES-NI is used by openssl. Although the server in RO has the same configuration, same operating system and a similar hardware, it does not get traffic as the server in GB. At the moment Atlas shows for torland3-6 only an advertised bandwidth rate of less the 3 MB/s. The GB node torland1 shows more than 30 MB/s. In order to test if there are any traffic limits I did several speed tests by doing up and downloads of a large 4GB iso image. Downloading simultaneously with 10 curl instances from different debian mirrors I measured around 1 GBit/s. To measure upload I stored the debian 4GB iso image on the webserver of the RO server and used curl on the GB server to download it from RO. The maximal measured upstream speed on the RO server was around 750 Mbit/s. Therefore I looks for me as there are no traffic limits inplace by my ISP or their upstream. One of the servers operated by Torservers.net is located in the same data center and runs wau, gorz and sofia at high speed. I am wondering why the directory authorities only measure such a small fraction of the available bandwidth for the RO nodes. Because I am paying personally for the server I would like to get most out of the server. Can someone who runs a tor authority please help me to understand what is the reason for the low observed bandwidth. Thanks, Torland

2 2

Announcing the Walla Walla Project
by admin 23 Oct '12

23 Oct '12

Hi, I'm representing the Walla Walla Project, a volunteer initiative that aims to support the Tor network by contributing (exit-)relays and bridges to the network, and I would like to quickly announce today's (initial) launch of our humble project to the Tor relay operator mailinglist. Without any further ado, our project website is available at http://wallawallaproject.org/ We certainly very much welcome questions, comments and suggestions! Have a great day. On behalf of the Walla Walla Project team, Thomas

5 10

Running relay on OpenBSD ulimit problems
by Gijs 18 Oct '12

18 Oct '12

Hey guys, I just created a new relay on my new firewall box thats running openbsd, however I'm running into issues with ulimits: Failing because we have 991 connections already. Please raise your ulimit -n. I tried editing login.conf (might be doing it wrong) to no avail Anyone able to help me out ? Gijs

2 2

openBSD question.
by sharon dvir 12 Oct '12

12 Oct '12

sorry to bother you guys, and i hope its not a dumb repeated question. but which of the two following options is preferred for an exit node on openBSD? - run the Tor package available through the openBSD repositories, which is 2.2.35 but probably been reviewed by the openBSD team. or - compile and use 2.2.39 which is not as obsolete? thanks

3 2

interesting sequence of messages
by Scott Bennett 10 Oct '12

10 Oct '12

I'm running 0.2.4.3-alpha and had to restart it during the night due to a system crash. As it was starting up, it put out the following sequence of messages. Oct 08 00:38:44.616 [notice] We now have enough directory information to build circuits. Oct 08 00:38:44.616 [notice] Bootstrapped 80%: Connecting to the Tor network. Oct 08 00:38:45.728 [notice] Bootstrapped 85%: Finishing handshake with first hop. Oct 08 00:38:46.130 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 08 00:38:46.359 [notice] Bootstrapped 90%: Establishing a Tor circuit. Oct 08 00:38:48.930 [notice] Our directory information is no longer up-to-date enough to build circuits: We have only 1868/2874 usable descriptors. Oct 08 00:38:48.930 [notice] I learned some more directory information, but not enough to build a circuit: We have only 1868/2874 usable descriptors. Oct 08 00:38:49.495 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Oct 08 00:38:49.495 [notice] Bootstrapped 100%: Done. Oct 08 00:38:49.830 [notice] I learned some more directory information, but not enough to build a circuit: We have only 1917/2874 usable descriptors. Oct 08 00:38:50.062 [notice] I learned some more directory information, but not enough to build a circuit: We have only 2013/2874 usable descriptors. Oct 08 00:38:50.142 [notice] I learned some more directory information, but not enough to build a circuit: We have only 2108/2874 usable descriptors. Oct 08 00:38:50.229 [notice] We now have enough directory information to build circuits. Oct 08 00:38:51.476 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Oct 08 00:39:03.079 [notice] Performing bandwidth self-test...done. The above really are nothing new, but just a really clear example of the screwiness of some common messages. In particular, the "no longer up-to-date enough to build circuits" and "learned some more directory information, but not enough to build a circuit" messages apparently are issued at times and under conditions contrary to the textual content of those messages. Let's examine the sequence shown above. 1) tor claims to have enough information to build a circuit. 2) It begins doing so by establishing the first hop of a testing circuit. 3) The testing circuit connects to my tor's own ORPort, so... 4) it builds a circuit to publish a descriptor and publishes it. 5) In less than 5 seconds from the time tor had enough directory information to build circuits, enough of that information has expired that tor no longer can build circuits. 6) tor fetches some descriptors, but still claims not to be able to build circuits. 7) tor announces that it has build a client-side circuit and pronounces that its startup is 100% complete. 8) tor continues to fetch three more batches of descriptors, saying that it still needs more to be able to build circuits, even after having claimed to have just built another one. I conclude from the above that the text of the messages claiming not to have enough directory information to build circuits is in error and should be revised to reflect the actual situation and events more accurately. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

2 1

Problems Setting up Bridge Relay on AWS
by freeflow＠mail.md 06 Oct '12

06 Oct '12

Hi! I recently set up a bridge relay on my home broadband connection. Unfortunately my ISP is restricting bandwidth during what it refers to as "peak hours", usually between 16:00 & 00:00 each day. This is obviously having a detrimental affect on my bridge relay as both upstream & downstream bandwidth is severely limited during these times. So I decided to set up a bridge relay on AWS, using the documentation at https://cloud.torproject.org/#get_started During the set-up process I've experienced 2 separate problems which I've described below. These are the actions I've taken: 1) I've successfully registered my account with AWS. 2) I've navigated my web browser to https://cloud.torproject.org/#get_started 3) At the above mentioned web page I've chosen: Obfsproxy Bridges (required ports: 22, 443, 52176) eu-west-1-Ireland 4) The pre-configured image is selected, and I'm directed to the AWS Management Console. When I arrive on the AWS Management Console page my web browser (Firefox 15.0.1) presents me with a "Warning: Unresponsive Script" dialogue box. The dialogue box explains, "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: https://images-na.ssl-images-amazon.com/images [snip]... I chose to persevere & clicked "Continue" on the "Warning: Unresponsive Script" dialogue box. After being presented with another "Warning: Unresponsive Script" dialogue box I arrive at the "Choose an AMI" pane of the "Request Instances Wizard" which displays the pre-configured settings. It's at this stage that I begin to get confused... I've attempted to use the "Step-by-Step" instructions provided at https://cloud.torproject.org/#get_started The "Step-by-Step" instructions state, "Simply follow the steps as illustrated below, and your bridge will up and running in just a couple of minutes." With regard to the "Choose an AMI" pane the "Step-by-Step" instructions suggest, "Click "Continue". (No changes needed here.)" There doesn't appear to be an option to continue beyond the first pane (Choose an AMI), the only available option that I can see is to cancel (top right corner of the Choose an AMI/Request Instances Wizard pane). This takes me to the "Amazon EC2 Console Dashboard". However, because nothing has been set up, the EC2 Console Dashboard quite correctly informs me that there are no instances running. On the left-hand side of the Amazon EC2 Console Dashboard is the "Navigation" pane listing "Instances" & "Images" (including AMIs). So, I can see some of the required components that are incorporated into the "Request Instances Wizard" but I lack the experience to set up my AWS manually. So, more confusion! On the plus side the Amazon EC2 Console Dashboard does inform me that I've selected my chosen region which it reports is up & running. Maybe a "Continue" option isn't being displayed in the "Choose an AMI" pane because of the above-mentioned "Unresponsive Script" dialogue box, or maybe there's some other way to move through the "Request Instances Wizard" that I'm unaware of? I'm currently running java version 1.7.0_07 from Oracle Corporation on 12.04.1 LTS precise. I have no experience of setting up anything like an AWS so any help would be much appreciated & hopefully I can succeed in setting up my bridge relay! Best regards!

2 5