How a server's address reaches it depends on the IP block the address comes from. You choose the kind when you add a block in Infrastructure › IP pools › Add IP block, and a server's kind follows its main address. Check which modes your provider supports before you buy addresses.
The modes at a glance#
| Mode | What your provider must do | IPv6 | Per-server firewall | Notes |
|---|---|---|---|---|
| Routed (default) | Route the addresses to the node's main address, or put them on the node's link | Yes | Yes | Works with almost every provider |
| NAT | Nothing: servers share the node's address | Yes, if the server also has routed IPv6 | Yes | Servers get a private address and a range of the node's ports |
| Bridged | Accept a separate MAC address per IP (for example OVHcloud virtual MACs) | No | No | Needs the node's uplink bridge |
| VLAN (beta) | Carry a tagged VLAN to the node's switch port | No | No | For blocks on a VLAN of yours or your provider's |
| Private network | Nothing | No (IPv4 only) | No security groups on the private card | A second network card linking servers across nodes |
Routed#
The node routes each address to its server. Your provider routes the block (or single addresses) to the node, or the block is on the node's own link and the node answers for the addresses. IPv4 and IPv6 blocks, several addresses per server, and IPv6 subnets per server are all supported. This is the mode to start with. See Routed IPv4 and IPv6.
NAT#
Each node has one private NAT network (10.200.0.0/16 unless you choose another). A server behind NAT gets an address in it and a range of the node's public ports, 20 by default: the first is forwarded to its SSH port, the rest to the same port numbers on the server, TCP and UDP. Use it for cheap plans without a public IPv4 address. Public IPv4 address limits do not count NAT addresses. See NAT servers and port forwards; websites on NAT servers can also be reached by domain name, see Websites by domain.
Bridged#
The server's network card sits on the node's uplink bridge with its own MAC address, and the provider's gateway answers it directly. This is how providers such as OVHcloud deliver extra addresses (virtual MACs); the panel can order the virtual MACs from OVHcloud itself. The node needs its uplink bridge set up first, from the node page.
Not supported for bridged servers: IPv6, the per-server firewall (the node's own network rules still apply on the bridge), and moving the server to another node. See Bridged networking.
VLAN Beta#
Beta: this works and is being tested on more setups; report problems you find.
A public IPv4 block that is on the node's link can be bound to a VLAN. Its servers are bridged onto that VLAN and reach the gateway on it. The node builds the VLAN interface and bridge at run time without touching the host's network configuration. The node's switch port must carry the VLAN tagged; arranging that is up to you or your provider. VLAN servers have no IPv6, no NAT and no per-server firewall. See VLANs.
Private networks#
A private network gives servers a second network card on a network shared by servers on any of your nodes, without public addresses. The nodes carry it between them over an encrypted link, so UDP 51820 must be open between nodes. Customers can make their own networks. See Private networks.
Choosing#
- Your provider routes a block to the server: routed.
- Your provider gives addresses only with its own MAC per address: bridged.
- You want servers without public IPv4: NAT, optionally with routed IPv6.
- Your addresses live on a VLAN delivered to the node: VLAN.
- Servers need to talk to each other privately: add a private network on top of any of the above.
Floating IPs, load balancers, reverse DNS and duplicate address detection work on top of these modes; see Networking.