docs(elastic-metal): Fix IPv6 details for PN ext-add-elastic-metal#5770
Open
florian-forestier wants to merge 1 commit intoscaleway:mainfrom
Open
docs(elastic-metal): Fix IPv6 details for PN ext-add-elastic-metal#5770florian-forestier wants to merge 1 commit intoscaleway:mainfrom
florian-forestier wants to merge 1 commit intoscaleway:mainfrom
Conversation
Updated doc to explain for IPv6. Sometimes (not always, don't know why), when using a PN with IPv6, the server will contact the wrong DHCP server, leading in an invalid lease, preventing the server to communicate with others. In this case, we'll have to manually set an IP.
bene2k1
reviewed
Nov 6, 2025
| <Message type="important"> | ||
| If you are running multiple virtual machines on an Elastic Metal server, our managed DHCP is not currently able to distribute IP addresses to your virtual machines. We recommend that you use the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/) to book IP addresses for your virtual machines, and assign them manually. | ||
|
|
||
| Also, if you are using a IPv6 private network, your Elastic Metal server may contact the public DHCP server instead of your Private Network's one. If it occurs, you will not be able to communicate with other |
Member
There was a problem hiding this comment.
@copilot
Suggested change
| Also, if you are using a IPv6 private network, your Elastic Metal server may contact the public DHCP server instead of your Private Network's one. If it occurs, you will not be able to communicate with other | |
| Also, if you are using an IPv6 Private Network, your Elastic Metal server may contact the public DHCP server instead of your Private Network's DHCP server. If this occurs, you will not be able to communicate with other resources in your subnet, except by manually assigning an IP address. |
RoRoJ
added
the
do not merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Your checklist for this pull request
Description
Updated doc to explain for IPv6. Sometimes (not always, don't know why), when using a PN with IPv6, the server will contact the wrong DHCP server, leading in an invalid lease, preventing the server to communicate with others. In this case, we'll have to manually set an IP.