Enable IPv6 reachability testing for the Bridge Authority

We'll need to set AuthDirHasIPv6Connectivity 1.

changed milestone to %Tor: unspecified

added 040-deferred-201915 bridgeauth component::core tor/dirauth dirauth ipv6 milestone::Tor: unspecified parent::31280 points::.2 priority::high resolution::fixed severity::normal sponsor::M status::closed type::task labels

Trac:
Status: assigned to accepted
Points: N/A to .2

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

Trac:
Resolution: N/A to implemented
Status: accepted to closed

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?

Trac:
Resolution: implemented to N/A
Status: closed to reopened

Trac:
Cc: N/A to karsten
Priority: Medium to High

Trac:

Trac:

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:

Here's the current routes:

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?

Trac:

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:

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:

Here's the current routes:

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).

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.

Hmm, looks like Bifroest is down now.

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?

Trac:
Username: beastr0

Trac:
Milestone: N/A to Tor: 0.3.6.x-final

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

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

Trac:
Status: reopened to assigned
Owner: isis to N/A

This still appears to be an issue with Serge.

Bridges don't have IPv6 addresses on relay search #28888 (moved) or in BridgeDB #26542 (moved).

Trac:
Component: Core Tor/Tor to Core Tor/DirAuth
Cc: karsten to karsten, gman999

Serge does not have AuthDirHasIPv6Connectivity knob set, as it wasn't in the recommended torrc.

But I can do right now if it's advised.