Opened 8 months ago

Last modified 8 weeks ago

#29258 needs_information task

What is the IPv6 story with Snowflake

Reported by: ahf Owned by: dcf
Priority: Medium Milestone:
Component: Circumvention/Snowflake Version:
Severity: Normal Keywords: anti-censorship-roadmap-august
Cc: dcf, arlolra, cohosh Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor28-must

Description

We have a bit of a tendency to forget to test IPv6 solutions properly and in a structured way. We should make sure that IPv6 is working properly with Snowflake.

Child Tickets

Change History (9)

comment:1 Changed 4 months ago by phw

Keywords: anti-censorship-roadmap-maybe added

A brief summary from an anti-censorship meeting in which we discussed snowflake and IPv6:

  • Clients already can connect to snowflake proxies over IPv6.
  • Our broker currently has no IPv6 address.
  • We should have a way to ensure that an IPv6-only Tor Browser can use snowflake (see #29259).

comment:2 Changed 4 months ago by gaba

Keywords: anti-censorship-roadmap added

Adding this tickets to the backlog.

comment:3 Changed 4 months ago by gaba

Keywords: anti-censorship-roadmap-maybe removed

comment:4 Changed 3 months ago by phw

Sponsor: Sponsor19Sponsor28-must

Moving from Sponsor 19 to Sponsor 28.

comment:5 Changed 2 months ago by arlolra

Milestone: Tor: unspecified
Version: Tor: unspecified

comment:6 Changed 2 months ago by dcf

Owner: set to dcf
Status: newassigned
  • Our broker currently has no IPv6 address.

I'm claiming responsibility for getting an IPv6 address for the broker.

comment:7 Changed 2 months ago by gaba

Keywords: anti-censorship-roadmap-august added; anti-censorship-roadmap removed

thanks!

comment:8 Changed 2 months ago by dcf

Status: assignedneeds_information

Back in 2017, I inquired about IPv6 addresses. The reply is that IPv6 is only supported in one of the Greenhost data centers, namely Amsterdam

...instances on our Amsterdam location we can give you an ipv6 prefix. Other locations don't have ipv6 available yet.

The bridge is in the Amsterdam location, so I activated IPv6 for it back then. But the broker is in the Hong Kong location. I sent another support request this week to ask whether anything had changed, but IPv6 is still not available in Hong Kong.

Unfortunately there are no ipv6 block available yet for our Hong Kong customers.

My proposed solution is to migrate the broker to the Amsterdam data center.

  1. Provision a new VM in Amsterdam.
  2. Set it up just as the current broker and rsync past logs to it.
  3. Change the snowflake-broker.bamsoftware.com DNS record to point to the new broker.
    1. Restart our proxy-go instances. Web badge and WebExtension instances should restart automatically.
  4. Run the two brokers in parallel for a while.
  5. Shut down the Hong Kong broker.

If all goes well, this plan means no required downtime. The downside I see is that during step 4, there will be two separate sets of logs (snowflake.log and metrics.log) being kept. We will need to either merge them, or ignore one copy during the transition.

comment:9 Changed 8 weeks ago by arlolra

My proposed solution is to migrate the broker to the Amsterdam data center.

Maybe get some resolution on #31232 first

Note: See TracTickets for help on using tickets.