Skip to content

docs(kb): move a VergeOS system to a new subnet - #497

Open
CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-move-system-new-subnet
Open

CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-move-system-new-subnet

Conversation

@CarlRodabaugh

Copy link
Copy Markdown
Collaborator

Summary

New KB article: knowledge-base/posts/move-system-to-new-subnet.md.

No public page covers re-addressing an existing VergeOS system when its upstream subnet changes. The article walks through the move in order:

  1. Get console/IPMI access on the new subnet first.
  2. Take the login account off emailed 2FA codes for the window. The UI path is System → Users → Edit → Two Factor Type.
  3. Leave the core network alone.
  4. Edit the External network's IP Address, Network Address and DNS Servers. The UI path is Networks → List → External → Edit.
  5. Set the new gateway as the Target IP of the External network's Default gateway rule, then run Apply Rules. The edit form has no gateway field.
  6. Repoint any incoming site sync on the sending system.

A warning up front explains how you can lose UI access partway through.

Verification

  • UI paths and field labels were checked on a 26.1.8 system.
  • A support SME confirmed the procedure.
  • Rendered locally with mkdocs serve.
  • All links return 200 on docs.verge.io.

🤖 Generated with Claude Code

How-to for re-addressing a system when its upstream management subnet
changes: secure console/IPMI access first, move the login off email 2FA,
edit the External network's IP and DNS, set the new gateway as the Target
IP of the Default gateway rule and Apply Rules, then repoint any incoming
site sync. The core network is left alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant