Roman Mamedov schreef op 01/07/14 15:48:
On Tue, 01 Jul 2014 22:36:10 +1000
Tim wrote:
Tom,
Why not run multiple tor relays on different ports on the same IPv4 address?
For example, you could run 6 relays on 6 different ports on your IPv4 address (6 x
180 Mpbs > 1 Gbps).
This would also ut
On Tue, 01 Jul 2014 22:36:10 +1000
Tim wrote:
> Tom,
>
> Why not run multiple tor relays on different ports on the same IPv4 address?
>
> For example, you could run 6 relays on 6 different ports on your IPv4 address
> (6 x 180 Mpbs > 1 Gbps).
>
> This would also utilise your 4 cores much more
My apologies - I wasn't aware of the 2 relays per IP restriction.
Is it for security reasons?
On 1 Jul 2014, at 23:48 , Roman Mamedov wrote:
> On Tue, 01 Jul 2014 22:36:10 +1000
> Tim wrote:
>
>> Tom,
>>
>> Why not run multiple tor relays on different ports on the same IPv4 address?
>>
>>
Tom,
Why not run multiple tor relays on different ports on the same IPv4 address?
For example, you could run 6 relays on 6 different ports on your IPv4 address
(6 x 180 Mpbs > 1 Gbps).
This would also utilise your 4 cores much more efficiently than running 2
relays (each relay will only ever u
Hi there,
You will never be able to utilize the whole gigabit connection, at least
with the current tor version.
I'm also running 2 tor nodes (000myTOR) on a single machine (3rd
gen Core i, Quad Core /w AES-NI) on an single IP,
reaching ~1.3 Gbit/s on an 1000 Base-T FD connection. Since yo
Hi,
I'm running a Tor exit node on a 1gbit connection. Currently it's maxing
at about 180Mbit/s (both ways, so 360Mbit/s) per instance, and I'm
running two instances.
That's not really using the connection well. The box has 4 cores (no
AES-NI) and I'm looking for ways to utilize the other 64
