Re: [tor-relays] How to post to this list

5) WRAP your lines at around 72 characters long, or set your mailer to do this. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] How to post to this list

1) DO NOT Top Post, backwards it's because that's, reply below what you're replying to. 2) DO NOT Bulk Quote, trim what you're replying to down to the minimum size needed to convey the relavant context. 3) DO NOT Block Reply, piecewise interleave your replies below each piece of context to which

Re: [tor-relays] A lot of Warn messages when bootstrapping Tor 0.3.2.9 (stable)

On Fri, Jan 26, 2018 at 08:16:20PM +1100, teor wrote: > Your relay has probably chosen some overloaded guards. > The problem comes from the extra load on those machines, not your relay. > Your relay will eventually try other guards. > > > Jan 25 18:31:54.000 [warn] Problem bootstrapping. Stuck at

Re: [tor-relays] The Onion Box: Connections

Hi, i think the page 2 on nyx is a god idea. I have stoppet my 2 torservers i canot see and write more, but i hope you understand this. :-) regards Steffen TorGate torgate(at)linux-hus.dk > Am 28.01.2018 um 21:18 schrieb Ralph Wetzel : > > Dear Tor Relay Operators, >

Re: [tor-relays] The Onion Box: Connections

> On 29 Jan 2018, at 07:18, Ralph Wetzel wrote: > > * IP addresses of 'CONNECTED' nodes (list / tree) > * names / fp's of connected nodes (list / tree) > > The latter two are - from my personal perspective - quite useless, as even my > small node already has more than 2k

[tor-relays] The Onion Box: Connections

Dear Tor Relay Operators, following some remarks lately given here concerning the display of 'connections', I did some initial investigations of how to integrate that connection data into The Onion Box. My question is: What are you interested in? What data should be displayed?   Options

Re: [tor-relays] tor on arm vps

good share. thanks. On Sun, Jan 28, 2018 at 8:35 PM niftybunny wrote: > By the way: Ignore the Wiki for providers, its outdated. > > Nusenu is providing a good source > > https://nusenu.github.io/OrNetStats/asnameshare > > If they already have a lot of Exits Its a

Re: [tor-relays] tor on arm vps

If you want Exit + Speed + Cheap + Unlimited Traffic = Online.net / Scaleway.com There is not much Choice. On 28. Jan 2018, at 19:17, Quintin wrote: > > Exit > > On Sun, Jan 28, 2018 at 8:16 PM niftybunny

Re: [tor-relays] tor on arm vps

Exit On Sun, Jan 28, 2018 at 8:16 PM niftybunny wrote: > Exit or Guard? > > > On 28. Jan 2018, at 19:11, Quintin wrote: > > any other providers you can recommend? > > On Sun, Jan 28, 2018 at 7:59 PM niftybunny

Re: [tor-relays] tor on arm vps

Exit or Guard? > On 28. Jan 2018, at 19:11, Quintin wrote: > > any other providers you can recommend? > > On Sun, Jan 28, 2018 at 7:59 PM niftybunny > wrote: > Its better to tell them. I used

Re: [tor-relays] tor on arm vps

any other providers you can recommend? On Sun, Jan 28, 2018 at 7:59 PM niftybunny wrote: > Its better to tell them. I used them for nearly 2 years and I had to > verify myself at one point but no problems after that. > The problem with online.net/scaleway.com is

Re: [tor-relays] tor on arm vps

Its better to tell them. I used them for nearly 2 years and I had to verify myself at one point but no problems after that. The problem with online.net/scaleway.com is that everyone is there. A very good target for a black box sucking of Tor traffic. > On 28.

Re: [tor-relays] Tor uses up all available memory and eventually quits

> On 28 Jan 2018, at 20:51, r1610091651 wrote: > > I think the advice to create swap will get George kicked of VPS, as it goes > right against the wishes of hosting company, and directly affects their > hardware. > > A better advice is to tune tor process to work

Re: [tor-relays] Tor uses up all available memory and eventually quits

I think the advice to create swap will get George kicked of VPS, as it goes right against the wishes of hosting company, and directly affects their hardware. A better advice is to tune tor process to work within memory boundaries. The "MaxMemInQueues 512 MB" is right direction, but from personal