tor-relays June 2019

tor-relays@lists.torproject.org

43 participants
35 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays June 2019