[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #17298 [Tor Sysadmin Team]: IPv6 on cappadocicum
#17298: IPv6 on cappadocicum
-------------------------------+---------------------
Reporter: atagar | Owner: tpa
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Tor Sysadmin Team | Version:
Keywords: | Actual Points:
Parent ID: | Points:
Sponsor: |
-------------------------------+---------------------
Hi Peter. During the dev meeting Jake and other authority operators asked
for a DocTor check for the reachability of their IPv6 ORPort. Presently
five authorities have an IPv6 address and five don't.
{{{
tor26 => 2001:858:2:2:aabb:0:563b:1526
gabelmoo => 2001:638:a000:4140::ffff:189
longclaw => 2620:13:4000:8000:60:f3ff:fea1:7cff
maatuska => 2001:67c:289c::9
urras => has an ipv6 address, but authority is currently down
moria1 => no ipv6 address
dizum => no ipv6 address
Tonga => no ipv6 address
dannenberg => no ipv6 address
Faravahar => no ipv6 address
}}}
This is all well and good, and I
[https://gitweb.torproject.org/doctor.git/commit/?id=a50f3e0ad51b82f9523963bce19aab883f310a96
started writing a DocTor check], but I'm green to IPv6 and running into an
issue on cappadocicum...
{{{
% ping6 2001:858:2:2:aabb:0:563b:1526
connect: Network is unreachable
% test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready"
Running kernel is IPv6 ready
% lsmod | grep -w 'ipv6' | wc -l
0
}}}
No doubt something simple. Most Debian tips such as a
[https://wiki.debian.org/DebianIPv6#IPv6_6to4_Configuration 6to4 config]
look to require elevated permissions. If this is something I can/should
sort out myself then tips welcome. :)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17298>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs