On 13/05/15 00:09, Moritz Bartl wrote:
Hi!
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please enable it, especially if you run an exit! This has to be done
explicitly.
On Thu, 18 Jun 2015 20:40:44 +0200
Jesus Cea j...@jcea.es wrote:
# Declaramos que este nodo TOR es accesible a través de IPv6
ORPort [::]:PUERTO_TOR
You thought it would be this simple. Nope, unlike every other IPv6-capable
program on Earth, in Tor this syntax of bind to all IPs is not
nusenu nus...@openmailbox.org wrote
Sat, 16 May 2015 08:26:19 +:
| Since clients are not able to bootstrap over IPv6 yet:
|
| https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6 :
| Directory authorities on IPv6
|
| Clients and relays talk to directory authorities. The
Hello everyone,
I know that most of you know to do this already, but remember to
update your IPv6 firewall! :)
Matt
Speak Freely
___
tor-relays mailing list
tor-relays@lists.torproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/13/2015 01:43 AM, Moritz Bartl wrote:
It is exclusively using accept6/reject6 lines.
Sure - there are currently few trac entries opened for that.
I do currently assume, that the following 2 lines :
ExitPolicy accept *:443
ExitPolicy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/13/2015 02:41 AM, n...@cock.li wrote:
Wildcard accept/reject policies seem to catch both IPv6 and v4 going
from the comment (and code) in src/or/routerparse.c[1]:
When I (naivly) prepend just the following lines into torrc before the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the reminder. Just enabled IPv6 on the 100mbps unmetered exit
I started up yesterday and set appropriate reverse lookup records
for tor exit node identification.
On 05/13/2015 01:43 AM, Moritz Bartl wrote:
On 05/13/2015 12:53 AM, Aaron Hopkins wrote:
I tried configuring this a while ago, but got confused by what appeared to
be conflicting documentation for IPv6 exit policies. Is the ExitPolicy for
IPv6 completely separate (only using accept6/reject6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Moritz Bartl:
ORPort [IPv6::address]:port IPv6Exit 1 ExitPolicy reject6 *:*
Do non-exit relays require the last two lines as well?
https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto :
In order to be able to exit to IPv6 addresses,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since clients are not able to bootstrap over IPv6 yet:
https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6 :
Directory authorities on IPv6
Clients and relays talk to directory authorities. The work with
making directory
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
-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]:
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
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: PGP
Just added 3
--
Kind Regards, Martijn Beekhuis
|
]V[ \ /_\/_
.-'-. //o\ _\/_
-- / \ -- |
[::1] is the IPv6 loopback address - use [::] to listen on any address.
On 05/13/2015 03:09 AM, torser...@ittk.it wrote:
I have enabled it at 1 VPS and 1 Root.
And I enabled it on 2 instances which are connected via
broadbandconnections with dynamic addresses for IPv4 and IPv6. There I got
Hi,
I set IPv6 tor relay
*ORPort [::]:9050*
getting this error when restarting:
###
*sudo tor restartMay 13 16:01:53.021 [notice] Tor v0.2.5.12
(git-3731dd5c3071dcba) running on Linux with Libevent 2.0.21-stable,
OpenSSL 1.0.1f and Zlib 1.2.8.May 13 16:01:53.021 [notice] Tor can't
On Tue, 12 May 2015 22:45:24 -0700, Brian Kroll
br...@fiberoverethernet.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I just enabled four relays, who has the next two? ^_^
Sydney Australia's in the IPv6 house now, wut wut.
Thanks for the reminder. Should've done this months ago.
On 13/05/15 00:09, Moritz Bartl wrote:
Hi!
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please enable it, especially if you run an exit! This has
On 05/13/2015 12:53 AM, Aaron Hopkins wrote:
I tried configuring this a while ago, but got confused by what appeared to
be conflicting documentation for IPv6 exit policies. Is the ExitPolicy for
IPv6 completely separate (only using accept6/reject6 lines) or does it also
make use of lines like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/12/2015 06:09 PM, Moritz Bartl wrote:
Hi!
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please enable it, especially if you run an exit! This has to
How did you measure IPv6 traffic specifically? Ive been running an IPv4+6 exit
for a while now and would be interested to know how much of that is IPv6.
https://atlas.torproject.org/#details/D51EE9D0653AA0D62F4D76AC428DF20F5377846B
Linode has a dashboard page for each of one's vservers that shows,
among other things, graphs of its IPv4 and v6 network bandwidth.
I don't know any details of how this is done but the graphs look MRTG-ish to me.
On Wed, May 13, 2015 at 2:24 PM, Ethan Rose et...@ethanrose.co.nz wrote:
How did
thanks, now I got a similar information:
13:36:02 [WARN] Unable to use configured IPv6 address [::] in a
descriptor. Skipping it. Try specifying a globally reachable address
explicitly.
what do you think?
Marcel
JovianMallard t...@sec.gd hat am 13. Mai 2015 um 15:27 geschrieben:
[::1]
Googling finds these:
https://lists.torproject.org/pipermail/tor-commits/2012-May/042676.html
https://trac.torproject.org/projects/tor/ticket/5146
https://trac.torproject.org/projects/tor/ticket/5940
Looks like tor hasn't been taught to turn [::] into a reachable global
IP address yet (for
On Tue, May 12, 2015 at 11:09 PM, Moritz Bartl mor...@torservers.net
wrote:
especially if you run an exit!
1 exit, 2 bridges and 4 general relays are now explicitly IPv6 enabled
Once https://trac.torproject.org/projects/tor/ticket/5788 is done I'll be
able to bring several more online
Done. Thx for the reminder :)
--
PGP Key: https://0x80.io/pub/files/key.asc
PGP Key Fingerprint: 2DF2 79CD 48DD 4D38 F0B6 7557 2E68 D557 49AA 1D99
Note: I'll be transitioning away from this key in the near future.
On 05/13/2015 06:32 PM, Gareth Llewellyn wrote:
On Tue, May 12, 2015 at 11:09
Unfortunately, I can't do this to the CMU Tor exit because the
university network doesn't do IPv6 -- I asked, and and it's on the
list, but there is an awful lot of old equipment which would have to
be replaced first, things like better WiFi coverage are higher
priority, and I can't say that I
I have enabled it at 1 VPS and 1 Root.
And I enabled it on 2 instances which are connected via
broadbandconnections with dynamic addresses for IPv4 and IPv6. There I got
that information after applying the configuration:
07:05:49 [WARN] Unable to use configured IPv6 address [::1] in a
Aaron Hopkins:
I tried configuring this a while ago, but got confused by what
appeared to be conflicting documentation for IPv6 exit policies. Is
the ExitPolicy for IPv6 completely separate (only using
accept6/reject6 lines) or does it also make use of lines like
ExitPolicy accept *:80 which
On Wednesday 13 May 2015 00:09:45 Moritz Bartl wrote:
If your host supports IPv6,
please enable it, especially if you run an exit! This has to be done
Done. Thanks for remembering!
--
Bandie Kojote
Encrypted and signed messages are welcome.
GPG: 0x0607E094
signature.asc
Description: This is
Hi!
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please enable it, especially if you run an exit! This has to be done
explicitly.
https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto
In short,
On Wed, 13 May 2015, Moritz Bartl wrote:
In short, you add:
ORPort [IPv6::address]:port
IPv6Exit 1
ExitPolicy reject6 *:*
(or a more open exit policy respectively)
I tried configuring this a while ago, but got confused by what appeared to
be conflicting documentation for IPv6 exit policies.
If atlas shows an IPv6 ORPort, that means it's working correctly, right?
-tom
On 12 May 2015 at 17:09, Moritz Bartl mor...@torservers.net wrote:
Hi!
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please
Hi all,
On Wed, May 13, 2015 at 12:09:45AM +0200, Moritz Bartl wrote:
We still have a depressingly low number of relays that support IPv6
(currently only ~120 of ~1900 relays). If your host supports IPv6,
please enable it, especially if you run an exit! This has to be done
explicitly.
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I just enabled four relays, who has the next two? ^_^
//Brian
Ana Lucia Cortez:
On Wed, May 13, 2015 at 12:09:45AM +0200, Moritz Bartl wrote:
Come on guys, we only need 6 more IPv6 relays to help Moritz out
of his depression ...
We
36 matches
Mail list logo
