Skip to main content
Code42 Support

Use IPv4 and IPv6 in your Code42 environment

Applies to:
  • CrashPlan PROe

Overview

The Code42 platform can be configured to use IPv4 only, IPv6 only, or both IPv4 and IPv6 (also called dual stack). This article describes how to configure your existing Code42 environment to use both IPv4 and IPv6 addresses.

If you are installing the Code42 platform in an environment that uses IPv6 only, see our installation instructions.

IPv6 support

The Code42 platform version 4.3 and later supports IPv6.

Compatible With IPv6
  • Enterprise server
  • CrashPlan app for Windows, OS X, and Linux
  • Administration console
Not Compatible With IPv6
  • CrashPlan mobile app
  • SharePlan app
  • SharePlan mobile app
  • SharePlan web app

Considerations

  • You must have an on-premises master server running version 4.3 or later to use IPv6.
  • The Code42 public cloud does not currently support IPv6. If your Code42 environment uses public cloud storage, all connections to the public cloud must use IPv4.
  • An enterprise server cannot be configured to communicate with a RADIUS server over IPv6. However, if an enterprise server is configured to communicate with a RADIUS server over IPv4, a CrashPlan app can authenticate with a master server using RADIUS over IPv6.

How dual stack IPv4 & IPv6 works

Dual stack environments rely on DNS hostnames with both A (IPv4) and AAAA (IPv6) records. When a host (CrashPlan device or enterprise server) resolves the hostname for a dual stack enterprise server that has appropriately configured DNS:

  • A host with both IPv4 and IPv6 addresses attempts to connect to the enterprise server's IPv4 address first. If the IPv4 connection is not successful, the client device connects to the enterprise server's IPv6 address.
  • A host with an IPv4 address connects to the enterprise server's IPv4 address.
  • A host with an IPv6 address connects to the enterprise server's IPv6 address.

Dual stack configuration guidelines

Follow these guidelines to configure dual stack support in your Code42 environment:

  • Assign IPv4 and IPv6 addresses to your enterprise servers.
  • Configure enterprise server hostnames with A (IPv4) and AAAA (IPv6) records.
  • Configure CrashPlan devices with IPv4 addresses, IPv6 addresses, or both.

Enterprise server address configuration options

Enterprise server addresses must be configured in a specific way to support dual stack IPv4 and IPv6. Each enterprise server has two types of addresses that are configured in the administration console:

Primary & secondary addresses

The Primary network address and Secondary network address are both used for multiple types of communication in a Code42 environment:

In a dual stack environment, a host (device or enterprise server) attempts to connect to the primary address first. If the host cannot connect, it attempts to connect to the secondary address.

Although dual stack hosts always prefer IPv4 when they resolve hostnames with both A (IPv4) and AAAA (IPv6) records, you can configure the primary and secondary server addresses to control whether hosts use IPv4 or IPv6. The following tables summarize the available configuration options.

Recommended configuration options

Primary Network Address Secondary Network Address Behavior
Hostname with A (IPv4) and AAAA (IPv6) records IPv6 address or IPv4 address
(Allows capable devices to connect in the event of a DNS failure)
  • Dual stack hosts prefer IPv4 and fall back to IPv6
  • IPv6 hosts use IPv6
  • IPv4 hosts use IPv4
Hostname with an AAAA (IPv6) record only Hostname with an A (IPv4) record only
  • Dual stack hosts prefer IPv6 and fall back to IPv4
  • IPv6 hosts use IPv6
  • IPv4 hosts use IPv4
Hostname with an A (IPv4) record only Hostname with an AAAA (IPv6) record only
  • Dual stack hosts prefer IPv4 and fall back to IPv6
  • IPv6 hosts use IPv6
  • IPv4 hosts use IPv4

Alternative configuration options

Primary Network Address Secondary Network Address Behavior
IPv6 address IPv4 address
  • Dual stack hosts prefer IPv6 and fall back to IPv4
  • IPv6 hosts use IPv6
  • IPv4 hosts use IPv4
IPv4 address IPv6 address
  • Dual stack hosts prefer IPv4 and fall back to IPv6
  • IPv6 hosts use IPv6
  • IPv4 hosts use IPv4

Private address

Enterprise servers use the Private address to communicate with each other within a destination.

In a dual stack Code42 environment, configure each enterprise server's private address to use a hostname with A (IPv4) and AAAA (IPv6) records. In this configuration:

  • Dual stack servers prefer IPv4 and fall back to IPv6
  • IPv6 servers use IPv6
  • IPv4 servers use IPv4

Step 1: Assign IPv6 addresses to your host servers

For each server that hosts an enterprise server in your Code42 environment, use the operating system to assign an IPv6 address.

Step 2: Configure upgraded Enterprise servers to accept connections on all addresses

Enterprise servers that have been upgraded from version 4.2.x or earlier only

Enterprise servers running version 4.2.x and earlier listen for connections on a specific IP address. If your Code42 environment contains servers that have been upgraded from version 4.2.x or earlier, configure the enterprise servers to listen on all IPv4 and IPv6 addresses associated with the host server.

Network security impact
Implementing this change may impact your Code42 environment's security by accepting inbound connections on all IPv4 and IPv6 addresses associated with the host server.
  1. Sign in to the enterprise server's administration console.
  2. Double-click the logo in the upper-left corner of the administration console to open the administration console CLI.
  3. Run the following commands:
    address.bind peer ::
    address.bind superpeer ::
    address.bind space ::
    
  4. Restart the enterprise server.
Viewing an Enterprise server's bind configuration
To view an enterprise server's bind configuration, run the address.bind status command from the administration console CLI.

Step 3: Add IPv6 records to Enterprise server hostnames

Based on the enterprise server address configuration option that is best for your Code42 environment, configure your DNS server to add AAAA (IPv6) records for enterprise server hostnames.

Step 4: Configure Enterprise server addresses in the Administration console

Perform these steps for each enterprise server in your Code42 environment:

  1. Sign in to the administration console.
  2. Navigate to Destinations > Servers.
  3. Click the name of the server.
  4. From the action menu, select Edit.
    Server Settings
  5. Configure the enterprise server's addresses:
    • Website protocol, host, and port: Make sure the URL includes the enterprise server's hostname, and the hostname has A (IPv4) and AAAA (IPv6) records in DNS.
    • Primary network address: Configure this address based on the enterprise server address configuration option that is best for your Code42 environment.
    • Secondary network address: Configure this address based on the enterprise server address configuration option that is best for your Code42 environment.
    • Private address: Enter a hostname that has A (IPv4) and AAAA (IPv6) records in DNS.
  6. Restart the enterprise server.

Step 5: Assign IPv6 addresses to your CrashPlan devices

Perform these steps for each CrashPlan device in your environment that will use IPv6:

  1. Use the operating system to assign an IPv6 address.
  2. Restart the CrashPlan service:
  3. Verify that the CrashPlan app can back up:
    • From the administration console, go to Devices, then click the name of the device to view backup status.
    • From the CrashPlan app, go to Backup to view backup status.

External resources

IPv6 (Wikipedia)

  • Was this article helpful?