Skip to content

Commit 1c573c7

Browse files
authored
Update network/ipam/reference-content/ipv6.mdx
1 parent 2d58f6f commit 1c573c7

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

network/ipam/reference-content/ipv6.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,10 @@ Scaleway Elastic Metal servers are compatible with 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+
<Message type="note">
65+
In addition to the possibility of attaching and detaching flexible IP addresses, note that each Elastic Message server also comes with a statically routed public IPv4 address, which cannot be detached, other than manually.
66+
</Message>
67+
6468
#### Private IPv6
6569

6670
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.

0 commit comments

Comments
 (0)