Routing a Subnet to an IP

For use cases requiring large amounts of usable IPs, entire subnets can be routed to another IP. When this is done, all IPs in the routed subnet become available for use because a gateway is no longer required on the switch.

Static Routing a Subnet to an IP

Before you can route a subnet to another IP address, you must ensure that all assignments of that subnet - to bonds, ports or VLANs - are removed. You cannot route a subnet to an IP in its own subnet. The routed subnet and the target IP must be in the same facility.

Via the Portal

📘

In Development

This feature is not supported in the portal. It should be available in late 2022.

Via the API

To route a subnet to another IP send a PUT request to /ip/IP_ID , where the IP_ID belongs to the subnet you wish to route, with the target IP as the nextHopIP in the request body.

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

Remove a Subnet's Static Route to an IP

Via the Portal

📘

In Development

This feature is not supported on the portal. It should be available in late 2022.

Via the API

To remove a route from a subnet to another IP send a PUT request to the same /ip/IP_ID with a null value for the nextHopIp field in the request body.

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

Did this page help you?