- tor-relays - lists.torproject.org

Build problem
by dns1983＠riseup.net 25 Jun '19

25 Jun '19

Hello, I'm trying to build tor for from source on a x86 Debian stretch machine. I first installed all dependencies, but when I launch the "./configure" command I see the following error: configure: WARNING: Unable to find liblzma. configure: WARNING: Unable to find libzstd I installed, among the others liblzma-dev, lzma, libzstd-dev and zstd. I'm working through ssh. What I'm doing wrong? Could It be caused by a wrong environment variables settings? Cheers Gigi

2 2

obfs4proxy installation from deb.torproject.org says Release file expired
by s7r 25 Jun '19

25 Jun '19

Hello, Trying to spin some new obfs4bridges. I am using: deb.torproject.org/torproject.org obfs4proxy main in /etc/apt/sources.list -- I hope this is correct. I get this: E: Release file for https://deb.torproject.org/torproject.org/dists/obfs4proxy/InRelease is expired (invalid since 1d 15h 7min 11s). Updates for this repository will not be applied. Just recently saw Yawning's release notification, is it somehow related? Thanks.

2 1

fresh assault on Tor network
by starlight.2018q2＠binnacle.cx 25 Jun '19

25 Jun '19

https://metrics.torproject.org/userstats-relay-country.html?start=2017-06-2…

3 3

Become a Fallback Directory Mirror
by gus 25 Jun '19

25 Jun '19

Dear Relay Operators, Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint. If your relay is on the current list, you don't need to do anything. If you're asking: Q: What's a fallback directory mirror? Fallback directory mirrors help Tor clients connect to the network. For more details, see [1]. Q: Is my relay on the current list? Search [2] and [3] for your relay fingerprint or IP address and port. [2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks. Q: What do I need to do if my relay is on the list? Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change. Q: Can my relay be on the list next time? We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay. Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2]. Q: Why didn't my relay get on the list last time? We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time. It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder. cheers, gus [1] https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2] https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3] https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4] https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_…

13 19

Re: [tor-relays] Become a Fallback Directory Mirror
by teor 24 Jun '19

24 Jun '19

Hi, > On 24 Jun 2019, at 02:49, tschador(a)posteo.de wrote: > > On 2019-06-23 14:32, teor wrote: > >> But your relay needs a DirPort to be a fallback directory mirror. >> Here are some instructions for different platforms: >> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecifi… > > This should be clarified in the Tor manual [1] too! > > "Tor will contact the authority at ipv4address to download directory > documents. The provided port value is a dirport; clients ignore this in > favor of the specified "orport=" value. If an IPv6 ORPort is supplied, > Tor will also download directory documents at the IPv6 ORPort." > > Am I right that for fallback directory mirrors DirPort is needed but > ignored by clients? It is needed to make sure that the relay serves directory documents. We run a script that uses the DirPort to check the download speed. > Possibly this explains why I lost the fallback > directory flag since I have removed the DirPort in torrc … Fallbacks need the same ports, IP addresses, and keys for 2 years. That includes the DirPort. It's not possible to configure a fallback without a dirport: FallbackDir ipv4address:port orport=port id=fingerprint [weight=num] [ipv6=[ipv6address]:orport] (The first port is a dirport, and both dirport and orport are required.) I have updated the template: https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectory… And opened a ticket for the man page: https://trac.torproject.org/projects/tor/ticket/30955 T

1 0

Tor memory leak (0.3.5.7)?
by Roman Mamedov 23 Jun '19

23 Jun '19

