Files

defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor

2026-04-12 06:12:20 -07:00

3.4 KiB

Raw Blame History

Gitea and Proxmox VE IP Address Conflict Check

Date: 2026-02-15 (IP matrix); 2026-04-05 (config vars + upgrade runbook cross-links)
Conclusion: No IP conflict for the Gitea VM (VMID 104 @ 192.168.11.31). One other IP (.60) has a documentation ambiguity to verify on the live network.

Gitea VM (VMID 104)

VMID	IP	Hostname	Source
104	192.168.11.31	gitea	ALL_VMIDS_ENDPOINTS, R630_01_02_VMID_INVENTORY, NPMPLUS_SERVICE_MAPPING_COMPLETE

192.168.11.31 is assigned only to VMID 104 (gitea) in the repo. No other VMID uses .31.
config/ip-addresses.conf defines IP_GITEA_INFRA (default 192.168.11.31) and GITEA_PUBLIC_UPSTREAM_* for NPMplus. Platform ops and upgrades: GITEA_PLATFORM_AND_UPGRADE_RUNBOOK.md.

Verdict: No conflict for Gitea (104) with any other VM.

VMID 104 vs 1004 (no conflict)

VMID 104 = gitea = 192.168.11.31
VMID 1004 = besu-validator-5 = 192.168.11.104 (in config: IP_VALIDATOR_4)

Different VMIDs and different IPs; no conflict. The similar numbers (104 vs 1004) can cause confusion but the addresses do not overlap.

Two Gitea deployments (design choice, not conflict)

Docs describe two possible backends for Gitea:

VMID 104 @ 192.168.11.31 — Infrastructure Gitea (Web 80/443). update-npmplus-fourth-proxy-hosts.sh default for gitea.d-bis.org (GITEA_PUBLIC_UPSTREAM_HOST / PORT in config/ip-addresses.conf).
Dev VM (VMID 5700) @ 192.168.11.59 — Optional local Gitea on port 3000 (scripts/setup-dev-vm-users-and-gitea.sh). Use only if you intentionally set GITEA_PUBLIC_UPSTREAM_HOST=$IP_DEV_VM and GITEA_PUBLIC_UPSTREAM_PORT=3000 before updating fourth NPMplus.

These are two different IPs (.31 and .59). Older NPM backups may still show 192.168.11.60:3000 (pre–IP_DEV_VM move); re-run the fourth NPM script or align the proxy row manually.

192.168.11.60 — documentation ambiguity (verify on network)

ALL_VMIDS_ENDPOINTS.md: VMID 3000 (ml110) = 192.168.11.60.
R630_01_02_VMID_INVENTORY.md (r630-01): VMID 3000 = service-1 = 192.168.11.60.
Dev/Codespaces docs: VMID 5700 (dev VM) = 192.168.11.59 (updated 2026-02 to resolve conflict).

So 192.168.11.60 is now assigned only to VMID 3000 (ML). On a single 192.168.11.0/24 segment only one VM can have .60. Action: On Proxmox, confirm which VMID actually has 192.168.11.60 (e.g. pct exec or qm guest cmd and check ip a, or inspect CT/VM net config). Update the docs so only one VMID is assigned .60, or confirm one of the two is decommissioned/moved.

192.168.11.202 — no active conflict

VMID 2506 (besu-rpc-luis-0x1) was destroyed (2026-01-18 / 2026-02-08); previously used .202.
VMID 8642 (vault-phoenix-3) is running at 192.168.11.202.

.202 is now used only by 8642; 2506 is gone. No current conflict.

Recommendation

Gitea (104 @ .31): No change needed; no IP conflict.
Config: Use IP_GITEA_INFRA / GITEA_PUBLIC_UPSTREAM_* from config/ip-addresses.conf (already present).
Done: Dev VM (5700) moved to 192.168.11.59; .60 is now only VMID 3000 (ML). Reconfigure LXC 5700 on Proxmox to use .59 if not already.
Upgrades: scripts/operator/upgrade-gitea-lxc.sh and GITEA_PLATFORM_AND_UPGRADE_RUNBOOK.md.

3.4 KiB Raw Blame History Unescape Escape