feat(vpc): reorganize troubleshooting and add connectivity testing page #5042
Conversation
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
bene2k1
approved these changes
Jun 2, 2025
RoRoJ
added
the
do not merge
jcirinosclwy
reviewed
Jun 2, 2025
|
|
||
| 2. Try to reach the non-communicating Instance with a ping via `ping instance-name` (where `instance-name` is the name you gave your Instance upon creation.) | ||
|
|
||
| 3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name` |
There was a problem hiding this comment.
Suggested change
| 3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name` | |
| 3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name`. |
jcirinosclwy
reviewed
Jun 2, 2025
| 172.16.8.2 dev ens5 lladdr 02:00:00:1c:0d:9b REACHABLE | ||
| ``` | ||
|
|
||
| 2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab.) |
There was a problem hiding this comment.
Suggested change
| 2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab.) | |
| 2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab). |
jcirinosclwy
reviewed
Jun 2, 2025
|
|
||
| ### Step 3: Try reaching the Instance using its LLA | ||
|
|
||
| If the Instance could not be reached via resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network. |
There was a problem hiding this comment.
Suggested change
| If the Instance could not be reached via resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network. | |
| If the Instance could not be reached via the resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network. |
jcirinosclwy
approved these changes
Jun 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Please describe what you added or changed.