Just to confirm - the same happens to my relay, so this seems to be a general
issue.
Keifer Bly schrieb am Montag, 15. Januar 2024 um 09:29:
> Hi,
>
> So my relay at
> https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D
> is suddenly saying it's a new relay
is thread on the forum:
> https://forum.torproject.net/t/release-0-4-5-12-and-0-4-6-10/2024/6 .
>
> Petrarca:
> For Debian (and Ubuntu and alike), it's recommended to use TorProject
> repository as it is often more up to date than what Debian provides.
> You can
I'm running a relay on Debian (flavor) - all software is up-to-date and the tor
version installed is 4.5.16. So I think it's up the Debian admins to update tor
on their repositories (?); that way at least the Debian relays would get a
proper update I assume.
--- Original Message ---
G
My middle relay 605EE4375EE4C38215C8949F5808863749FD4F4A crashed and I had to
set it up from scratch. It's up again for over 14 hours now, and all logs and
other checks I did look fine - the only thing which is strange is on the
Tor-Metrics page showing "Advertised Bandwidth" as zero (0 B). Any
I noticed that my Relay got a "Not Recommended" Flag. It's running on version
4.2.7 currently. I checked a few things and this is poping up with a apt update
on the Raspberry:
N: Skipping acquire of configured file 'main/binary-armhf/Packages' as
repository 'http://sdscoq7snqtznauu.onion/torpro
Same here - obviously something happening all over in Tor (timezone is CET):
Nov 02 05:29:24.000 [warn] Possible compression bomb; abandoning stream.
Nov 02 05:29:25.000 [warn] Possible compression bomb; abandoning stream.
Nov 02 05:29:29.000 [warn] Possible compression bomb; abandoning stream.
No
Since tonight I can't get any usable Tor connections anymore; restarting Tor
gives the following error message:
Guard TOR2DFNrelB ($0ED0EA324C931CF41CB5272BFB1D015B3D5772A9) is failing more
circuits than usual. Most likely this means the Tor network is overloaded.
Success counts are 152/217. Us
Hello all,
my relay is set up to support 42 Mbps, however does not get any real traffic
routed through it (605EE4375EE4C38215C8949F5808863749FD4F4A). I checked
anything I could think of but everything looks fine to me. Anyone with an idea
what could be wrong here? Many thanks!___
I'm wondering why this relay is almost unused: Fingerprint
605EE4375EE4C38215C8949F5808863749FD4F4A ?
It's running on a 1 Gbit link and there is plenty of unused bandwidth. The
bandwidth is set to 42 Mbps (even prioritized on the internet link). There were
no outages for months and the connecti
I do run a dedicated relay (middle only, non-exit, no guard) and can at least
confirm that the CPU load is very "spiky" indeed. I was wondering myself in the
past but never really cared about it (since it's a dedicated device anyhow).
Attached chart shows just a recent example for information.
So, could it be that there is just a wording issue on tor-metrics - to me
"observed" and "advertised" bandwidth are two different things but they seem to
be the same on tor-metrics. I think I do understand the observed bw, however,
still struggle to understand the advertised bw.
‐‐‐ Origina
Hello all - I see a constant mismatch of my relay regarding the Advertised
Bandwidth vs. the defined and available RelayBandwidthRate.
Tor metrics usually only shows around 1.3 MiB/s as Advertised Bandwidth
(Bandwidth rate: 3 MiB/s, Bandwidth burst: 6 MiB/s).
The torrc config defines:
RelayBand
Great, and many thanks - that explains it: if the bursting-timespan is 1 sec
only only I obviously can't see that bandwidth bursting with my resolution of
10 sec measurements.
‐‐‐ Original Message ‐‐‐
On Thursday, 22. August 2019 05:02, teor wrote:
> Hi,
>
> > On 20 Aug 2019, at 20:2
I'm struggling a bit with the two config options for RelayBandwidthRate and
RelayBandwidthBurst - what I currently have in my torrc config file is:
> ...
> RelayBandwidthRate 8 Mbit
> RelayBandwidthBurst 12 Mbit
> ...
My assumption was that on average the Relay would consume 8 Mbps max. but ove
Just an fyi for those who might be interested...
With upgrading to 0.3.5.8 the memory usage of my Tor relay dropped again to
reasonable levels. It suddenly started to increase end of January causing my
relay to crash twice before leveling around 45% (a week before I had an ISP
outage). Now it's
There is something really strange going on indeed. What I noticed is an
increase of circuits and my device running out of memory until it stopped
working so I had to reboot it on 31. Jan. Then again the memory usage increased
until it leveled out at a rather unusual, high usage. The actual band
Is it just me having issues - today, I couldn't reach the onion-repository of
torproject.org at sdscoq7snqtznauu.onion anymore. It was working until very
recently though. Everything else is working fine (internet, other onion
services, etc.) and I didn't change anything really (just an upgrade t
I was thinking about setting up a monitoring of a Tor-Relay using Telegraf,
InfluxDB and Grafana. Although I did read quite some documenation about it
already I thought it might be good to check for possible experiences made here
before spending (wasting) too much time trying it out myself.
Que
Great - I think that's it! For whatever reason I had a "SocksPolicy reject *"
in my torrc and I did not relate it to the DNSPort config. I removed it and
everything seems to be working fine right away. Many thanks!
‐‐‐ Original Message ‐‐‐
On Friday, 23. November 2018 13:05, teor wrot
Hi,
on a small server I did try to force local DNS requests to the local Tor via
iptables/ferm (Nat, Output-Chain, protocol udp dport domain REDIRECT to-ports
5300). Torrc has the following included: 'DNSPort 127.0.0.1:5300'.
Unfortunately, it doesn't work as expected, but I get a warning in Tor
I read a few times at different places that there is a maximum of two Tor
instances that can be run over one public IP address. My questions:
1) Is this statement true?
2) Is there an easy workaround maybe?
3) Just out of curiosity: what is the background for this limitation (if it is
true)?
Ba
Hello all,
I just got the following in my tor logfile:
[warn] Your Guard GrmmlLitavis ($8C00FA7369A7A308F6A137600F0FA07990D9D451) is
failing a very large amount of circuits. Most likely this means the Tor network
is overloaded, but it could also mean an attack against you or potentially the
22 matches
Mail list logo
