I don't know the actual numbers for the Raspberry Pi 1, I was just
quoting from Duncan:
https://lists.torproject.org/pipermail/tor-relays/2016-December/011182.html
On 12/06/2016 03:00 PM, diffusae wrote:
Well, I can read and also now the translation from Bits to Bytes.
But I am not sure about
I keep getting Account Takeover Attempt abuses on my Tor exit, and I'm
not sure how to handle them:
It is most likely the attack traffic is directed at one of the following
endpoints:
account.sonyentertainmentnetwork.com
auth.np.ac.playstation.net
auth.api.sonyentertainmentnetwork.com
auth.api
So, I tried putting the IPs into my exit policy like this:
xx.xx.xx.xx-xx.xx.xx:*
But Tor doesn't like that syntax. What's the correct way to block
address ranges in the exit policy?
On 11/01/2016 07:32 AM, Ralph Seichter wrote:
On 01.11.2016 12:56, hwertiout695 wrote:
https://whois.arin.n
For Debian-based systems, on the top of
"/etc/apt/apt.conf.d/50unattended-upgrades" my file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
//"${distro_id}:${distro_codename}-proposed";
Well, Tor-relay-debian says 250KBps (bytes):
https://www.torproject.org/docs/tor-relay-debian.html.en
But Tor-doc-relay says 2Mbps (bits):
https://www.torproject.org/docs/tor-doc-relay.html.en
On 10/31/2016 11:58 PM, ane...@tutanota.de wrote:
In order to clarify this once and for all: If I s
They give me the IP address to block. The problem is yesterday it was on
s01.panelboxmanager.com. Today it was s502.panelboxmanager.com. I was
hoping for a way to block all sub-domains of panelboxmanager.com to
prevent further abuse on that particular network. Guess I'll keep going
per-IP for n
I've been wondering this myself, and recently found this thread:
https://tor.stackexchange.com/questions/791/how-to-calculate-optimal-relay-bandwidth-throughput
TL;DR, using AccountingMax means your relay won't be very stable because
it will be idle for a certain amount of time, whereas RelayBa
It's been mentioned here once before, but you shouldn't be using
Google's DNS servers as they see almost all of the Tor network traffic.
My solution was to run a local DNS resolver (unbound in my case) and to
use at least 2 DNS servers from the Open NIC project:
https://www.opennicproject.org/
I only got 1 abuse complaint, but I also only ran a Tor node for about a
month with a reduced exit policy. I explained that I was running a Tor
exit node, told them I blocked the offending address, and then linked to
the Tor Project website for more info. They thanked me for my time, and
marked
I think you're missing the point of running a Tor relay.
"The Tor network relies on /volunteers/ to *donate* bandwidth."
Volunteer: A person who /freely/ offers to undertake a task, or,
/freely/ offer to do something.
Donate: *give* (money or goods) for a good cause.
The Tor Project doesn't
me in the right direction. I should
probably start checking logs first when something stops working...
On 06/11/2016 09:50 AM, SuperSluether wrote:
Ok maybe I spoke too soon. After running rpi-update and rebooting,
it's still having trouble starting. I'll poke around and see if I can
ith this.
On 06/11/2016 09:35 AM, SuperSluether wrote:
I have the Raspberry Pi Model B 2, which has an ARM7 processor. As
such, I am able to use the official Debian repository without issue.
Current version of Tor is 0.2.7.6-1~d80.jessie+1. Systemd is at
version 215-17+deb8u4.
I poked around
16 03:13 AM, Peter Palfrader wrote:
On Fri, 10 Jun 2016, SuperSluether wrote:
After rebooting my Raspberry Pi for a few updates, Tor is not working
properly. From the logs,
[warn] OpenSSL version from headers does not match the version we're running
with. If you get weird crashes, that mi
After rebooting my Raspberry Pi for a few updates, Tor is not working
properly. From the logs,
[warn] OpenSSL version from headers does not match the version we're
running with. If you get weird crashes, that might be why. (Compiled
with 100010bf: OpenSSL 1.0.1k 8 Jan 2015; running with 100011
Off topic, but Minecraft is VERY easy to install in Linux because you
don't actually install it. You simply "apt-get install openjdk-8-jre"
and run the Minecraft.jar file.
On 05/31/2016 05:10 PM, Gumby wrote:
Minecraft is not very easy to install in Linux.
- @Percy - so why would */Tor accept
In my opinion, Tor should update the "fast" flag as well. 100KBytes/s
isn't very fast by today's standards.
On 04/07/2016 01:39 PM, Roger Dingledine wrote:
On Thu, Apr 07, 2016 at 08:21:55PM +0200, Michael Armbruster wrote:
To be a relay, your bandwidth has to be at least 250KB/s. [2]
[2] htt
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting
bits/bytes. Sorry for that confusion.
I found where my numbers came from:
https://www.torproject.org/docs/tor-relay-debian.html.en
"If you have at least 250 kilobytes/s each way, please help out Tor by
configuring your T
While I don't have any actual numbers, I'm pretty sure you won't be
getting a guard flag with that kind of speed. Actually, I don't think
you'll get much traffic at all with that slow of a relay, especially
since the recommended upload speed is 2Mbps (1600kBytes/s).
At any rate, you'll still g
Thanks, this will be very helpful!
I suppose now I have to figure out the AS numbers for the different VPS
providers. Any ideas on how to find those?
On 04/05/2016 02:06 PM, Felix Eckhofer wrote:
Hey.
Am 05.04.2016 20:24, schrieb SuperSluether:
I want to host an exit relay, but at the same
I want to host an exit relay, but at the same time I don't want to use a
service that already hosts multiple Tor relays. Is there a website that
lists relays by AS Names so I can find a service that isn't already
populated with Tor?
___
tor-relays mai
ion
speed? Should I run a bridge instead?
SuperSluether
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
From what I understand, the 3% that was lost should eventually be
distributed to the remaining relays, correct?
On 02/28/2016 08:39 AM, Kurt Besig wrote:
On 2/28/2016 5:00 AM, nusenu wrote:
Looks like SG.GS stopped their guard relays. They had >3% guard probability.
+---++
Are you using the official Tor repository? The Tor version in the Ubuntu
repositories is still on version 2.6.10. I suppose your script still has
a problem though, since you're still running 2.4.27.
On 02/25/2016 01:41 PM, stea...@nym.mixmin.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash:
Hi,
My Raspberry Pi and Ubuntu Server already have the updated version of
libc6. Is a reboot still required? I thought only kernel updates
required a reboot.
On 02/22/2016 04:44 PM, nusenu wrote:
Hi,
if we assume for simplicity that every relay running Linux that has not
rebooted since 2016
Try running "sudo lsof -i :9001"
That should tell you what process is bound to the port, and also give
you the PID so you can kill it.
On 02/14/2016 07:10 AM, Volker Mink wrote:
I think I found something.
could not bind to 0.0.0.0:9001: address already in use
Where can i set the bindin
2016, at 06:33, SuperSluether <mailto:supersluet...@gmail.com>> wrote:
My exit node's consensus weight just jumped from 20 to 1750
overnight. When I checked to see how things were going, my log file
is full of nameserver problems, happening every couple of minutes:
Jan 31 14:12:40.
My exit node's consensus weight just jumped from 20 to 1750 overnight.
When I checked to see how things were going, my log file is full of
nameserver problems, happening every couple of minutes:
Jan 31 14:12:40.000 [warn] eventdns: All nameservers have failed
Jan 31 14:12:40.000 [notice] eventd
I really hope this isn't gonna post a duplicate, but it didn't go
through the first time I sent it.
Forwarded Message
Subject:Nameservers fail and come back at the same time?
Date: Sun, 31 Jan 2016 13:33:24 -0600
From: SuperSluether
To:
ext release of arm (now called nyx) accounts
for this.
On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether
wrote:>>> Found this error when checking my relay today:
ARM_NOTICE Read the last day of bandwidth history from the state file (-
seconds is missing)
Every time I start arm, the
message, not an error,
and it's simply telling you that it wasn't able to prepopulate all the
data.
Tor has changed its state file format which actually breaks that
feature entirely. The next release of arm (now called nyx) accounts
for this.
On Thu, Jan 28, 2016 at 10:02 AM, SuperSlu
Found this error when checking my relay today:
ARM_NOTICE Read the last day of bandwidth history from the state file
(- seconds is missing)
Every time I start arm, the -xxx seconds missing is different. The
bandwidth graph is also stuck, but real-time data is still shown.
Is this a prob
31 matches
Mail list logo
