Opened 3 years ago

Closed 2 years ago

#17298 closed enhancement (implemented)

IPv6 on cappadocicum

Reported by: atagar Owned by: tpa
Priority: Low Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Minor Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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 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 6to4 config look to require elevated permissions. If this is something I can/should sort out myself then tips welcome. :)

Child Tickets

Change History (9)

comment:1 Changed 3 years ago by teor

Severity: Minor

atagar, I'm currently working on IPv6 bootstrapping for clients. In my initial patch, I used the 2 authority IPv6 addresses available in Globe. Is there another place I should look (apart from this ticket) to find the latest IPv6 addresses for the authorities?
(Apologies for the off-topic question.)

comment:2 Changed 3 years ago by atagar

Hi teor, you can find the IPv6 addresses by looking at their descriptors. See the DocTor check I mentioned above - the IPv6 address is part of the or_address entry of the consensus' router status entries.

comment:3 Changed 3 years ago by weasel

We can't get IPv6 at 1984. If you need IPv6 for the doctor host, we need to move the service.

comment:4 Changed 3 years ago by atagar

Sure, can do. If we have another spot available then happy to move it over.

comment:5 Changed 2 years ago by atagar

Hi Peter, just a quick bump since I've had another person ask for IPv6 checks (this time on #18177). If this is in my court then let me know.

comment:6 Changed 2 years ago by weasel

It is still blocking on getting (more) space for VMs in one of the places that do v6.

Thanks for the ping.

comment:7 Changed 2 years ago by weasel

I have set up carinatum and copied the doctor tree to /srv. We can do another sync-run later. Note that carinatum is running jessie.

comment:8 Changed 2 years ago by atagar

Thanks Peter! Disabled DocTor on cappadocicum, synced with carinatum, and resumed the crontab there. Gonna keep this open to keep an eye on this for a day. Once I've seen this happily chugging along I'll resolve this ticket.

I'll leave /srv/doctor.torproject.org around on cappadocicum but after we see this working on carinatum you're welcome to drop it from disk if you'd like.

comment:9 Changed 2 years ago by atagar

Resolution: implemented
Status: newclosed

DocTor has been chugging quite happily on carinatum for a full day now, successfully sending notices. Resolving.

Thanks!

Note: See TracTickets for help on using tickets.