June 2019 - tor-relays - lists.torproject.org

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