Hello, As sometimes happens, I notice my nodes getting into swap heavily. This time: ------------ KiB Mem: 1010576 total, 897388 used, 113188 free, 5144 buffers KiB Swap: 1048572 total, 123592 used, 924980 free. 61732 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4740 debian-+ 25 5 565448 259032 15204 R 63.2 25.6 1621:47 tor 4765 debian-+ 25 5 491636 200812 13136 S 32.9 19.9 678:36.65 tor total used free shared buffers cached Mem: 1010576 870392 140184 4 1144 64604 -/+ buffers/cache: 804644 205932 Swap: 1048572 123592 924980 ------------ After killing PID 4740 and starting that instance again (now PID 25456): ------------ KiB Mem: 1010576 total, 691264 used, 319312 free, 4336 buffers KiB Swap: 1048572 total, 58624 used, 989948 free. 209692 cached Mem Unknown command - try 'h' for help PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4765 debian-+ 25 5 491636 195900 8584 R 38.3 19.4 678:56.29 tor 25456 debian-+ 20 0 441092 240824 140452 S 29.9 23.8 0:28.48 tor total used free shared buffers cached Mem: 1010576 663816 346760 12 4344 209692 -/+ buffers/cache: 449780 560796 Swap: 1048572 58624 989948 ------------ How come killing a Tor instance which was shown to be using 259 MB of RAM, has freed up 355 MB, even counting the new copy of Tor which was started in its place and is already using 240 MB? The math only adds up to 19 MB delta, not 355. As this memory usage doesn't seem to be attributed to Tor, it reminds me of that major memory leak which was fixed some time ago, so maybe it was not fixed entirely? -- With respect, Roman

1 0

Re: [tor-relays] tor update question
by Olaf Grimm 21 Jun '19

21 Jun '19

On Website: "update to latest upstream release (bz#1679732) How to install sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-EPEL-2019-f8311ec8a2" Not working! The command there is "dnf". A replacement with "yum" get the following error on my system: "[root@75f449 ~]# yum upgrade --enablerepo=updates-testing --advisory=FEDORA-EPEL-2019-f8311ec8a2 Geladene Plugins: fastestmirror Error getting repository data for updates-testing, repository not found [root@75f449 ~]# " Any other solution available? Olaf Am 20.06.19 um 21:31 schrieb nusenu: >> I am running Centos7 (CentOS Linux release 7.6.1810 (Core)) and Tor >> v. 0.3.5.7. Now I see in nyx that is is unrecommended, but the epel >> repo doesn't have 0.3.5.8. Should I be adding another repo, or just >> wait, or try to compile my own? > You can get tor 0.3.5.8 on CentOS 7 by enabling the updates-testing repo > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2 > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

tor update question
by torix＠protonmail.com 20 Jun '19

20 Jun '19

Dear List, I am running Centos7 (CentOS Linux release 7.6.1810 (Core)) and Tor v. 0.3.5.7. Now I see in nyx that is is unrecommended, but the epel repo doesn't have 0.3.5.8. Should I be adding another repo, or just wait, or try to compile my own? TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Wrong country and AS number/ name
by ILikeTor 20 Jun '19

20 Jun '19

Hello everybody, I have set up a relay about 3 days ago now. I am hosting my relay at a German hosting provider called "contabo", but the relay search of Tor Metrics tells me that the relay is based in the United States and that the AS number and name are unknown. Does someone know what I could do to fix this? Link: https://metrics.torproject.org/rs.html#details/53E89AD9B9320749F04DCA757F1C… Thanks in advance :) ILikeTor (or so - I definitely need a better nickname :/)

3 2

Tor Debian repo update
by Peter Ludikovsky 20 Jun '19

20 Jun '19

Hello, Does the official Tor Project repo provide upgrades to the new 0.4.0.5 stable for anyone? I can see the new packages in pool/main/t/tor/, but the package index in dists/stretch/main/binary-amd64/Packages still points to 0.3.5.8. Regards, /peter

3 2

Moving Exit Node
by Yggdrasil Admin 20 Jun '19

20 Jun '19

