Re: [tor-relays] Tor Relay Operator Meeting at the Gulaschprogrammiernacht
Hello everyone, the Meetup will be this saturday from 17:45 to 18:45 o'clock at the ZKM CodeHUB. Best regards Chrëscht International Ambassador Frënn vun der Ënn A.S.B.L. Am 19.05.19 um 11:00 schrieb Christophe Kemp: > 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 > > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Auto Upgrading Tor Using Unattended Ugrades
Hi, > On 28 May 2019, at 06:18, Keifer Bly wrote: > > So I am now auto upgrading tor using the method at > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates > > > Upon testing, this is what I got. > > … > > 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? Step 4 of the instructions runs the process automatically every day. You will also need to follow these instructions to get the latest tor version: > From my last email: > When I tried updating tor I got a message saying that was the newest version. >>> >>> It looks like you're on Debian or Ubuntu, please follow these instructions >>> to update: >>> https://2019.www.torproject.org/docs/debian.html.en T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Auto Upgrading Tor Using Unattended Ugrades
Hello all, So I am now auto upgrading tor using the method at https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates Upon testing, this is what I got. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: [] Checking: firefox-esr ([]) Checking: google-cloud-sdk ([]) Checking: google-compute-engine ([]) Checking: google-compute-engine-oslogin ([]) Checking: libavcodec57 ([]) Checking: libavfilter6 ([]) Checking: libavformat57 ([]) Checking: libavresample3 ([]) Checking: libavutil55 ([]) Checking: libpostproc54 ([]) Checking: libswresample2 ([]) Checking: libswscale4 ([]) Checking: python-google-compute-engine ([]) Checking: python3-google-compute-engine ([]) 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Relay Consensus Low
Matt, if you only have 1 host, it may be more beneficial to create 2 relays on it (or more than 2 - if you have more than 1 IPv4 address available) using tor-instance-create. You could be hitting the limits of what a single CPU core can do. On Sun, May 26, 2019 at 4:07 PM Keifer Bly wrote: > > Hello Matt, I recently started a new middle relay (torworld) as well, and > also run a PT bridge on a separate network. This is just my knowledge, but > tor relays are not always used to their maximum capacity, so your relay will > receive more traffic some days and less on other days. Different tor relays > are chosen for each user each time they connect, so varying amounts of > traffic are to be expected. As long as your relay is correctly configured, > you should not have much to worry about. > > --Keifer > > > On Sat, May 25, 2019 at 4:48 PM Matt Westfall wrote: >> >> My tor node: >> https://metrics.torproject.org/rs.html#details/B1B10104EB72A1FBBF6687B05F1915D87D00DBDE >> >> 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 >> >> ___ >> tor-relays mailing list >> tor-relays@lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
