- tor-relays - lists.torproject.org

what's up(down) with gablemoo?
by starlight.2016q1＠binnacle.cx 21 Jan '16

21 Jan '16

Lately 'gabelmoo' had been bouncing down and up like a ping-pong ball. Because gabelmoo is a BWauth (of which only five exist) as well as a normal authority, the impact is greater than if it did not participate in bandwidth measurement. Disrupts the consensus median. Does anyone know anything about it? Thanks

2 1

Location of private key on Android?
by Christian Andersen 21 Jan '16

21 Jan '16

Hey guys, I'm running Orbot as a relay on my otherwise unused mobile. It works great! https://atlas.torproject.org/#details/B47A49120A51D28A6191BE9A67F102AA96F5F… But in case I ever need to move the relay to a real computer, or start using the mobile, I'll need the private key, but I can't seem to find it. My phone is Sony Xperia ZR, unrooted, running Android 5.1.1, 10.7.A.0.228 (possibly a Sony version number). Orbot is version 15.1.0-RC-2 (Tor 0.2.7.5-020120160125) I just updated from Google Play Store - I realize the version above (from the About-menu) doesn't reflect the Atlas-info. I don't know why. Root\Android\data shows no folders related to Orbot, I have unchecked "Hide system files" in the file managers I downloaded from Google Play store. - File Manager from ZenUI - File Manager from SAND STUDIO and - File Commander - File Manager from MobiSystems - - Which requires Premium to view hidden files(!). Any help is appreciated. Maybe i just need a non-sucky file manager? C A

1 0

arm /flags gives unknown
by Dr. Who 21 Jan '16

21 Jan '16

Since some months I monitored my tor instance via this one liner: echo "/info" | /usr/bin/arm -p | /bin/grep flags but it seems after updating to 0.2.7.6 it only gives my unknown as result. Has something changed the communication between tor and arm? Even manually I can only get this answer: >>> /info TeamTardis (330CD3DB6AD266DC70CDB512B036957D03D9BC59) address: 185.100.84.212:443 (ro) published: 06:28:21 2016-01-20 os: Linux version: 0.2.7.6 flags: unknown exit policy: reject 1-65535 contact: Team Tardis <drwho(a)posteo.is>

5 5

relays possible sybil
by tor-server-creator＠use.startmail.com 20 Jan '16

20 Jan '16

hi, just wondering whats the matter with these 66+ relays "cloudvps" ... guess they get vote, should we discard some iprages? thanks

3 3

Running a relay, only, in win7
by je suis 19 Jan '16

19 Jan '16

Hello all I'm sorry if I'm writing to the wrong list. Until recently and since some months back, I ran a tor relay under Linux, during daytime (only have my laptop), with 2.5/5MBps speed. Not much, it took an hour or two to really start, but it worked, I hope it helped a bit. Now I find I need to spend time in win7 more and I'd like to keep on running a relay, but I can't seem to get tor to work. Since the FAQ only says what Linux users should do and all my searches turned out to have Vidalia involved, I don't know how to make this work, so I'm asking for help: is there a place where I can read, or could you tell me what I need to do to run a relay in win7? Thank you in advance, Vlad

4 6

atlas not showing 3 days and 1 week graphs
by krishna e bera 19 Jan '16

19 Jan '16

Is atlas.torproject.org broken or changed? It seems to show only 1 month and longer graphs now.

5 6

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors
by starlight.2016q1＠binnacle.cx 19 Jan '16

19 Jan '16

I'd guess a bug in the version update script. At 19:20 1/12/2016 +0100, Aeris wrote: >> Are you *absoultely* certain that the config >> was not fiddled with at the time of this event? > >After grepping some logs, seems 13/12 was the day of a Tor >upgrade : > >2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 0.2.7.6-1~d80.jessie+1 >2015-12-13 10:48:39 configure tor:amd64 0.2.7.6-1~d80.jessie+1 > >Timing is good compare to the 10:48:46 of the consensus ! > >But I donât remember a config change after that, >perhaps only on /usr/share/tor/tor-service-defaults-torrc >or on a default config param change ? > >And perhaps the Tor reboot cause the DirPort to >be temporarily disabled (seems not human, only >2s duration) ? > >Regards, >-- >Aeris