Hi at all. Yesterday i was kicked by my hosting provider urdn (https://urdn.com.ua) kicked me because "someone we can't name here, wasn't happy" about what i did on a non urdn server. That's why they nullrouted my ipv4 and made the Exit Node inaccessible. After a talk with the support over jabber he told my that the server was still accessible over ipv6 so i backuped my identity keys and tried to setup my exit node on another server which wasn't possible because it alway tried to connect to the nullrouted ipv4. My main question is: Can i setup my exit node on another server with another ipv4 or is this impossible? Regards

2 1

Re: [tor-relays] Questions about relays on IPv6
by teor 19 Jun '19

19 Jun '19

Hi, > On 19 Jun 2019, at 05:56, tschador(a)posteo.de wrote: > > I have enabled IPv6 on my Relay [1] and setup a new one [2]. > Both got the additional Flag 'ReachableIPv6' - fine. > > In the 'IPv6 HOWTO' [3] I found: > > "Since clients only use the ORPort (because it's more anonymous2), and > relays only use IPv4, there is no reason to configure an IPv6 DirPort - > if you do, it will never be used." > > Hmm - 'relays only use IPv4' seems to be true. Until now I can see only > incoming connections from the authorities; no other IPv6 and no outgoing > IPv6 connection while on [1] there are over 6800 und on [2] over 4800 > IPv4 connections! > > So I wonder: Does it make sense to setup IPv6 non-exit relays when IPv6 > is not used? Or must I wait patiently - how long? If your relay becomes a Guard, a small number of clients will use its IPv6 ORPort. We want to use IPv6 more in tor, but we have to write the code to do it, and work out if it has any anonymity issues. I updated the wiki page so it is clearer: https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto?action=dif… > [1] 6A7551EEE18F78A9813096E82BF84F740D32B911 (Tormachine) > [2] 9556D34D97C0382E8B9901B036ACAA2F2B453FEC (Tormachine2) > [3] https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto T

1 0

Re: [tor-relays] Questions about relays on IPv6
by Charly Ghislain 19 Jun '19

19 Jun '19

Basically, assuming relays communicate between them over ipv4, guards and exits supporting ipv6 would allow clients with ipv6-only connectivity to join the network, and establish connections to ipv6-aware servers. So I guess it makes sense if you relay ever gets the guard flag. On Wed, Jun 19, 2019 at 10:21 AM <tschador(a)posteo.de> wrote: > > Hello, > > I have enabled IPv6 on my Relay [1] and setup a new one [2]. > Both got the additional Flag 'ReachableIPv6' - fine. > > In the 'IPv6 HOWTO' [3] I found: > > "Since clients only use the ORPort (because it's more anonymous2), and > relays only use IPv4, there is no reason to configure an IPv6 DirPort - > if you do, it will never be used." > > Hmm - 'relays only use IPv4' seems to be true. Until now I can see only > incoming connections from the authorities; no other IPv6 and no outgoing > IPv6 connection while on [1] there are over 6800 und on [2] over 4800 > IPv4 connections! > > So I wonder: Does it make sense to setup IPv6 non-exit relays when IPv6 > is not used? Or must I wait patiently - how long? > > Thanks. > > [1] 6A7551EEE18F78A9813096E82BF84F740D32B911 (Tormachine) > [2] 9556D34D97C0382E8B9901B036ACAA2F2B453FEC (Tormachine2) > [3] https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

exit relay "internal error"
by dns1983＠riseup.net 19 Jun '19

19 Jun '19

Hello, I have an exit relay on a debian remote vm. Yesterday, after I installed the last linux security update, I rebooted It, and than I had a problem with additional IPs, that were no more being assigned. In order to understand if it were a problem caused by the last upgrade I restored a previous backup, that I made on May with tar. I didn't solved the problem restoring the backup, so I opened a ticket with my provider. Now they have fixed this issue, but my tor instance is going in loop. The log says: ... Jun 18 13:33:31.000 [notice] Bootstrapped 0%: Starting Jun 18 13:33:32.000 [notice] Starting with guard context "default" ============================================================ T= 1560854012 INTERNAL ERROR: Raw assertion failed at ../src/lib/ctime/di_ops.c:179: ! old_val/usr/bin/tor(dump_stack_symbols_to_error_fds+0x33)[0x55a17b410943] /usr/bin/tor(tor_raw_assertion_failed_msg_+0x86)[0x55a17b410fd6] /usr/bin/tor(dimap_add_entry+0xa0)[0x55a17b411ba0] /usr/bin/tor(construct_ntor_key_map+0x69)[0x55a17b357969] /usr/bin/tor(server_onion_keys_new+0x4d)[0x55a17b39f4dd] /usr/bin/tor(+0x66e27)[0x55a17b287e27] /usr/bin/tor(threadpool_new+0x18b)[0x55a17b3b3f0b] /usr/bin/tor(cpu_init+0x9d)[0x55a17b28828d] /usr/bin/tor(run_tor_main_loop+0x136)[0x55a17b27a496] /usr/bin/tor(tor_run_main+0x1215)[0x55a17b27b935] /usr/bin/tor(tor_main+0x3a)[0x55a17b278a8a] /usr/bin/tor(main+0x19)[0x55a17b278609] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ffb901ba2e1] /usr/bin/tor(_start+0x2a)[0x55a17b27865a] Jun 18 13:33:33.000 [notice] Tor 0.3.5.8 opening log file. ... What could be the problem? thanks Gigi

2 3

Having trouble getting my relay to be picked up
by Stephen Downward 17 Jun '19

17 Jun '19

Good evening, I am having some trouble running a tor relay node. I have forwarded TCP 9001, and can confirm I can access it from outside of my network. I used the following instructions to set up my node: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntu Here is the relevant snippet from my log file: Jun 15 23:31:00 TorRelay systemd[1]: Starting Anonymizing overlay network for TCP... Jun 15 23:31:01 TorRelay tor[3488]: Jun 15 23:31:01.127 [notice] Tor 0.2.9.16 (git-9ef571339967c1e5) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0j and Zlib 1.2.8. Jun 15 23:31:01 TorRelay tor[3488]: Jun 15 23:31:01.127 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jun 15 23:31:01 TorRelay tor[3488]: Jun 15 23:31:01.127 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jun 15 23:31:01 TorRelay tor[3488]: Jun 15 23:31:01.127 [notice] Read configuration file "/etc/tor/torrc". Jun 15 23:31:01 TorRelay tor[3488]: Jun 15 23:31:01.131 [notice] Based on detected system memory, MaxMemInQueues is set to 1125 MB. You can override this by setting MaxMemInQueues by hand. Jun 15 23:31:01 TorRelay tor[3488]: Configuration was valid Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.288 [notice] Tor 0.2.9.16 (git-9ef571339967c1e5) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0j and Zlib 1.2.8. Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.288 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.288 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.288 [notice] Read configuration file "/etc/tor/torrc". Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.292 [notice] Based on detected system memory, MaxMemInQueues is set to 1125 MB. You can override this by setting MaxMemInQueues by hand. Jun 15 23:31:01 TorRelay tor[3491]: Jun 15 23:31:01.292 [notice] Opening OR listener on 0.0.0.0:9001 Jun 15 23:31:05 TorRelay systemd[1]: Started Anonymizing overlay network for TCP. As you can see, I'm not getting "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.", which would indicate that the relay is working properly. The server does not have any outgoing connections blocked. I am unsure what to do in order to get this to work - some help would be beneficial. Thanks!

2 1

Home Router limits question
by torix＠protonmail.com 16 Jun '19

16 Jun '19

Would tor show something in its log if I were hitting my router's limit? Seeing nothing there or in my router's gui log interface, but not sure what I should expect to see. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 2

Setting Tor Relay to Hibernate After 100Mbits
by Keifer Bly 04 Jun '19

04 Jun '19

Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am attempting to set my relay to hibernate after sending 100 mbits of data per month. Does this torrc configuration look like it would do that? SOCKSPort 0 ORPort 65534 ExitPolicy reject *:* ContactInfo keiferDoTblyAtgmaildOtcom Nickname torworld RelayBandwidthRate 100 MBits RelayBandwidthBurst 100 MBits AccountingMax 100 MBits AccountingStart month 1 00:00 AccountingRule out Thanks all. --Keifer

5 6

Curious up disclosure possible?
by Dr Gerard Bulger 04 Jun '19

04 Jun '19

Conclusion...avoid http, 80 ? https://blog.duszynski.eu/tor-ip-disclosure-through-http-301-cache-poisonin… Gerry Mobile Device > On 3 Jun 2019, at 9:26 pm, Keifer Bly <keifer.bly(a)gmail.com> wrote: > > So I am trying to limit as google cloud has strict pricing plans. Perhaps I should go back to just running a bridge for now. What would the traffic limit for a useful relay be? Thanks. > >> On Mon, Jun 3, 2019 at 10:40 AM Matt Traudt <pastly(a)torproject.org> wrote: >> On 6/3/19 13:20, Keifer Bly wrote: >> > Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am >> > attempting to set my relay to hibernate after sending 100 mbits of data >> > per month. Does this torrc configuration look like it would do that? >> > >> > SOCKSPort 0 >> > >> > ORPort 65534 >> > >> > ExitPolicy reject *:* >> > >> > >> > ContactInfo keiferDoTblyAtgmaildOtcom >> > >> > Nickname torworld >> > >> > RelayBandwidthRate 100 MBits >> > >> > RelayBandwidthBurst 100 MBits >> > >> > AccountingMax 100 MBits >> > >> > AccountingStart month 1 00:00 >> > >> > AccountingRule out >> > >> > Thanks all. >> > >> >> 100 Megabits is 12.5 Megabytes, and approximately ~10 page loads of the >> average web page these days (as unscientifically eye-balled by me). >> >> Further, setting RBR and RBB to 100 Mbits (per second) means you could >> theoretically hit your tiny AccountingMax in the first second of every >> month. >> >> An AccountingMax of 100 Megabits is almost assuredly not what you >> actually want. >> >> I'm wondering if there was some confusion about the difference between >> speed and a simple of bytes. Confusingly, Tor uses the same unit strings >> (like "MBits") for both, but mentally we should be adding "per second" >> for torrc options like RelayBandwidthRate. >> >> 100 Megabits per second is a reasonable RBR setting for a reasonable >> relay. 100 Megabits per month is a useless relay. >> >> Hope that helps. >> >> Matt >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -- > --Keifer > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Auto Upgrading Tor Using Unattended Ugrades
by Keifer Bly 03 Jun '19

03 Jun '19

Hello all, So I am now auto upgrading tor using the method at https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpd… Upon testing, this is what I got. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: [] Checking: firefox-esr ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: google-cloud-sdk ([<Origin component:'main' archive:'cloud-sdk-stretch' origin:'cloud-sdk-stretch' label:'cloud-sdk-stretch' site:'packages.cloud.google.com' isTrusted:True>]) Checking: google-compute-engine ([<Origin component:'main' archive:'google-compute-engine-stretch-stable' origin:'google-compute-engine-stretch-stable' label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com' isTrusted:True>]) Checking: google-compute-engine-oslogin ([<Origin component:'main' archive:'google-compute-engine-stretch-stable' origin:'google-compute-engine-stretch-stable' label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com' isTrusted:True>]) Checking: libavcodec57 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libavfilter6 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libavformat57 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libavresample3 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libavutil55 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libpostproc54 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libswresample2 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: libswscale4 ([<Origin component:'main' archive:'stable' origin:'Debian' label:'Debian-Security' site:'security.debian.org' isTrusted:True>]) Checking: python-google-compute-engine ([<Origin component:'main' archive:'google-compute-engine-stretch-stable' origin:'google-compute-engine-stretch-stable' label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com' isTrusted:True>]) Checking: python3-google-compute-engine ([<Origin component:'main' archive:'google-compute-engine-stretch-stable' origin:'google-compute-engine-stretch-stable' label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com' isTrusted:True>]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals What I am attempting to do is automatically install new tor versions when they are released. Will this do that automatically? How can I keep this process running? Thanks. --Keifer

3 9

Relay Consensus Low
by Matt Westfall 02 Jun '19

02 Jun '19

My tor node: https://metrics.torproject.org/rs.html#details/B1B10104EB72A1FBBF6687B05F19… Doesn't ever go up above 8800 or so. One thing I notice in Nyx is that my connections never go above about 2000 in and out connections. I have advertised bandwidth of just shy of a gigabit in my config. I understand now that the "advertised bandwidth" is calculated based on observed traffic through the node, which while more reliable and avoids abuse, seems to be counter productive to a degree. Ultimately what do I need to do to get more traffic through my node? Cause I have a 2Gbps fiber sitting here basically doing nothing so I was giving 1Gbps to tor :) Config -------------- RunAsDaemon 1 ControlPort 9051 ORPort 9001 ORPORT [2001:559:c290::fffb]:9001 RelayBandwidthRate 45 MB # Throttle traffic to 100KB/s (800Kbps) RelayBandwidthBurst 50 MB # But allow bursts up to 200KB/s (1600Kbps) DirPort 9030 # ExitPolicy reject *:* # no exits allowed ExitPolicy reject6 *:* Any suggestions appreciated. Matt Westfall President & CIO ECAN Solutions, Inc. Everything Computers and Networks 804.592.1672

6 10

Onionoo and ASN Number/AS Name
by Conrad Rockenhaus 02 Jun '19

02 Jun '19

Hello, Onionoo returns “unknown” for my ASN for some reason (should return 63080) and returns “unknown” for AS Name (Should be GreyPony Consultants - as named in ARIN). I’m trying to find out where things might be potentially breaking here before I start connecting to the route servers at DE-CIX next week. Has anyone seen this type of issue before? Thanks, Conrad

4 3

Verizon.com blocked on Tor Middle Relay on FiOS
by Neel Chauhan 31 May '19

31 May '19

Hi, I have a Tor middle relay on Verizon FiOS. If I try to access Verizon.com on the FiOS connection running a Tor middle relay, I get this error: > Access denied, in accordance with Verizon Information Security Policy > Please contact us if there is a legitimate business need to access this > content. They gave an email address to the EdgeCast NOC that I contacted, but the EdgeCast support said I should contact FiOS and not EdgeCast, even though I think the blocking is on EdgeCast's side (if it was on FiOS then I would get a "Hmm. We’re having trouble finding that site" error from Firefox). Other Verizon sites such as Verizon Wireless and Verizon Media/Oath properties like AOL/Yahoo/Tumblr/HuffPost/etc. are not blocked on FiOS running Tor (heck, I can even sign up for Tumblr on exit relays), even though these other Verizon sites also use EdgeCast. For those who have middle relays on their home broadband connection (not bridge or exit), both on Verizon FiOS and other ISPs regardless of country or technology, please test for if Verizon.com is blocked. Thank You, Neel Chauhan

5 5

Tor relay operators meetup, 25/05/2019 @ RADIX hacklab, Athens
by Vasilis 28 May '19

28 May '19

Dear Tor friends and relay operators, Next Saturday (25.05.2019) a Tor relay operators meetup will take place at RADIX hacklab in Athens. When: Saturday, May 25th, 2019 Time: 19:00 / 7:00 PM Where: Kaniggos 34 & Stournari, Athens 10682, Greece Event link: https://radix.one/en/2019-05-18-tor-meetup/ Hope to see many of you there. Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 1

Tor Relay Operator Meeting at the Gulaschprogrammiernacht
by Christophe Kemp 27 May '19

27 May '19

Hello everyone, there will be a Tor Relay Operator Meeting at the Gulaschprogrammiernacht :) You will find soon more information here: https://entropia.de/GPN See you there! Best regards Chrëscht International Ambassador Frënn vun der Ënn A.S.B.L

1 1

VPNs and Ports
by grarpamp 25 May '19

25 May '19

>> On May 23, 2019, at 4:39 AM, Wallichii <wallichii(a)riseup.net> wrote: >> >> On Thu, 23 May 2019 04:15:36 -0500 >> Conrad Rockenhaus <conrad(a)rockenhaus.com> wrote: >> >>> I’ll be starting a free VPN service soon to allow users that are >>> blocked from using Tor at their location to access Tor. To prevent >>> abuse of the service, I plan on restricting the ability of the VPN to >>> only access 53, 80, 443, 8080, 8443, 9001, and 9030. Are there any >>> other ports I should consider keeping open for the service? >> >> IMO setting up a bridge will help more users because not everyone is >> going to trust someone on the internet giving free proxy, you should >> run a bridge if you want to help more users. That would be an input VPN... perhaps useful if DPI was breaking user's tor access protocols (to bridges or regular entry guards), but not their VPN traffic. Output VPN's could also be useful to allow tor users to bind their stack to it over tor, thus permitting UDP back and forth from clearnet... typical with voice video comms and a bunch of other applications that have been disabled for tor users becase tor only supports TCP. Operators would have to publish their VPN node info somewhere for users to use... or getbridges, getvpns. There are prior exploratory threads on this here before. Operators can also be running and supporting VPNGate.net service as both input and output.

1 0