Repository navigation
docs(network): wearable-01 is a Kea reservation at 10.0.50.14 - #1462
Merged
Merged
Conversation
Reserved in the pfSense UI on 2026-11-11, below the .100-.200 Hicks pool. It held .114 by lease, which is what #1458 recorded; the changelog entry names that one and corrects it. Refs #1416 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L2EwecfJXXbRck9qdq62Jh
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the documentation-only correction of wearable-01’s recorded address.
No open issues 🎉
What changed in this PR
Updates the network documentation to reflect wearable-01’s existing Kea reservation at 10.0.50.14, replacing the .114 lease address recorded in #1458. No runtime configuration changes are included.
Changes:
- Updates the host inventory and diagram to
.14. - Documents the Hicks DHCP pool and the reservation’s dependency on a fixed private Wi-Fi address.
- Adds a dated changelog correction without rewriting the earlier record.
| File | Description |
|---|---|
docs/network.md |
Updates the watch’s address and explains the reservation conditions. |
docs/diagrams/current/network.svg |
Changes the watch’s displayed address to .14. |
docs/changelog.md |
Records the reservation and corrects the earlier lease-address entry. |
Review effort: Balanced
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
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.
What changed
docs/network.md: thewearable-01row says10.0.50.14, and a Hicks note records the.100–.200pool and the watch's reservation below it, with the caveat that it holds only while the watch keeps its private Wi-Fi address Fixed.docs/diagrams/current/network.svgsays.14; PNG re-rendered.docs/changelog.md: a new 2026-11-11 entry that names and corrects the.114the Four facts Lemmiwinks read more recently than HomeLab records them #1416 entry recorded (that was the watch's lease, not a reservation).Why
Refs #1416. The watch was reserved at
.14in the pfSense UI on 2026-11-11, below the pool by the estate's convention, rather than keeping its in-pool lease at.114that #1458 recorded.Blast radius
None to the running lab: docs and the diagram describe a reservation already made in pfSense. MAC published to its OUI only, per
docs/security.md.secrets/*.sops.yamlVerification
python3 scripts/check_docs.py:docs OK../scripts/lint.sh: passed, 12 checks skipped and not run (no docker daemon or pipx here). CI runs them with--require-all.PNG re-rendered with
rsvg-convert --zoom=1.5. No other file named10.0.50.114.make validatenot run in full; docs-only change.make validatepassesDeployed to the lab and confirmed working
Docs updated (
docs/, service README, ordocs/roadmap.md)Generated by Claude Code