- tor-relays - lists.torproject.org

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 16 Jun '19

16 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