Guide · For administrators
Network and IPs
Network & IPs holds the address blocks the panel gives to VPSs. Each square is an IPv4 address: filled when free, grey when used by a VPS, empty when reserved. Click an address to see it or reserve it.
IPv4 blocks
New block › IPv4: network (e.g. 203.0.113.0/24), gateway, first and last address to use, DNS and the nodes that can use it. Addresses are assigned in order; reserved ones are never given to a VPS.
The VPS gets its IP statically at first boot (cloud-init): no DHCP server needed.
Blocks routed to the server (no virtual MAC)
Some servers don't accept virtual MACs: for example OVH Kimsufi servers, which still receive IP blocks routed to the server's main IP. For these blocks choose New block › IPv4 › Routed to the server:
- the block's network (e.g.
203.0.113.176/28) and the node it reaches (only one: a block goes to a single server); - no gateway: VPSs use an interface routed by the node, with /32 addresses and gateway
169.254.0.1(on-link); - every address of the block can be used, the first and the last too.
OVH IPs imported with Connect a provider on a server that doesn't accept virtual MACs (the panel asks OVH's API) are used the same way, without creating virtual MACs.
Extra IPs of a VPS
A VPS can have more IPv4 addresses, taken from the routed blocks of its node: on the VPS page, Network › Add IPs (the first free ones or specific addresses), and the × next to an address to remove it. The panel adds them live and, if the agent answers, configures them inside the VPS (NetworkManager or systemd-networkd, netplan too):
- if the main IP is routed too, the extra IPs sit on the same interface;
- otherwise (main IP on a normal block) they sit on a second routed interface,
pub0, with a rule that sends the replies of those addresses out through it. A program that must send from one of those IPs (a mail server, for example) picks it as its source address.
Extra IPs survive snapshots, backups and reinstalls (the panel puts them back inside the VPS). Reconfigure IPs redoes the configuration if someone changed it by hand.
If you already added a routed interface with IPs by hand on Incus (before the panel could do it), create the routed block that contains them and use Add IPs › Added by hand: the panel takes them over without touching the VPS, which stays "configured by hand" (you manage the network inside the VPS, or press Let the panel handle it).
IPv6 blocks
New block › IPv6: a /48 to /64 network of the server (e.g. 2001:41d0:303:c216::/64) and the nodes that use it. Each VPS gets a /128 address on a second network interface, with gateway fe80::1.
- The node must have an address in that network (on OVH dedicated servers usually
…::1/128). - The panel prepares the node over SSH (IPv6 forwarding and NDP proxy, file
/etc/sysctl.d/60-koavm-ipv6.conf): the panel's SSH key must be on the node. - In plans with the IPv6 option new VPSs get it automatically. For existing ones use Add IPv6 on the VPS page: the panel hot-plugs the interface and configures it inside the VPS (netplan, NetworkManager or systemd-networkd). Set up again restores it if the customer removed it.
Provider IPs
With Connect a provider the panel reads the IPs from the account and manages them on its own:
| Provider | What it needs | IPs |
|---|---|---|
| OVHcloud dedicated | API keys (the link creates them with the right permissions) | Additional IPs, virtual MAC (routed on Kimsufi) |
| OVHcloud Public Cloud | API keys and project ID | project Additional IPs |
| Hetzner Robot | webservice user | additional IPs with separate MAC, subnets, failover |
| Hetzner Cloud | API token | floating IPs |
| Contabo | client ID, client secret, API user and password | additional IPs |
| Scaleway | API key and project ID | Dedibox failover IPs, virtual MAC |
What the panel does:
- links on its own the nodes that have the same main IP as a server in the account (or by hand with Link a node);
- imports the IPs into a provider block and reads them again every 30 minutes;
- when a VPS takes an IP, it moves it to the node's server and creates the virtual MAC when needed (on servers without them, like Kimsufi, it uses the routed interface);
- if an IP disappears from the account it removes it (if free) or flags it (if used).
Buying IPs
- By hand: Buy an IP on the node shows the price; the order starts only after you confirm.
- Automatically (off by default): choose how many free IPs to keep per node and a monthly spending cap. The panel orders with the account's payment method and never goes above the cap; orders stopped by the cap stay in the history under Orders and costs.
Contabo IPs and OVH Public Cloud Additional IPs are bought from the providers' panels: they show up here at the next sync.
Reverse DNS
For the IPs of connected providers reverse DNS is set from the VPS page (customers can do it too). For blocks added by hand, ask whoever manages the block.