You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: network/ipam/reference-content/ipv6.mdx
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,15 +35,15 @@ The following products support IPv6:
35
35
36
36
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/).
37
37
38
-
### Public IPv6
38
+
####Public IPv6
39
39
40
40
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.
41
41
42
-
### Private IPv6
42
+
####Private IPv6
43
43
44
44
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.
45
45
46
-
### Going further
46
+
####Going further
47
47
48
48
Go further with Instances and IPv6 in the following documentation:
49
49
@@ -57,17 +57,17 @@ Go further with Instances and IPv6 in the following documentation:
57
57
58
58
Scaleway Elastic Metal servers are compatible with IPv6.
59
59
60
-
### Public IPv6
60
+
####Public IPv6
61
61
62
62
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.
63
63
64
-
### Private IPv6
64
+
####Private IPv6
65
65
66
66
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.
67
67
68
68
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.
69
69
70
-
### Going further
70
+
####Going further
71
71
72
72
Go further with Elastic Metal and IPv6 in the following documentation:
73
73
-[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
86
86
87
87
Scaleway Load Balancers are compatible with IPv6.
88
88
89
-
### Public IPv6
89
+
####Public IPv6
90
90
91
91
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.
92
92
93
-
### Private IPv6
93
+
####Private IPv6
94
94
95
95
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.
96
96
97
-
### IPv6 at the backend
97
+
####IPv6 at the backend
98
98
99
99
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).
100
100
101
-
### Going further
101
+
####Going further
102
102
103
103
Go further with IPv6 and Load Balancers with the following documentation:
104
104
-[How to create and manage flexible IPs](/network/load-balancer/how-to/create-manage-flex-ips/)
0 commit comments