Opened 13 months ago

Last modified 4 weeks ago

#24264 assigned task

Enable IPv6 reachability testing for the Bridge Authority

Reported by: isis Owned by:
Priority: High Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: dirauth, bridgeauth, ipv6
Cc: karsten Actual Points:
Parent ID: Points: .2
Reviewer: Sponsor: SponsorM

Description

We'll need to set AuthDirHasIPv6Connectivity 1.

Child Tickets

Attachments (3)

Screenshot_2017-12-06_06-05-35.png (61.8 KB) - added by isis 13 months ago.
Screenshot_2017-12-06_06-06-22.png (24.2 KB) - added by isis 13 months ago.
bridges-ipv6.png (61.9 KB) - added by karsten 13 months ago.

Download all attachments as: .zip

Change History (16)

comment:1 Changed 13 months ago by isis

Points: .2
Status: assignedaccepted

comment:2 Changed 13 months ago by isis

Resolution: implemented
Status: acceptedclosed

Done. IIUC, we should be doing reachability testing of bridges' IPv6 ORPorts now.

comment:3 Changed 13 months ago by karsten

Resolution: implemented
Status: closedreopened

Uhm, I believe that the bridge authority marks all IPv6-enabled bridges as not running now! Try fetching an IPv6-enabled bridge from BridgeDB; there are none available. Can you find out what's not working there?

comment:4 Changed 13 months ago by karsten

Cc: karsten added
Priority: MediumHigh

Changed 13 months ago by isis

Changed 13 months ago by isis

comment:5 Changed 13 months ago by isis

Alright… please forgive the awful screenshots, there's not really a way to copy terminal output from the machine I use to access it.

It looks like it's dropping IPv6 connections because of a missing route:

https://trac.torproject.org/projects/tor/raw-attachment/ticket/24264/Screenshot_2017-12-06_06-05-35.png

Here's the current routes:

https://trac.torproject.org/projects/tor/raw-attachment/ticket/24264/Screenshot_2017-12-06_06-06-22.png

From what I understand of IPv6, it doesn't seem like there's anything missing? Am I missing something obvious? Should I just disable AuthDirHasIPv6Connectivity for now?

Changed 13 months ago by karsten

Attachment: bridges-ipv6.png added

comment:6 Changed 13 months ago by karsten

I'm sorry, but I have no clue how to diagnose this problem, nor do I know whether it's better to disable the config option vs. fixing the issue at hand.

I mainly wanted to the report the issue. Please find the following graph showing that there are zero bridges supporting IPv6 as of November 28:


comment:7 in reply to:  5 Changed 13 months ago by teor

Replying to isis:

Alright… please forgive the awful screenshots, there's not really a way to copy terminal output from the machine I use to access it.

It looks like it's dropping IPv6 connections because of a missing route:

https://trac.torproject.org/projects/tor/raw-attachment/ticket/24264/Screenshot_2017-12-06_06-05-35.png

Here's the current routes:

https://trac.torproject.org/projects/tor/raw-attachment/ticket/24264/Screenshot_2017-12-06_06-06-22.png

From what I understand of IPv6, it doesn't seem like there's anything missing? Am I missing something obvious?

There is no default route through eth0.
This probably means you need to tell your machine that eth0 has IPv6.
I can't remember how I did it on mine, it was about 15 months ago!

Should I just disable AuthDirHasIPv6Connectivity for now?

This might be a good idea until you can ping6 ipv6.google.com (for example).

comment:8 Changed 12 months ago by isis

I've disabled the setting for now, but I think I know what needs to be done to get it IPv6 working, or, at least, I've identified at least two problems in the current setup.

comment:9 Changed 12 months ago by karsten

Hmm, looks like Bifroest is down now.

comment:10 in reply to:  8 Changed 10 months ago by beastr0

Replying to isis:

I've disabled the setting for now, but I think I know what needs to be done to get it IPv6 working, or, at least, I've identified at least two problems in the current setup.

Do you need any help with understanding or resolving these problems?

comment:11 Changed 4 months ago by nickm

Milestone: Tor: 0.3.6.x-final

comment:12 Changed 6 weeks ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:13 Changed 4 weeks ago by gaba

Owner: isis deleted
Status: reopenedassigned
Note: See TracTickets for help on using tickets.