- tor-relays - lists.torproject.org

freebsd relay doesnt receive any traffic (after 1 month)
by dlugasny＠protonmail.com 25 Oct '18

25 Oct '18

Hi, few weeks ago ( more than 4) I have installed Freebsd with Tor relay service. System is connected to Tor network since more than one month but I see only 1-2 connections per day. I had Tor relay service on my Debian server for many years and I havent got any problems. With Freebsd its pain, nothing is working as expected. Any how I would like to build more BSD instances in few different countries, but first I need to know why its not working. Does any one could help me to do some troubleshooting ? Maybe some of the parameters in the torrc are blocking traffic ? My torrc without Hashedpassword, Nickname: ########################### SocksPort 0 Log notice file /var/log/tor/notices.log ControlPort 9051 ORPort 9001 RelayBandwidthRate 400 KBytes # Throttle traffic to 100KB/s (800Kbps) RelayBandwidthBurst 600 KBytes # But allow bursts up to 200KB (1600Kb) ContactInfo Dlugas-ny <dlugasny AT protonmail dot com> DirPort 9030 # what port to advertise for directory connections ExitPolicy reject *:* # no exits allowed PublishServerDescriptor 0 CellStatistics 1 ExtraInfoStatistics 1 ConnDirectionStatistics 1 EntryStatistics 1 LogMessageDomains 1 AvoidDiskWrites 1 WarnPlaintextPorts HeartbeatPeriod 1hours ServerTransportPlugin obfs2,obfs3 exec /usr/local/bin/obfsproxy managed ServerTransportPlugin obfs4 exec /usr/local/bin/obfsproxy managed ExtORPort auto ############################ Thanks in advance for any support Cheers Dlugasny Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Tor bridge on Windows 10 going down for a reason I cannot detect?
by Keifer Bly 25 Oct '18

25 Oct '18

