Skip to main content
Network bonding joins a server’s two NICs into one redundant bond0 link, keeping the server connected if one link or switch port fails. A bonded server takes an IP from a public network instead of a standard public IP. Latitude.sh’s OS images already include the bonding configuration, so it’s applied automatically when you deploy or reinstall with bonding on. You don’t configure the OS yourself. Because bonding is part of the server’s configuration, reinstalling a bonded server keeps it bonded unless you explicitly turn bonding off. A bond requires a public network.
Bonding replaces the server’s public IP. Update any DNS records and network automation to use the new IP before you bond a server.

​
Bonding a server

You bond a server when you deploy a new one, or by reinstalling an existing one. When deploying a new server:
1

Turn on Bond to a public network

On the Create servers page, find the Bond to a public network toggle in the Advanced section and turn it on.
2

Pick a public network

Choose a public network from the picker. Each option shows its CIDR, location, and how many IPs are free; a full public network is disabled. Deploy is blocked until you pick a public network.
3

Deploy

The server is delivered bonded onto the public network, with a redundant two-NIC link and an IP from the public network.
On an existing server — reinstall it with the Bond to a public network toggle on. This joins the server to the public network and replaces its public IP with a bond IP.
A bonded server’s public network is locked — you can’t re-point a bonded server to a different public network. To move a server, tear down the bond, then bond it onto the other public network.
Not every server can be bonded: bonding has network requirements. This eligibility check applies when you reinstall an existing server: if a server doesn’t meet the requirements, reinstall won’t let you bond it.

​
Removing a bond (teardown)

1

Turn off Bond to a public network

Open Reinstall for the bonded server and turn the Bond to a public network toggle off.
2

Confirm the IP change

Removing the server from its public network replaces its public IP again. Update any DNS records and network automation before you reinstall.
3

Reinstall

The bond is removed, the server’s IP is freed back to the public network, and the server returns to standard networking.
Teardown frees the server’s IP but does not delete the public network or stop its billing — see Billing.

​
What happens to my IP

​
FAQ

Why does deleting my server still bill me? The public network is billed separately from the server. See Billing. Why can’t I delete my public network? A server is still bonded onto it. See Deleting a public network. Can I move a server to another public network? No — a bonded server’s public network is locked. Tear down the bond, then bond the server onto the other public network.