2 4

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors
by starlight.2015q3＠binnacle.cx 18 Jan '16

18 Jan '16

Relay 'Binnacle' experienced outages due to a loose fiber-option junction in the overhead wires that has been repaired. I believe it would make the list if not for this and do not foresee further trouble. Has a static IP and another Verizon FiOS relay qualifies, a positive reflection on the network. Available if desired. Can configure IPv6 on the HE tunnel here if helpful. $ python updateFallbackDirs.py DEBUG:root:Failed to get an ipv6 address for 4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2. DEBUG:root:Adding uptime 4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2. DEBUG:root:4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2 not a candidate: guard avg too low (0.910189) { "dir_address":"108.53.208.157:80", "or_addresses":["108.53.208.157:443"], "contact":"starlight dot YYYYqQ at binnacle dot cx", "consensus_weight":17500, "fingerprint":"4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2", "recommended_version":true, "nickname":"Binnacle", "last_changed_address_or_port":"2015-06-12 18:00:00" }

3 3

Revised Opt-In Trial: Fallback Directory Mirrors
by Tim Wilson-Brown - teor 18 Jan '16

18 Jan '16

Hi all, Nick sent an email in December[0] asking relay operators to opt-in as a fallback directory mirror. This will help tor clients reach the tor network, and reduce the load on directory authorities.[1] We will keep the opt-ins and opt-outs submitted so far - no need to opt-in or opt-out again! If you run an under-utilised exit, we encourage you to opt-in as a fallback directory. We've also fixed a major bug that excluded some relays from the list. (Thanks starlight!) Here's the latest list of fallback directory candidates: https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_d… <https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_d…> This list was generated a few minutes ago from scripts/maint/updateFallbackDirs.py in my branch fallback-17887-17888-18035 on [2]. (This branch has some bug fixes compared to what's in master.) Tim [0]: https://lists.torproject.org/pipermail/tor-relays/2015-December/008361.html <https://lists.torproject.org/pipermail/tor-relays/2015-December/008361.html> [1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors <https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors> [2]: https://github.com/teor2345/tor.git <https://github.com/teor2345/tor.git> Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

6 13

Opt-In Trial: Fallback Directory Mirrors
by Felix 17 Jan '16

17 Jan '16

Hi I'm happy to bring in the relay Doedel22 '8FA37B93397015B2BC5A525C908485260BE9F422'. Best regards, Felix

3 2

Do less-secure pluggable transports on bridges render more-secure types useless?
by Rick Huebner 17 Jan '16

17 Jan '16

I've read that obfs4 and scramblesuit are very resistant ("immune" is so optimistic) to such things as active probes performed by the Great Firewall, which can quickly probe and detect older transports (and of course vanilla ORports), plus the older transports and ORports are subject to relatively quick detection through deep packet inspection once a user connects from there. Does it make sense to offer older more vulnerable transports along with newer more secure ones? If my bridge offers both obfs3 and obfs4, does that just mean that as soon as someone in China uses obfs3 it's detected and my IP address is blocked, making the obfs4 port unusable from there as well even though it would have avoided detection on its own? More fundamentally, does the bridge address server also publish vanilla ORports for those bridges which offer obfs4, and does a Chinese user accessing my bridge's ORport doom my entire bridge to immediate blockage from there? I can't imagine the GFW would be so kind as to only block the ORport's specific port number, I assume it blocks the entire bridge IP address, making all transports useless if any single one of them is detected. Would it be better to only offer obfs4 to avoid detection and blockage via older transports?

2 2

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors
by Joost Rijneveld 17 Jan '16

17 Jan '16

Hi all, > On 17 Dec 2015, at 15:07, Nick Mathewson wrote: > If your relay is on this list, and you expect it to be on the same IP > address(es) and port for at least 2 years, please consider opting-in > for this trial. I realise it's been a while since the last post in this thread, but I'd like to opt-in. Relay: kili DD85503F2D1F52EF9EAD621E942298F46CD2FC10 Cheers, Joost

3 3

Tor being blocked by mayor ISP in Mexico?
by Test This 17 Jan '16

17 Jan '16

Tor being blocked by mayor ISP in Mexico? I've been running an exit relay for about 2 years. Since new year's day, I noticed that my relay went down and was no longer listed in Globe or Atlas. Just like Fabian Bustillos Vega reported here: https://lists.torproject.org/pipermail/tor-relays/2016-January/008491.html a few days ago. Software version at the time: (was running without problems for almost five months) Tor: 2.6.10 openSSL: 1.0.1i libevent: 2.0.21 running on Linux At first, I thought it was a configuration error, so I double checked the TORRC file manually and with software (Vidalia and ARM). Everything was OK. I check the log file and found something very unusual, when trying to connect to the Tor network, there were several openSSL connection errors. Eventually after a while and several attempts, Tor connection was successful. Here's the error: *[warn]* 8 connections died in state connect()ing with SSL state (No SSL object) *[warn]* 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN *[warn]* Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 11; recommendation warn; host 7BE683E65D48141321C5ED92F075C55364AC7123 at 193.23.244.244:443) This happened for other host as well. Link to complete log <http://pastebin.com/vUXkfXNf>. *See note at bottom. I thought maybe some Tor's Directories went down or my router was dropping packets for some reason. Several hours later I restarted my router and tried to connect again. I got the same error. I went to the tor project website and read the release notes, I found that new versions were using a new *elliptic-curve* Diffie-Hellman function, so I decided to update Tor to version 2.7.6. The error appeared once again. I tried with The Tor Browser and again, it took a while to establish a connection. I had to abort and reconnect several times in order to establish a successful connection. With these results I tried some other software; *TAILS* (Linux distro), *Fire.Onion* (Android browser). Both got stuck as well while bootstrapping. TAILS with no intervention is able to connect after a long long while, just like my Relay. Fire.Onion just like the Tor Browser are unable to connect unless I abort and reconnect several times. Back to my Relay... When it finally connects: *[notice]* Bootstrapped 90%: Establishing a Tor circuit *[notice]* Tor has successfully opened a circuit. Looks like client functionality is working. *[notice]* Bootstrapped 100%: Done *[notice]* Now checking whether ORPort XXX.XXX.XXX.XXX:9001 and DirPort XXX.XXX.XXX.XXX:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) *[notice]* Self-testing indicates your DirPort is reachable from the outside. Excellent. *[notice]* Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. *[notice]* Performing bandwidth self-test...done. So I Waited a couple of hours and check in Atlas and Globe again. No luck. In the log I also get: *[notice]* Heartbeat: It seems like we are not in the cached consensus. The DIR and ONION ports are open as showed by the log, I also manually checked them using port scanners. I used other people's networks, the Tor Browser and TAILS to connect to my XXX.XXX.XXX.XXX:9030 port. In every case I got the DirPortFrontPage (html) served by Tor. As indicated by the log I have client connectivity and the Relay seems to be in order but in reality the Relay is dead. It is also worth mentioning that after a successful connection the openSSL errors no longer appear in the Relay's log. Maybe Tor is skipping those (previously faulty) servers. I can only guess. A similar thing happen with the Tor Browser, if I open it frequently, it connects fast (after a successful connection), but if is not used in days, when I launch it, it gets stuck while bootstrapping. Since TAILS is a “live” distro I can't reproduce this behavior. My Relay, the Tor Browser and Fire.Onion have a higher possibility to get stuck while bootstrapping at 0, 5, 20%. Once passed the 50~60% it get faster. My assumption is that my ISP is blocking or at least randomly dropping packets to and from well known Tor Authorities (IP blocking). I don't suspect DPI, as client functionality is working. Using bridges was not necessary when trying client functionality. I was able to connect (abort and retry). As reported by Fabian Bustillos as well. Other Observations: Tor Project <https://www.torproject.org/> website, TAILS <https://tails.boum.org/> website and other Tor related pages are visible without tor. Once connected the Tor Browser is able to fetch updates. Instead of ports 9001 and 9030 I also tried 443 (OR) and 80 (DIR). *For the log, I deleted the Data directory in order to reproduce all the errors, this includes; keys, logs and cached* files.

2 1

Suggestion to make Tor usage more disguised
by Raúl Martínez 16 Jan '16

16 Jan '16

Hi, I am writing this message to make a simple suggestion that could help driving more adoption to Tor by making using tor less obvious for a network administrator. This suggestion tries to address the user case of a common Tor usage, in which the user is not being attacked nor mitm, he is just using tor in his work for example. The network admin of the office is not searching actively for Tor users in his network but one day he log-in in the router panel and he sees this: - Current conexions - WORKSTATION-98 38.29.00.2 [torproxy10.teaxxcu.com] Is obvious that is using tor. The network admin was not looking for Tor usage in his network but it saw this without looking for it. Now this worker can be in serious trouble for using Tor. So my suggestion is to set-up a custom hostname an a Tor-explaining html index ONLY in TOR EXIT nodes. They are the only nodes that can get in trouble and its helpful to advertise that they are tor nodes. ENTRY GUARD nodes should not advertise neither in the hostname nor in a HTML-index-page that they are Tor nodes. This way the network admin would only see an IP and a common hostname, that is a normal behaviour for a HTTPS request. So, having said that *I encourage all Entry-Guard owners to unset his hostname and to disable the HTML-index-page*. That could help a lot of Tor users to not draw unwanted attention. Obviously a network-admin can get a list of Tor relays and check if you are connecting to one of them but most of network-admins just take a look at his router info page without further investigation. Thanks for your time. TL;DR: I encourage all Entry-Guard owners to unset his hostname and to disable the HTML-index-page.

5 5

Re: [tor-relays] [tor-dev] How many exits exit from an IP address different than their OR address? (10.7%)
by grarpamp 14 Jan '16

14 Jan '16

On Wed, Jan 13, 2016 at 10:05 PM, Virgil Griffith <i(a)virgil.gr> wrote: > In our quantifications of relay diversity, knowing the IP addresses that > traffic exits from is important. Ways to have this information correctly > reported would be very helpful. Which is exactly why free to connect back through them and make your quanta and know for yourself or for some research statisticals. But it is the apparent disappreciation for and implied calls to remove them or to publish consensusify their would be formerly stealthy feature use that is a problem from this view. Users use them to access things around censorship, there is no higher purpose of Tor.

1 0

avoid exclusion from FallBack Dir list: do not start during minute 49
by starlight.2016q1＠binnacle.cx 14 Jan '16

14 Jan '16

See comment 6 in Bug #18050: Relay submitted a descriptor with 0 DirPort due to a self-test race condition https://trac.torproject.org/projects/tor/ticket/18050

1 0

probable FallbackDir relay determination bug
by starlight.2016q1＠binnacle.cx 12 Jan '16

12 Jan '16

Dug into the situation Aeris reported where his kitten1 relay was nixed off the fallback directory list due to a single consensus where the dir-port was published as zero. Quickly found three additional very fast very stable relays where the same thing happened: BF0FB582E37F738CD33C3651125F2772705BB8E8 12-28:17 quadhead C43FA6474A9F071E9120DF63ED6EB8FDBA105234 12-25:03 ArachnideFR5 5665A3904C89E22E971305EE8C1997BCA4123C69 11-15:18 GermanCraft In each case the V2Dir flag and DirPort are removed for a single consensus interval and then restored on the next consensus. Appears that a daemon restart is the trigger. Version update not required. Several possible causes, but the one that comes to mind is the daemon could be briefly pushing a descriptor with V2Dir inactive while completing the reacahability test for that port. This deserves to be researched further and mitigated. A possible solution is to have the script tolerate a single consensus with V2Dir removed and a reset uptime. Alternately the daemon could not push a non-V2Dir descriptor during restart and wait for the reacahability determination. I don't know enough about it to be sure the problem isn't something else. At 19:20 1/12/2016 +0100, Aeris wrote: >> Are you *absolutely* certain that the config >> was not fiddled with at the time of this event? > >After grepping some logs, seems 13/12 was the day >of a Tor upgrade: > >2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 0.2.7.6-1~d80.jessie+1 >2015-12-13 10:48:39 configure tor:amd64 0.2.7.6-1~d80.jessie+1 > >Timing is good compare to the 10:48:46 of the consensus ! > >But I don't remember a config change after that, >perhaps only on /usr/share/tor/tor-service-defaults-torrc >or on a default config param change ? > >And perhaps the Tor reboot cause the DirPort to >be temporarily disabled (seems not human, only >2s duration) ? > >Regards, >-- >Aeris

1 1

Traffic on a small Middle Relay, Advertised Bandwidth 1 MB/s
by pa011 12 Jan '16

12 Jan '16

Since about 3 months i am running a small middle relay with Advertised Bandwidth of 1 MB/s. The ISP cuts the line every night as its common on most German private DSL. The relay therefore doesn't get a stable-flag :-( What is the amount of traffic i could/should possibly generate? Is a utilization between 10 and 20 percent not too small, with 15% RAM, 0-20% CPU used only? Could i do any better? Rgds Paul

1 0

Re: [tor-relays] [tor-dev] How many exits exit from an IP address different than their OR address? (10.7%)
by grarpamp 12 Jan '16

12 Jan '16

On Tue, Jan 12, 2016 at 12:44 AM, Jesse V <kernelcorn(a)riseup.net> wrote: > This is quite interesting, thanks for the report. I'm not sure why it > would be advantageous to set up a server or network this way, but I > guess they have their reasons. 1) They may or may not be aware of their routing, or the routing applied to them. 2) Having this feature in the network doesn't break anything, except for maybe check.torproject.org, and a handful of clearnet sites that attempt and often fail to redirect you to their onion, no big deal, hit the new circuit button and try again. 3) Having this feature in the network greatly enhances Tor user's ability to select an exit and get around silly Tor blocks that rely on various consensus, RBL, DNS, whatever lists. Whether it's censorship of the source or destination, it's still censorship. And getting around censorship is one key features and critical use cases of Tor. There is no specification that says exits must exit from their OR IP, or any other IP. I seriously don't know why people continue to get their panties in a bunch over this. Please stop. Nice stats though. cc tt tr because relavance

