Opened 2 years ago

Last modified 3 months ago

#24264 assigned task

Enable IPv6 reachability testing for the Bridge Authority

Reported by: isis Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/DirAuth Version:
Severity: Normal Keywords: dirauth, bridgeauth, ipv6, 040-deferred-201915
Cc: karsten, gman999, jan@… Actual Points:
Parent ID: #31280 Points: .2
Reviewer: Sponsor: SponsorM

Description

We'll need to set AuthDirHasIPv6Connectivity 1.

Child Tickets

TicketStatusOwnerSummaryComponent
#26542closedphwDistribute IPv6 bridges through bridges.torproject.orgCircumvention/BridgeDB
#28888reopenedmetrics-teamThe Relay Search Results table doesn't show the IPv6 capability of a bridgeMetrics/Relay Search

Attachments (3)

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

Download all attachments as: .zip

Change History (28)

comment:1 Changed 2 years ago by isis

Points: .2
Status: assignedaccepted

comment:2 Changed 2 years ago by isis

Resolution: implemented
Status: acceptedclosed

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

comment:3 Changed 2 years 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 2 years ago by karsten

Cc: karsten added
Priority: MediumHigh

Changed 2 years ago by isis

Changed 2 years ago by isis

comment:5 Changed 2 years 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 2 years ago by karsten

Attachment: bridges-ipv6.png added

comment:6 Changed 2 years 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 2 years 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 2 years 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 2 years ago by karsten

Hmm, looks like Bifroest is down now.

comment:10 in reply to:  8 Changed 23 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 16 months ago by nickm

Milestone: Tor: 0.3.6.x-final

comment:12 Changed 13 months 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 13 months ago by gaba

Owner: isis deleted
Status: reopenedassigned

comment:14 Changed 12 months ago by teor

Cc: gman999 added
Component: Core Tor/TorCore Tor/DirAuth

This still appears to be an issue with Serge.

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

comment:15 Changed 12 months ago by 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.

comment:16 Changed 12 months ago by arma

Yes, let's try it, and see if everything gets better (or if something unexpected catches fire).

Thanks!

comment:17 Changed 12 months ago by gman999

AuthDirHasIPv6Connectivity 1 knob set

comment:18 Changed 12 months ago by gman999

All seems fine almost 24 hours later. Can someone confirm on the bridgedb end?

It would be nice if the heartbeat showed ipv6 vs. ipv4, but I think that's been discussed.

comment:19 Changed 12 months ago by darkspirit

Cc: jan@… added

comment:20 in reply to:  15 Changed 12 months ago by teor

Replying to gman999:

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

Let's fix the recommended torrc. Where did you get it from?

Replying to gman999:

All seems fine almost 24 hours later. Can someone confirm on the bridgedb end?

Metrics now shows IPv4 and IPv6. But bridgedb still just has IPv4, which might be a bridgedb bug. We'll follow that up on #26542.

It would be nice if the heartbeat showed ipv6 vs. ipv4, but I think that's been discussed.

Our IPv6 logs and stats are still pretty minimal. You're right, we should improve them. I opened #28919.

comment:21 Changed 11 months ago by nickm

Keywords: 040-deferred-201915 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring some tickets from 0.4.0 without proposing them for later. Please tag with 041-proposed if you want to do them.

comment:22 Changed 4 months ago by phw

Parent ID: #31268

comment:23 Changed 4 months ago by phw

Parent ID: #31268#31280

comment:24 Changed 3 months ago by arma

I think we are good to go on this ticket?

That is, Serge is testing the reachability of the vanilla ipv6 ORPort for bridges?

(There are some other issues, like bridgedb doesn't give those out, but those are other tickets.)

comment:25 in reply to:  24 Changed 3 months ago by teor

Replying to arma:

I think we are good to go on this ticket?

That is, Serge is testing the reachability of the vanilla ipv6 ORPort for bridges?

How do you know?
I can't find any IPv6 bridges on relay search:
https://metrics.torproject.org/rs.html#search/type:bridge%20running:true%20

(There are some other issues, like bridgedb doesn't give those out, but those are other tickets.)

Is that relay search issue one of these other tickets?

Note: See TracTickets for help on using tickets.