- tor-relays - lists.torproject.org

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