Update static config #101
Merged
Update static config #101
Conversation
This file contains 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
Updated the notes to fix spelling mistakes, odd formatting choices and add additional information.
…CCDC_Practice_Infrastructure into Update-Static-Config
Updated to add routing and DNS configuration notes. (Still need to fix spelling mistake. I will make a separate PR after this for that)
|
Please DO NOT merge till others I have requested reviewed this. |
P-rple
reviewed
Nov 8, 2024
| @@ -13,6 +18,9 @@ Click Create and fill out the information in the *Basics* window. If you chose t | |||
|
|
|||
| <img src="Images/VMC.png"> | |||
|
|
|||
| > [!IMPORTANT] | |||
| > Selecting the *Untagged* network is preferred to prevent any internal conflicts, and we have observed it is much more stable in our environment. | |||
|
|
|||
| In the *Route* window configure it to use the **Manual** mode so we can make this network *internal* and not able to immediately access the internet. Fill in a `CIDR` range that does not conflict with the host's network (In our case do not use addresses that conflict with `192.168.0.0/21`). You should also set the `Gateway` to be some address in the `CIDR` range you selected. | |||
There was a problem hiding this comment.
I would add, how can someone determine and confirm the host's network CIDR range?
For the purpose of longevity of this document, in the event it ever changes.
P-rple
reviewed
Nov 8, 2024
| > The use of the following options is **OPTIONAL** you can remove all of them, and the netplan can be applied to multiple VMs without issues. | ||
| > ``` | ||
| > match: | ||
| > macaddress: MACADDR |
There was a problem hiding this comment.
Make a note that "MACADDR" is a placeholder for an actual mac address
"FF:FF:FF:FF:FF:FF"
P-rple
requested changes
Nov 8, 2024
P-rple
requested changes
Nov 8, 2024
|
|
||
|  | ||
|
|
||
| 6. Click *add* and fill out the information (IP address *We are on a /21 network*) | ||
| 1. Click *add* and fill out the information. |
There was a problem hiding this comment.
Is this supposed to be 6. instead of 1.
…CCDC_Practice_Infrastructure into Update-Static-Config
P-rple
approved these changes
Dec 9, 2024
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.
Overview of Changes
Updated Linux Static Configuration Documents (standalone) and the Harvester Document to refer to routes and DNS configuration as creating internal networks often requires this.
Reason for Modification
This cleans up some of the old documentation (marginally) and it updates the new Harvester docs with additional information that may be helpful.
Verification
Images.