Hello all, for some reason my tor bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032… is randomly removed from the network. Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours. This is very strange as I had not closed the tor software and my internet had not disconnected at all. Below is the tor log file, it is tor 0.3.4.8 on Windows 10, any thoughts would be great. Thanks. Oct 19 23:33:16.910 [notice] Tor 0.3.4.8 (git-da95b91355248ad8) running on Windows 8 with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A. Oct 19 23:33:16.910 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 19 23:33:16.957 [notice] Read configuration file "C:\Users\keife\AppData\Roaming\tor\torrc.txt". Oct 19 23:33:16.972 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted? Oct 19 23:33:16.972 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted? Oct 19 23:33:16.972 [notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand. Oct 19 23:33:16.972 [notice] Scheduler type KISTLite has been enabled. Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:33:16.972 [notice] Opening Extended OR listener on 127.0.0.1:0 Oct 19 23:33:16.972 [notice] Extended OR listener listening on port 56515. Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv4 file C:\Users\keife\AppData\Roaming\tor\geoip. Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv6 file C:\Users\keife\AppData\Roaming\tor\geoip6. Oct 19 23:33:57.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Oct 19 23:33:58.000 [notice] Your Tor server's identity key fingerprint is 'torland 8C6C18F8D95918F9DC90A09827DAD285064F8872' Oct 19 23:33:58.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 148BD64BED9F2C27637D986DE032ECF14E5B9E9A' Oct 19 23:33:58.000 [notice] Bootstrapped 0%: Starting Oct 19 23:35:03.000 [notice] Starting with guard context "default" Oct 19 23:35:03.000 [notice] Bootstrapped 5%: Connecting to directory server Oct 19 23:35:05.000 [notice] Bootstrapped 10%: Finishing handshake with directory server Oct 19 23:35:05.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002' Oct 19 23:35:05.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus Oct 19 23:35:06.000 [notice] Bootstrapped 50%: Loading relay descriptors Oct 19 23:35:06.000 [notice] Guessed our IP address as 174.87.240.59 (source: 136.243.176.148). Oct 19 23:35:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network Oct 19 23:35:15.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Oct 19 23:35:18.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Oct 19 23:35:18.000 [notice] Bootstrapped 100%: Done Oct 19 23:35:18.000 [notice] Now checking whether ORPort 174.87.240.59:9002 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Oct 19 23:35:21.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 19 23:36:44.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes. Oct 19 23:36:45.000 [notice] Performing bandwidth self-test...done. Oct 20 05:35:00.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0 circuits open. I've sent 3.08 MB and received 14.49 MB. Oct 20 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 11:35:00.000 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 1 circuits open. I've sent 4.38 MB and received 19.35 MB. Oct 20 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 17:35:00.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 5.74 MB and received 23.84 MB. Oct 20 17:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 20:49:17.000 [notice] Channel padding timeout scheduled 180307ms in the past. Oct 20 23:35:00.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 1 circuits open. I've sent 7.19 MB and received 28.20 MB. Oct 20 23:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 05:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 5:59 hours, with 0 circuits open. I've sent 8.77 MB and received 34.02 MB. Oct 21 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 11:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 11:59 hours, with 0 circuits open. I've sent 10.16 MB and received 38.10 MB. Oct 21 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1... Oct 23 00:47:29.000 [notice] #0 created at 2018-10-21 17:34:12. open, General-purpose client. Not marked for close. Package window: 1000. usable for new conns. Dirty since 2018-10-21 17:34:13 (112396 seconds vs 600-second cutoff). Oct 23 00:47:29.000 [notice] It has been 112368 seconds since I last called circuit_expire_old_circuits_clientside(). Oct 23 00:47:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work. Oct 23 00:47:31.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent usable consensus. Oct 23 00:48:29.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:48:29.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1... Oct 23 00:48:29.000 [notice] #0 created at 2018-10-21 17:34:12. open, General-purpose client. Marked for close. Package window: 1000. Not usable for new conns. Dirty since 2018-10-21 17:24:13 (113056 seconds vs 600-second cutoff). Oct 23 00:48:29.000 [notice] It has been 59 seconds since I last called circuit_expire_old_circuits_clientside(). Oct 23 00:48:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 23 00:48:32.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus. Oct 23 00:48:35.000 [notice] We now have enough directory information to build circuits. Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

5 9

Strength in numbers (of $$)
by I 24 Oct '18

24 Oct '18

4 3

Loss of Guard Flag
by Harkirat Virk 22 Oct '18

22 Oct '18

Hi, I am running an Tor Node nickname 3sKtjMnoiZAIGz07 from ip 59.179.28.221. I was given guard flag briefly on 20th Oct and flag removed on 22 Oct. My advertised bandwidth also dropped from 2.29 MiB/s to 1.79 MiB/s unceremoniously. The consensus weight reduced from 992 to 810. I have checked but did not find any discontinuity on the network end or any connections dropped. Will is be possible to confirm as the the exact reasons for loss of guard and drop in both advertised bandwidth and consensus weight. Regards, Loopback team

2 1

Relay country mismatch
by nusenu 21 Oct '18

21 Oct '18

Hi Mariel The Tor Project uses Maxmind's data to map IP addresses to countries, your IP address block might get updated in Maxmind's file in the future and after onionoo (the data source behind Relay Search) updates its Maxmind file it might appear. This might take a while. kind regards, nusenu btw: please avoid sending the same email to multiple lists, tor-relays is the correct list for this. Mariel: > Hello, > > I am running a relay 3B03DE96FEFB384972D1D31A105DD70E6BDBF079 which has IP 5.188.238.58 and is hosted at G-Core labs Brazil datacenter, but Tor Metrics engine shows the IP country as Luxembourg - https://metrics.torproject.org/rs.html#details/3B03DE96FEFB384972D1D31A105D… > > The valid WHOIS data is: > % Abuse contact for '5.188.238.0 - 5.188.239.255' is 'abuse(a)gcore.lu' > > inetnum: 5.188.238.0 - 5.188.239.255 > netname: LU-GCORELABS-20120809 > country: BR > org: ORG-WIG6-RIPE > admin-c: LA5122-RIPE > tech-c: LA5122-RIPE > status: ALLOCATED PA > geoloc: -23.468962 -46.843583 > mnt-by: RIPE-NCC-HM-MNT > mnt-by: GCL1-MNT > mnt-lower: GCL1-MNT > created: 2018-03-13T10:06:22Z > last-modified: 2018-08-08T10:44:27Z > source: RIPE # Filtered > > Thus, since country is BR it should have be shown as Brazil. Can you fix this data somehow? Thanks in advance. > > > _______________________________________________ > metrics-team mailing list > metrics-team(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/metrics-team > -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

exit operators: overall DNS failure rate above 5% - please check your DNS
by nusenu 20 Oct '18

20 Oct '18

Dear Exit relay operators, (you are getting this email because you are a subscriber of the tor-relays mailing list or because you are among the top 10 affected parties - addressed via BCC to protect the address) first of all thanks for running exit relays! One of the crucial service that you provide in addition to forwarding TCP streams is DNS resolution for tor clients. Exits relays which fail to resolve hostnames are barely useful for tor clients. We noticed that lately the failure rates did increase again and would like to urge you to visit Arthur's "Tor Exit DNS Timeouts" page that shows you the DNS error rate for exit relays: https://arthuredelstein.net/exits/ (the page is usually updated once a day) Please consider checking your DNS if your exit relay consistently shows a non zero timeout rate - and make sure you run an up to date tor version. If you are an exit operator but have no (or no working) ContactInfo, please consider updating that field in your torrc so we can reach you if something is wrong with your relay. kind regards nusenu -- https://twitter.com/nusenu_

5 5

Why is there a difference in the amount of data tor has sent and received?
by Keifer Bly 17 Oct '18

17 Oct '18

Hello list, So when running my OBFS4 bridge I noticed something, tor recently popped up with a message saying “I’ve sent 30mb and received 104mb.” Why is there such a big difference in the amount of data my bridge has received and sent? Info – tor 0.3.4.8 running on Windows 10 (Although tor seems to think it’s running on Windows 8 for some reason)? Thanks. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Memory leak in 0.3.4.8?
by r1610091651 17 Oct '18

17 Oct '18

Hi I've noticed following after upgrading to latest stable version (0.3.4.8): Memory usage [image: image.png] Connection count [image: image.png] Cpu usage [image: image.png] You'll notice the upgrade happened around Saturday midnight. Known issue? Any work-around? Thanks Sebastian

5 4

Tor relays Workshop in FOSSCOMM
by George Kadianakis 17 Oct '18

17 Oct '18

Greetings list, a few days ago, Elias Papavasileiou did a "Setup your own Tor relay" workshop in the Greek open source conference FOSSCOMM. I attended the workshop and helped out a bit. During the workshop, a presentation was given describing how to setup a relay, and then we moved to hands-on, where we helped 3 groups of 2 people each setup a Tor bridge in their laptop. Even tho a laptop is definitely not the right platform for this, the idea was that if those people learned how to setup a Tor relay/bridge they could afterwards set it up themselves on proper hardware. A few takeaways: - Setting up a Tor relay is not easy even if it's just "apt-get tor, edit torrc, reload tor". There are various things that can go wrong in the between, and basically all groups asked for assistance even tho they all seemed experienced with Linux system administration. - Example of fail: One group put a wrong line in their torrc (they tried to launch with a low-port ORPort of 443 even tho they were not root), then had trouble debugging what's going on, then wiped logs and ran Tor manually as root. Tor overwrote the log file, permission issues occured, and Tor could not start again. We had to manually figure this out and remove the bad log file for Tor to work again. That took a while. - Example of fail: People kind of gave up reading all the comments in the Debian default torrc and asked us for assistance because they did not know what they had to do to make it work. aka what was necessary and what was optional. - After about 45 mins all three groups managed to successfuly run a bridge. I'm just mentioning these things here in case someone can relate and improve the situation. There might be a few things we can do (aka improve the default Debian torrc), or even provide images/docker/vagrant for relays. But I'm not good with these things so I can't really suggest things. Cheers!

2 1

"ORPort auto" versus "ORPort 9001" for a bridge
by Toralf Förster 17 Oct '18

17 Oct '18

I do wonder if the advice [1] is ok or wrong. [1] https://tor.stackexchange.com/questions/6370/how-to-run-an-obfs4-bridge -- Toralf PGP C4EACDDE 0076E94E

2 3