Hi Michael,
>From [0]:
> There is currently no support for running a DIR port on IPv6. Leave any
> DirPort option as is.
HTH,
Sharif
[0]: https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto
--
PGP: 6FB7 ED25 BFCF 3E22 72AE 6E8C 47D4 CE7F 6B9F DF57
signature.asc
Description: PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
In the light of this thread I made an onionoo (-> atlas) feature
request to display the Unmeasured=1 flag on atlas (eventually).
https://trac.torproject.org/projects/tor/ticket/16020
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVVHtkAAoJEFv7XvVCEL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/14/2015 05:09 AM, Sharif Olorin wrote:
> Hi Michael,
>
> From [0]:
>
>> > There is currently no support for running a DIR port on IPv6. Leave any
>> > DirPort option as is.
> HTH,
> Sharif
>
> [0]: https://trac.torproject.org/projects/tor/w
It seems like the most pertinent task would be to fix the problem, not
display it.
Just saying...
Matt
Speak Freely
nusenu:
> In the light of this thread I made an onionoo (-> atlas) feature
> request to display the Unmeasured=1 flag on atlas (eventually).
>
> https://trac.torproject.org/proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
> It seems like the most pertinent task would be to fix the problem,
> not display it.
>
> Just saying...
I agree.
Do we know already which relays are affected and why?
teor asked in the trac entry as well.
https://trac.torproject.
>From my experience, this happens only with exit relays. Changing from
an exit relay to a guard fixes the problem immediately.
I've seen past threads that mentioned deleting your id key would fix
the problem, but that never fixed it for me. But that is also
counter-intuitive given that going from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
>> From my experience, this happens only with exit relays. Changing
>> from
> an exit relay to a guard fixes the problem immediately.
>
> I've seen past threads that mentioned deleting your id key would
> fix the problem, but that ne
Tunnelbroker's ToS don't seem to prohibit proxies/relays, so I don't see
an issue here. Don't know how they'd react to exits, though.
On 13/05/2015 19:09, Michael Gorbach wrote:
Is there anything I should be concerned with w.r.t to activating IPv6 on a
relay that has IPv6 connectivity only thr
Ok, even my node
(https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9)
after 7 days is not yet measured.
But what happens to Tor Network with all these nodes (> 1000) with
consensus=20?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
From my ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Tor BW Authories,
we'd like to bring the following issue to your attention.
Since the last two weeks the amount of unmeasured relays is steadily
rising [1].
unmeasured relays on 2015-05-01: 387
unmeasured relays today: 1087 (and growing)
Gra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Graph showing the last 5 months:
> https://trac.torproject.org/projects/tor/attachment/ticket/13450/unmeasured_relaycount.png
you
>
can also see that the adv. bw. is going down since the beginning
of the month:
https://metrics.torproject.org/ba
A quick update regarding my guard-that-was-exit.
This relay, when it was an exit relay, never got past consensus weight
of 20. When I changed it to guard, the consensus weight immediately
jumped, and bandwidth was finally starting to be used. As usual, it
took a few days for full usage, but it did
On Thu, May 14, 2015 at 08:01:19PM +, nusenu wrote:
> Dear Tor BW Authories,
>
> we'd like to bring the following issue to your attention.
> Since the last two weeks the amount of unmeasured relays is steadily
> rising [1].
Hello nusenu,
Thanks for the kick.
For other statistics, each hour
That will be a problem because that instances will get several
IPv6-addresses during the day because of active privacy extensions and the
router get a new /56 for IPv6 from the ISP every day. A manual change of
the torrc is inefficient for me. Because of that I will deactivate
IPv6-support at the a
14 matches
Mail list logo
