Ah, thats it. My conntrack entries are full and temporarily increasing it
resolves the problem.
What would be a reasonable conntrack limit for a tor exit?
On Thu, Jan 18, 2018 at 10:45 PM nusenu wrote:
>
>
> Quintin:
> >> Do you reach your server's conntrack limit?
> >
> > The word conntrack n
Isn't this an inherent contradiction?
If someone exposes his bandwidth usage information to public access, he already harmed the anonymity of *his* relay.
Yet, as the bandwidth recording & display is local to the monitoring instance (with no API provided), even if disclosed to public access, t
Hi,
On 20/01/18 10:25, Ralph Wetzel wrote:
> As a consequece, I'll consider implementing a recording function into
> The Onion Box.
When you do this, please make it clear to users that making their
fine-grained bandwidth usage information public may harm the anonymity
properties of the Tor network
What about the coinciding Meltdown/Spectre patch with the new release?
Sent from ProtonMail, encrypted email based in Switzerland.
Original Message
On January 18, 2018 10:13 AM, Gisle Vanem wrote:
Alexander Kührmann wrote:
Not any noticable difference in CPU usage for me:
ht
Thank you for that info.
Following the link you provided I found some background details in https://trac.torproject.org/projects/tor/ticket/24729.
We should mention here, that - according to the discussion ongoing - '1 month' and '3 month' data & thus charts will most likely become obsolete.
As
> On 20 Jan 2018, at 18:17, Ralph Wetzel wrote:
>
> Good morning!
> I recently discovered, that the latest bandwidth record of my relay
> (97FC02820912441BC2DFE3ACF433E455714B0AF5) availabe from
> onionoo.torproject.org for the scale of '1 months' and '3 months' is quite
> old, from "2018-01-
