> On 22 Sep 2016, at 11:55, Dennis Ljungmark wrote:
>
> On Thu, Sep 22, 2016 at 6:30 PM, teor wrote:
>> ...
>>
Have you considered configuring an IPv6 ORPort as well?
(It's unlikely to affect traffic, but it will help clients that
prefer IPv6.)
>>>
>>> Not sure right now, I've
On Thu, Sep 22, 2016 at 6:30 PM, teor wrote:
> Hi,
>
> I wanted to highlight the following parts of my reply:
>
> The Tor network is quite happy to allocate around 47 MByte/s (yes, 376
> MBit/s) to your relay based on its bandwidth measurements, but it won't do
> that until your relay shows it i
Hi,
I wanted to highlight the following parts of my reply:
The Tor network is quite happy to allocate around 47 MByte/s (yes, 376 MBit/s)
to your relay based on its bandwidth measurements, but it won't do that until
your relay shows it is actually capable of sustaining that traffic over a
10-s
> On 22 Sep 2016, at 04:40, D. S. Ljungmark wrote:
>
> On tor, 2016-09-22 at 12:08 +0200, Aeris wrote:
>>>
>>> Scaling up on more hardware is always an option, but I really want
>>> to
>>> push the limit of the exit node, as the others won't be exits
>>> (Local
>>> network design, really) , and
On tor, 2016-09-22 at 12:08 +0200, Aeris wrote:
> >
> > Scaling up on more hardware is always an option, but I really want
> > to
> > push the limit of the exit node, as the others won't be exits
> > (Local
> > network design, really) , and exit traffic is always more
> > interesting.
>
> When I
On tor, 2016-09-22 at 06:29 +1000, teor wrote:
> >
> > On 22 Sep 2016, at 05:41, nusenu wrote:
> >
> > >
> > > >
> > > > >
> > > > > So, how do we get tor to move past 100-200Mbit? Is it just a
> > > > > waiting game?
> >
> > I'd say just run more instances if you still have resources left
>
Hi John,
thanks for adding all your exit relays (with proper MyFamily config)!
http://www.quintex.com/torgraph.html
https://atlas.torproject.org/#search/contact:quintex
https://lists.riseup.net/www/arc/ornetradar/2016-09/msg00090.html
signature.asc
Description: OpenPGP digital signature
__
> Scaling up on more hardware is always an option, but I really want to
> push the limit of the exit node, as the others won't be exits (Local
> network design, really) , and exit traffic is always more
> interesting.
When I say another instance, it’s on the same hardware.
Because Tor is not fully
D. S. Ljungmark:
>> You have to start another Tor instance to use a little more your CPU
>> > (1 other
>> > core) and so to drain additionnal 150-300Mbps.
>
> Scaling up on more hardware is always an option, but I really want to
> push the limit of the exit node, as the others won't be exits (L
On ons, 2016-09-21 at 17:29 +0200, Aeris wrote:
> >
> > 17 MBytes/s in each direction.
>
> From Atlas graph, your node is currently growing up, so wait few
> weeks more to
> have the real bandwidth consumption, but don’t expect huge change.
It looks as if it stabilized a while ago, and I see mo
10 matches
Mail list logo