1 0

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors
by starlight.2015q3＠binnacle.cx 12 Jan '16

12 Jan '16

At 14:24 1/12/2016 +1100, you wrote: >I've reviewed this patch and it looks good. >I updated it for the latest version of the script in the tor git repository, as it was based on an old version. great, thanks! >I've also logged the more general issue with OnionOO and date ranges as #18036. ><https://trac.torproject.org/projects/tor/ticket/18036>https://trac.torproject.org/projects/tor/ticket/18036 I looked at it more closely and I think that OnionOO does not support time-ranges in the retrieved data --one seems to always get everything. Posted a follow-up to the original forum message about this shortly after the original.

1 0

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors
by starlight.2015q3＠binnacle.cx 12 Jan '16

12 Jan '16

Found a serious bug in the updateFallbackDirs.py script used to generate the fallback relay candidate list. The OnionOO retrieval used to pull flag history returns the entire history of each relay rather than the 120 days requested. This results in 145 relays left off the list as too-old history is averaged into the percentages. While this bug appears to be in either OnionOO or in the constructed request URL (not sure which), I opted to add a maximum history age to the script. The result is 558 relays instead of the original 413. (My relay Binnacle now easily makes the cut with guard flag at 97.4 percent.) In addition several data validation bugs were discovered empirically and corrected. Changes: * support maximum history age in _avg_generic_history() * create and apply MAX_AGE_DAYS=120 in calls to _avg_generic_history() * fix division-by-zero trap in _avg_generic_history() * skip missing (i.e. null/None) intervals in _avg_generic_history() * Python timedelta.total_seconds() function not available in 2.6; replace with equivalent expression * set DEBUG logging level to make relay exclusion reasons visible * move CUTOFF_GUARD test to end in order to expose more exclusion reasons Attached to this message are 1) revised script 2) script patch Posted to PasteBin (one month expire): 3) fallback_dirs.inc as-of 2016/01/11 http://pastebin.com/8cxKCEP6 4) debug output showing causes of relay exclusions http://pastebin.com/raw/3SBpgECm

