Hello tor-relays team,
I am facing issue trying to set up a private obfs4proxy+tor
relay bridge(centos 7 server) on a vps outside Iran and using
the same methodology obfs4+tor client (Arch linu
Hi Stijn, my first thought is that this might be tor's
DisableDebuggerAttachment feature. It causes proc contents to only be
readable by root. Usually this breaks Nyx's connection resolution but
it can prevent resource usage lookups too. Does setting
'DisableDebuggerAttachment 0' in your torrc caus
> On 4 Feb 2018, at 07:55, George wrote:
>
> tor7:
>> Hello!
>>
>> I'd like to collect some samples for how many MBit/s on a single tor daemon
>> are possible on given CPU model before it is limited by the CPU.
>>
>> If your single tor daemon routes more than 350 MBit/s in each direction
>> an
Hi All,
I initially went to the nyx website to find the right forum to ask
questions. I understood this is the one :-), if not apologies.
So I'm running two relays, one is running on CentOS7, the other Debian
Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is
missing the CPU,
tor7:
> Hello!
>
> I'd like to collect some samples for how many MBit/s on a single tor daemon
> are possible on given CPU model before it is limited by the CPU.
>
> If your single tor daemon routes more than 350 MBit/s in each direction
> and you are running on bare metal it would be awesome if
Hello!
I'd like to collect some samples for how many MBit/s on a single tor daemon
are possible on given CPU model before it is limited by the CPU.
If your single tor daemon routes more than 350 MBit/s in each direction
and you are running on bare metal it would be awesome if you could share your
On Sat, 3 Feb 2018 at 12:50 Moritz Kammerer
wrote:
> Thanks for clarification. I will try LimitNOFILE = 6000. If that crashes
> my NAT box, I'm going to run a bridge.
>
> You could also consider getting a production class router (not some
consumer oriented thing), these don't have to be expensive
Thanks for clarification. I will try LimitNOFILE = 6000. If that crashes
my NAT box, I'm going to run a bridge.
Am 03.02.2018 um 12:38 schrieb teor:
>
>> On 3 Feb 2018, at 22:33, Moritz Kammerer wrote:
>>
>> Hi,
>>
>> I'm running a Tor relay on a Raspberry 2 behind a router using port
>> forward
> At the moment I run a iptables rule which restricts the connection count
> to port 9001 (OR port) to 1000.
If your setup can not handle at least 6k concurrent connections, I'm afraid
it is not suitable for a tor non-exit relay.
If you can, run the latest tor source code from git master, it i
> On 3 Feb 2018, at 22:33, Moritz Kammerer wrote:
>
> Hi,
>
> I'm running a Tor relay on a Raspberry 2 behind a router using port
> forward. Relay bandwidth is set to 1 MByte / second. Tor is accepting so
> many connections that my Raspi can't keep up and my router is getting
> very slow (I ass
Hi,
I'm running a Tor relay on a Raspberry 2 behind a router using port
forward. Relay bandwidth is set to 1 MByte / second. Tor is accepting so
many connections that my Raspi can't keep up and my router is getting
very slow (I assume because of a crappy NAT implementation). Bandwidth
is not an is
On Sat, Feb 03, 2018 at 11:31:18AM +0100, Nicolas Braud-Santoni wrote:
> Hi,
>
> Scheduling sucessful: Tor relays meet up @4pm tomorrow, FOSDEM, room H.3227.
Since some people seem confused (*cough* arma *cough*):
“Tomorrow 4pm” is Sunday, 4pm Central European Time
:P
signature.asc
Descript
Hi,
Scheduling sucessful: Tor relays meet up @4pm tomorrow, FOSDEM, room H.3227.
Best,
nicoo, who accidentally put on an orange shirt
On Sun, Jan 21, 2018 at 08:18:51PM +0100, Nicolas Braud-Santoni wrote:
> Hi again,
>
> On Sat, Jan 13, 2018 at 12:07:43AM +0100, Nicolas Braud-Santoni wrote:
13 matches
Mail list logo
