The 4 Steps to Wake Camelot
https://10.42.0.18:8006/
= SPEC-001: Camelot Network Startup Guide
:sectnums:
:toc:
== Background
After extended downtime or networking resets, Camelot (Server) may lose external network connectivity due to bridge configuration not exposing a physical NIC. This guide provides minimal, non-destructive steps to bring Camelot back online for SSH and web access.
== Requirements
* Physical console access to Camelot (keyboard/monitor or IPMI)
* Administrative (root) access on Camelot console
* Frodo (laptop) physically connected to same switch as Camelot
== Method
=== 1. Verify physical NIC name on Camelot
At Camelot console:
```
ip link show
```
Confirm physical NIC name (e.g., `enxc84d4429ae57`) is present and carrier is **ON**.
=== 2. Assign temporary IP on bridge interface
Temporarily assign network-accessible IP to `vmbr0` (existing Proxmox bridge):
```
ip addr add 10.42.0.18/24 dev vmbr0
ip link set vmbr0 up
```
=== 3. Assign compatible IP on Frodo
From Frodo, assign static IP in same subnet:
```
sudo ip addr add 10.42.0.100/24 dev enp0s20u2u1
```
=== 4. Test connectivity
From Frodo:
```
ping 10.42.0.18
ssh allison@10.42.0.18
```
✅ SSH should succeed.
== Implementation
* Run commands as shown above from respective consoles.
* Changes are temporary (reset on reboot).
== Milestones
* [x] Camelot responds to ping
* [x] SSH session successfully established from Frodo
* [ ] Optional: create permanent config to avoid step 2 after reboot
== Gathering Results
Connectivity confirmed when SSH session is established, web UI accessible at `https://10.42.0.18:8006`, and network tools (ping, nmap) show Camelot alive on `10.42.0.0/24`.
NOTE: The network `10.42.0.0/24` humorously reflects an inverted 42—a fitting tribute for a Camelot server in a quest-driven network.