Re: [tor-relays] Auto Upgrading Tor Using Unattended Ugrades
On 31.05.2019 02:43, teor wrote: On 31 May 2019, at 10:34, Keifer Bly wrote: Upon trying to open that folder, I got this. var/log/unattended-upgrades: No such file or directory Try a leading slash: /var/log/unattended-upgrades sorry, slash was lost when I copy & paste. :-( If you want to read as user the files in /var/log/ $ usermod -aG adm user have a look: https://lists.torproject.org/pipermail/tor-relays/2019-May/017311.html -- Ciao Marco! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Verizon.com blocked on Tor Middle Relay on FiOS
sems like verizon blocks all tor connections > Am 30.05.2019 um 23:49 schrieb René Ladan : > > Blocked here too, isp is xs4all in the Netherlands. > > René > > > Op do 30 mei 2019 23:15 schreef TorGate : >> also blocked here >> >> > Am 30.05.2019 um 11:54 schrieb abuse net >> > : >> > >> > Same here. Blocked. >> > >> >> On 30. May 2019, at 10:20, Roman Mamedov wrote: >> >> >> >> On Wed, 29 May 2019 17:58:10 -0400 >> >> Neel Chauhan wrote: >> >> >> >>> For those who have middle relays on their home broadband connection (not >> >>> bridge or exit), both on Verizon FiOS and other ISPs regardless of >> >>> country or technology, please test for if Verizon.com is blocked. >> >> >> >> Yes it is blocked from all of my middle relays. >> >> Seems like they block access from any Tor relay IP, and where it's located >> >> doesn't matter (mine are in DCs, not on home connections). >> >> >> >> -- >> >> With respect, >> >> Roman >> >> ___ >> >> 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 > ___ > 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] Relay Consensus Low
Hello thanks for the comments, I might do that, remove the limits, because it's self limiting by the 1 Gbps network port, so it can't use more than that anyway. I'm using an Opnsense routing platform, and I've had more than 4,000 simultaneous connections just running torrents, lol. Igor, it doesn't appear to be a CPU bottleneck: https://puu.sh/DA4GR/2ef1b58e2e.png Am I able to run another tor instance just on different ports on the same IP? According to file descriptor limit I shouldn't be hitting a socket/file descriptor limit either. https://puu.sh/DA4Sh/6e27417c74.png I tried to run chutney tests to see what hardware supports but haven't quite figured out what the command line I should be using is. Any help with that would be appreciated. Thanks, Matt Westfall President & CIO ECAN Solutions, Inc. Everything Computers and Networks 804.592.1672 -- Original Message -- From: "teor" To: tor-relays@lists.torproject.org Sent: 5/30/2019 7:05:20 PM Subject: Re: [tor-relays] Relay Consensus Low Hi, On 25 May 2019, at 01:13, 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. That's unusual, because there are about 7,000 relays in the network. How many simultaneous connections does your router support? (Lots of them claim to support unlimited connections, but only support a few hundred or a few thousand.) 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 :) You could remove all the bandwidth limits, and put them back in when tor is using more than you want it to. (Tor tries to keep some extra bandwidth to deal with traffic spikes, so a 1 Gbps limit will get you around 300 kbps sustained traffic.) Here's a more detailed explanation, and some other things to try: https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Onionoo and ASN Number/AS Name
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 smime.p7s Description: S/MIME cryptographic signature ___ 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
Hi, > On 1 Jun 2019, at 14:57, Matt Westfall wrote: > > Hello thanks for the comments, I might do that, remove the limits, because > it's self limiting by the 1 Gbps network port, so it can't use more than that > anyway. Following the instructions here: https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow#TorNetworkLimits It looks like your relay is limited by its own observed bandwidth. (The observed bandwidth that your relay has seen itself using.) So increasing the RelayBandwidthRate would be a good idea. If your relay's observed bandwidth gets above 9 megabytes a second, your relay will be limited by the bandwidth authorities' measurements. (The median measurement for your relay is 8910 scaled kilobytes per second.) https://consensus-health.torproject.org/consensus-health-2019-06-02-04-00.html#B1B10104EB72A1FBBF6687B05F1915D87D00DBDE There might not be much you can do about this: Comcast has slow peering with a large number of internet networks. And it looks like 4/6 of tor's current bandwidth authorities are on those networks. This isn't something Tor can fix: we can only measure the bandwidth that Comcast is giving you. If Comcast has slow peering to US East and Europe, then clients using your relay will be slow. > I tried to run chutney tests to see what hardware supports but haven't quite > figured out what the command line I should be using is. > > Any help with that would be appreciated. You're right, the README is more confusing than it needs to be. Try: ./chutney/tools/test-network.sh --data $[10*1024*1024] If a 10 MB transfer is too fast, try 100 MB. I opened this ticket for us to fix our documentation: https://trac.torproject.org/projects/tor/ticket/30720 T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Onionoo and ASN Number/AS Name
On 6/1/19 10:14 PM, Conrad Rockenhaus wrote: 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? As far as I'm aware onionoo uses maxmind's database [1] for AS-related information and it looks like your ASN hasn't made it into the database yet. [1] https://dev.maxmind.com/geoip/geoip2/geolite2/ -- Jordan https://yui.cat/ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Onionoo and ASN Number/AS Name
Hi, > On 2 Jun 2019, at 15:14, Conrad Rockenhaus wrote: > > 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? Onionoo uses MaxMind's AS database, which is slow to update: https://trac.torproject.org/projects/tor/ticket/26585 If you use RIPE, you can see that the AS is present in IANA and WHOIS, but not in MaxMind: https://stat.ripe.net/63080 T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
