Put the build VM on VLAN 1010 instead of the untagged legacy network - #4
Merged
Conversation
An untagged net0 lands on the 192.168.178.0/23 network that is being retired (Homelab#37); every other guest carries a VLAN tag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
VM 1100's
net0is untagged, so when started it lands on the legacy192.168.178.0/23network that is being retired (Chrison-Homelab/Homelab#37). The shape now declaresvlan: 1010like every other guest; converge applies the tag.Verification
validate stacks/BuildLab: valid. The VM is stopped; the tag lands on the next BuildLab converge.