2 3

How to update tor on my raspberry
by Volker Mink 10 Jan '16

10 Jan '16

Hey there. My exit is still running on tor 0.2.4.27. How can i update it to 0.2.7.6 ? Apt-get offers no package with apt-get update and upgrade. Any hints? Best, Volker

6 6

Is Tor being blocked by ISP? (Mexico)
by Fabian Bustillos Vega 09 Jan '16

09 Jan '16

Been running a node (relay non-exit) for about 5 years. Since the new year, i noticed that my node went down, and that it did not appear on the usual places (http://torstatus.blutmagie.de/router_detail.php?FP=78382b769d5d3baa41e89e5d… and https://atlas.torproject.org/#details/78382B769D5D3BAA41E89E5D9D7FF88E1A96A…) with the last seen timestamp of 2015-12-31 20:00:00. I run my node on a dedicated server under my physical control. I checked the Tor process and in the system it was running, with the logs showing: [warn] connection_edge_process_relay_cell (at origin) failed. and [notice] Heartbeat: It seems like we are not in the cached consensus. I confirmed and double checked all my settings and restarted my Tor node, but still noticed that it was not appearing as running on globe https://globe.torproject.org/#/relay/78382B769D5D3BAA41E89E5D9D7FF88E1A96A6… or atlas https://atlas.torproject.org/#details/78382B769D5D3BAA41E89E5D9D7FF88E1A96A… after almost 6 hours. I noticed on the logs i was getting "[notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes." after restarting the node. I tried to open Tor Browser on my personal use computer, and it stalls in "connecting to a relay directory" with "Connecting to a relay directory failed (no route to host - 86.59.21.38:443)". I was however able to connect with Orbot on my smartphone after several retries. That's when i tried to ping and do a trecepath to Tor directory authorities https://atlas.torproject.org/#search/flag:authority Of the ten Tor directory authorities i was not able to ping and tracepath any of them using my ISP Telefonos del Noroeste (telnor). But i was able to ping and tracepath all of the directory authorities using Riseup's Vpn servie https://black.riseup.net/ . I even tried to traceroute directly from within the ISP provided Internet Router and was still not able to get thru to any Tor directory authority or even a Tor node. traceroute to dannenberg directory authority with Telnor ISP: traceroute to 193.23.244.244 (193.23.244.244), 30 hops max, 60 byte packets 1 192.168.254.254 (192.168.254.254) 1.500 ms 1.650 ms 2.120 ms 2 dsl-servicio-l200.uninet.net.mx (200.38.193.226) 10.721 ms 10.758 ms 10.702 ms 3 * * * 4 * * * -snip- 30 * * * traceroute to dannenberg directory authority with Riseup Vpn: traceroute to 193.23.244.244 (193.23.244.244), 30 hops max, 60 byte packets 1 10.42.0.1 (10.42.0.1) 42.364 ms 42.342 ms 42.339 ms 2 wren.riseup.net (198.252.153.1) 43.103 ms 43.103 ms 43.101 ms -snip- 22 dannenberg.torauth.de (193.23.244.244) 205.293 ms 205.783 ms 204.446 ms Similar when i tracepath to a random Tor node in france (http://torstatus.blutmagie.de/router_detail.php?FP=7407277411041dc7bee802bf…) With Telnor ISP: tracepath 149.202.193.100 1?: [LOCALHOST] pmtu 1500 1: 192.168.254.254 1.500ms 1: 192.168.254.254 1.419ms 2: no reply 3: no reply 4: no reply 5: no reply 6: no reply C With Riseup Vpn: tracepath 149.202.193.100 1?: [LOCALHOST] pmtu 1500 1: 10.42.0.1 43.093ms 1: 10.42.0.1 39.373ms 2: wren.riseup.net 44.108ms 3: gi0-0-0-5.agr13.sea02.atlas.cogentco.com 42.399ms 4: multi-use.cogentco.com 44.246ms 5: be2288.ccr21.sea02.atlas.cogentco.com 44.367ms 6: level3.sea02.atlas.cogentco.com 41.783ms asymm 7 7: no reply 8: no reply 9: nwk-1-a9.nj.us 133.351ms asymm 15 10: ldn-1-a9.uk.eu 198.174ms asymm 17 11: rbx-g1-a9.fr.eu 202.478ms asymm 17 12: fra-1-a9.de.eu 206.248ms asymm 18 13: sbg-g1-a9.fr.eu 213.218ms asymm 20 14: sbg-4b-a9.fr.eu 215.017ms asymm 21 15: ns3015177.ip-149-202-193.eu 213.182ms reached Resume: pmtu 1500 hops 15 back 21 Before the new year, there used to be around 5 to 8 Tor nodes located in Mexico, right now, only one appears as online: http://torstatus.blutmagie.de/router_detail.php?FP=92dd0214bc72cb52777e2015… that i am not able to ping or traceroute to. I have a dynamic IP, so i rebooted the ISP provided router and tried with several IP's that where assigned by my ISP and all provided the same results. I plan on doing more testing and calling my ISP and asking directly about the IP's i am not able to reach and specifically if they block or plan on blocking Tor. UPDATE: Tech support chat with ISP - Jan 02 2016: http://pastebin.com/xZuWqAkX They confirmed that i can not access the IP's but don't have any info about why i am not able to access. They "escalated" the issue... Tech support chat with ISP - Jan 03 2016: http://pastebin.com/6MA2gj9e They said: Telnor connections to the rest of the world is thru the U.S. from Telnor no blocking is made to the rest of the world. I'm not seeing any Tor nodes with telnor/telmex/infinitum at http://torstatus.blutmagie.de/index.php only Axtel and Megared. I am sometimes able to connect to "longclaw" longclaw.riseup.net (199.254.238.53) but not always. Sometimes i get "Connecting to a relay directory failed (no route to host - directory_ip:port)" when using the Tor Browser, but if i try several times i am able to use the Tor browser. I would really like to keep running my Tor node, and i am willing to change ISP's, but i am still hoping that it's something on my end, but i am not seeing any more relays with Telmex/Telnor/Infinitum as ISP. Is there anyway to confirm that it's my ISP? any other reports from Mexico about similar issues?. In the meantime, i already donated $100 while my Tor node is down. (no t-shirt yet though :( ) Tor logs here: http://pastebin.com/4XQaQyLd torrc contents: ContactInfo fabian dot bustillos at riseup dot net ControlPort 9051 DirPort 9030 ORPort 9001 ExitPolicy reject *:* HashedControlPassword ------------------------------------------------ Nickname fbnaiaTorRelay SocksListenAddress 127.0.0.1 DisableDebuggerAttachment 0

1 0

Why is Tor trying to check the wrong ORPort/DirPort addresses?
by David Tomic 09 Jan '16

09 Jan '16

Hello everyone. Long story short I have just begun experimenting with running multiple Tor instances on a couple of my servers, namely to see if it actually makes an appreciable difference to my overall throughput. I have multiple public IPs on my servers, and I would like each Tor instance to use its own dedicated address so I have configured the appropriate ip:port addresses in my second torrc file. When I start up the second instance, everything gets bound to the correct ip:port combinations (as specified in my torrc file), and I have no problems getting Tor to bootstrap and successfully open a circuit. The problem appears when Tor tries to verify that my ORPort/DirPort are reachable, because for some reason it's trying to check the wrong IP address? EG - Here are the relevant ports from my torrc file: SocksPort 9053 ControlPort 9063 Log notice file /var/log/tor/notices3.log RunAsDaemon 1 DataDirectory /var/lib/tor/3 ORPort 50.7.178.99:445 DirPort 50.7.178.99:83 When I start Tor, everything matches the above: Jan 08 11:56:23.178 [notice] Opening Socks listener on 127.0.0.1:9053 Jan 08 11:56:23.179 [notice] Opening Control listener on 127.0.0.1:9063 Jan 08 11:56:23.179 [notice] Opening OR listener on 50.7.178.99:445 Jan 08 11:56:23.179 [notice] Opening Directory listener on 50.7.178.99:83 Tor successfully bootstraps and establishes a circuit: Jan 08 11:57:13.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Jan 08 11:57:13.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jan 08 11:57:13.000 [notice] Bootstrapped 100%: Done BUT THEN ... Jan 08 11:57:13.000 [notice] Now checking whether ORPort 50.7.178.102:444 and DirPort 50.7.178.102:83 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Notice that it's still checking the correct port from the torrc file, but not the correct ip address. I've tried different IP:port combinations, and each time it's the same result. Right port, wrong IP. I've tried now on two different servers, and had exactly the same results each time. Machines are running Debian 8.0 with Tor 0.2.7.6. I have tried installing from the Debian repo, as well as building from the latest source. No difference. What's causing this to go wrong? Is there something incredibly simple which I'm simply just not doing properly, or is there possibly more going on here than first meets the eye?

5 10

Debugging my small relay
by Markus Hitter 08 Jan '16

08 Jan '16

Hello all, for somewhat over a year now I run a Tor relay on my router. The router in turn is running OpenWRT. It's this one: https://globe.torproject.org/#/relay/A52C51551F3BD6A68E778720E02B53303F014E… https://atlas.torproject.org/#details/A52C51551F3BD6A68E778720E02B53303F014… Not much, but let it be one of my small shares for improving humanity :-) A few days ago I upgraded OpenWRT from 14.07 to 15.05, the latest release. Reinstalled the package 'tor', kept the old config file and the server started apparently smoothly. Previous Tor version was 0.2.4.22, now it's 0.2.5.12. I'm aware that these aren't exactly the latest, but that's what OpenWRT's package manager offers. As you can see in the link above, the relay is no longer recognized as 'running'. They don't recognize the new Tor version, don't recognize the restart. To what I know, /var/log/tor/notices.log looks fine, a few excerpts: Jan 02 14:34:36.000 [notice] Tor 0.2.5.12 (git-99d0579ff5e0349f) opening new log file. [... clock synchrionisation works :-) ...] Jan 04 17:35:42.000 [warn] Your system clock just jumped 183652 seconds forward; assuming established circuits no longer work. [...] Jan 04 17:38:09.000 [notice] Now checking whether ORPort x.x.x.x:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jan 04 17:38:15.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. [...] Jan 06 11:35:42.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 0 circuits open. I've sent 68.73 MB and received 85.15 MB. Jan 06 11:35:42.000 [notice] Average packaged cell fullness: 76.757% Jan 06 11:35:42.000 [notice] TLS write overhead: 9% Jan 06 11:35:42.000 [notice] Circuit handshake stats since last time: 9/9 TAP, 0/0 NTor. How could I find out about what's going wrong? Thanks, Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/

4 7