IPs and Subnets

Your client account holds your IPs grouped by subnets. By default, your client account has no IP addresses. You can add new subnets by deploying any server or requesting additional IPs. This process is detailed below.

Overview

Servers are provisioned with a public IPv4 subnet. The public IPs are used for server management, and hosting services. All subnets on your account are portable and can be moved between servers in your client account.

The first and last IP in your subnet is for the network and broadcast. The second IP by default is for the Gateway; the third IP is the first usable. Suppose you wish to make all IPs in your subnet usable. See splitting subnets below.

Limitations

  • Subnets are facility specific. To move subnets between facilities you must contact [email protected] This also means that you can only assign subnets to Ports, Bonds, VLANs, and other IPs in the same facility.

  • The only way to use subnets smaller than a /30 is by Routing a Subnet To an Ip.

  • If you delete a subnet from your account there is no guarantee you will receive the same subnet back next time you request additional IPs.

Getting Available IPs

Via Portal

To see all of the subnets and IP addresses available in your Client Account, click Network in the sidebar of the portal then click IPs & Subnets.

📘

In Development

This feature is not yet available in the portal. It is expected to become available late 2022.

Via API

To get a list of all the Subnets on your account, and where they are currently assigned, make a GET request to /ip:

curl -X 'GET' \
  'https://core.hivelocity.net/api/v2/ip' \
  -H 'accept: application/json' \
  -H 'X-API-KEY: $API_KEY'

Requesting Additional IPs

If you want more public IPv4 addresses in your client account you can reserve IPs on a monthly basis.

*Public IPv4 Addresses - You can order additional public IPv4 address space, ranging from a /31 (two IPs) through a /24 (256 IPs). Though there is no technical limit to how these IPs can be configured, we encourage you to use them responsibly. We charge a nominal fee per IPv4 address and per each /64 IPv6 block.

Via Portal

You can order additional IPs from the myVelocity portal by clicking request additional ips on the device details page

You will be asked to fill out the purpose of requesting new IP addresses. This is a requirement imposed by ICANN in order for Hivelocity to acquire additional IP blocks and provide our superior network.

Via API

You can make a POST request to /ip to request additional IPs. This endpoint is not automated. As the purpose of requesting must be manually reviewed and approved. Once the IPs are allocated they will be fully automatable.

curl -X POST \
-H "Content-Type: application/json" \
-H 'X-API-KEY: $API_KEY' \
    -d '{ \
        "prefixLength": 29, \
        "purpose": "WHAT YOU ARE USING THE IPS FOR", \
        "facilityCode": "TPA1" \
    }' \
https://core.hivelocity.net/api/v2/ip

Split & Combine Subnets

Sometimes you may wish to split large subnets into smaller subnets to use across different servers and Routed VLAN Interfaces . To split or combine a subnet you must first remove it from any assignments to a ports, bonds, VLAN interfaces, or other subnets. Only contiguous IP addresses can be combined. If you need to combine two non-contiguous subnets open a ticket with support to get an alternative larger subnet.

Via Portal

📘

In Development

This feature is only supported in the API. Portal support is expected to become available late 2022.

Via API

To split a subnet make a POST request to the /ip/IP_ID/split. This will split the target subnet into two equal halves. For example: Splitting a /28 into two /29s.

curl -X POST \
-H "Content-Type: application/json" \
-H 'X-API-KEY: $API_KEY' \
https://core.hivelocity.net/api/v2/ip/{IP_ID}/split

To combine multiple subnets make a POST request to the /ip/combine.

curl -X POST \
-H "Content-Type: application/json" \
-H 'X-API-KEY: $API_KEY' \
    -d '{ \
        "assignmentIds": [123, 124]
    }' \
https://core.hivelocity.net/api/v2/ip/combine

Deploying without Public IPs

The servers provisioned on the Hivelocity Bare Metal Cloud get allocated a public IPv4 address by default. However, you might want to deploy a dedicated server with no public internet access. It is possible to deploy your servers without public IP addresses, and it is supported for all deployment types.

Via Portal

To deploy an Instant server without a public IP Address, select Don't deploy with Public IPv4 under Optional Settings.

📘

In Development

This feature is not yet available. It will become available late 2022.

Via API

📘

In Development

This feature is not yet available. It will become available late 2022.

Routing IPs

The Hivelocity Bare Metal Cloud provides maximum flexibility when it comes to routing IP Subnets to support a wide range of use cases. IP Subnets can be routed to the following:

  • Individual ports - Most common use case. Direct use with a server's ports.

  • Port bonds - Another common use case. Direct use with a server's bonded ports.

  • To another IP - Common for scenarios requiring many IPs as it makes all IPs of the routed subnet usable.

  • VLAN Interfaces - Common for hypervisor scenarios. Makes a VLAN accessible to the public internet.


Did this page help you?