Skip to content

Commit 86f701b

Browse files
committed
fix(ipam): fix headres
1 parent 80593f1 commit 86f701b

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

network/ipam/reference-content/ipv6.mdx

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -35,15 +35,15 @@ The following products support IPv6:
3535

3636
Scaleway Instances are compatible with IPv6, with the caveat that the Instance must be using [routed IPs](/compute/instances/concepts/#routed-flexible-ip). Recently created Instances use routed IPs by default, older Instances may need to be [moved manually to routed IPs](/compute/instances/how-to/migrate-routed-ips/).
3737

38-
### Public IPv6
38+
#### Public IPv6
3939

4040
You can attach one or multiple public (flexible) IPv6 addresses to your Instance, as well as, or instead of, a public IPv4 address. These public addresses are flexible, meaning that you can detach them from an Instance, hold them in your account, and attach them to a different Instance later, if you want. Each flexible IPv6 address is a `/64` IPv6 subnet.
4141

42-
### Private IPv6
42+
#### Private IPv6
4343

4444
When you attach an Instance to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use.
4545

46-
### Going further
46+
#### Going further
4747

4848
Go further with Instances and IPv6 in the following documentation:
4949

@@ -57,17 +57,17 @@ Go further with Instances and IPv6 in the following documentation:
5757

5858
Scaleway Elastic Metal servers are compatible with IPv6.
5959

60-
### Public IPv6
60+
#### Public IPv6
6161

6262
You can attach one or multiple public (flexible) IPv6 addresses to your Elastic Metal server, as well as, or instead of, a public IPv4 address. These public addresses are flexible, meaning that you can detach them from an Elastic Metal server, hold them in your account, and attach them to a different Elastic Metal server, if you want. Each flexible IPv6 address is a `/64` IPv6 subnet. Flexible IPv6 addresses can also be used as additional IP addresses to create virtual machines on your Elastic Metal server.
6363

64-
### Private IPv6
64+
#### Private IPv6
6565

6666
When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use.
6767

6868
You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
6969

70-
### Going further
70+
#### Going further
7171

7272
Go further with Elastic Metal and IPv6 in the following documentation:
7373
- [How to order a flexible IP](/bare-metal/elastic-metal/how-to/order-flexible-ip/)
@@ -86,19 +86,19 @@ Full information on IPv6 with Dedibox can be found in our [dedicated documentati
8686

8787
Scaleway Load Balancers are compatible with IPv6.
8888

89-
### Public IPv6
89+
#### Public IPv6
9090

9191
You can attach a maximum of one (flexible) IPv6 address to your Load Balancer, in addition to a flexible IPv4 address. The Load Balancer cannot have **only** an IPv6 address. Once attached, the IPv6 address cannot be detached or changed for a different one. Each flexible IPv6 address is a `/64` IPv6 subnet.
9292

93-
### Private IPv6
93+
#### Private IPv6
9494

9595
When you attach a Load Balancer to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use.
9696

97-
### IPv6 at the backend
97+
#### IPv6 at the backend
9898

9999
Load Balancers can also use IPv6 to communicate with their backend servers. When you attach backend servers to a Load Balancer, you can either specify their public IPv6 address, or their private IPv6 address (if the Load Balancer and the backend servers are attached to the same Private Network).
100100

101-
### Going further
101+
#### Going further
102102

103103
Go further with IPv6 and Load Balancers with the following documentation:
104104
- [How to create and manage flexible IPs](/network/load-balancer/how-to/create-manage-flex-ips/)

0 commit comments

Comments
 (0)