diff --git a/10-systems/networks/pfsense-router.md b/10-systems/networks/pfsense-router.md index f37801e..48a34f6 100644 --- a/10-systems/networks/pfsense-router.md +++ b/10-systems/networks/pfsense-router.md @@ -1,7 +1,7 @@ --- owner: gmikcon status: active -last_reviewed: 2026-05-10 +last_reviewed: 2026-09-29 review_interval: 90d confidence: high source_of_truth: owner-confirmed-and-ssh-pfsense @@ -15,9 +15,15 @@ - Web UI: `https://192.168.1.1/` - SSH: `ai_agent_ro@192.168.1.1:22`, read-only access for documentation agents. -- SSH authentication: owner-managed key. +- SSH authentication: owner-managed key. The private key `gnexus_book_pfsense_ro` is stored on the owner's PC `gmikcon` (192.168.1.129, dynamic DHCP address) at `~/.ssh/gnexus_book_pfsense_ro`. Agents without direct access can reach pfSense through that PC over SSH (password auth, see gnexus-creds secret `gbook-creds`). - Secret values are not stored in this repository. +### Read-only account limitations (verified 2026-09-29) + +- `ai_agent_ro` (uid 2000, group nobody) can run basic commands (`date`, `ls`, `id`, `cat /etc/ssh/sshd_config`) but CANNOT read `/var/log/*` — all logs are `root:wheel` mode 600. +- No `sudo`, no `clog` binary in PATH, no Match/ForceCommand block in sshd_config — the restriction is plain file permissions. +- WAN outage analysis must therefore use alternative sources: NetworkManager connectivity logs on LAN hosts (`journalctl | grep "state is now"`), OpenVPN reconnect logs on tunnel endpoints, or the pfSense Web UI (owner). + ## Role - Local network edge. diff --git a/90-maintenance/pending-changes/20260929191953-a9c3f690.json b/90-maintenance/pending-changes/20260929191953-a9c3f690.json new file mode 100644 index 0000000..661f808 --- /dev/null +++ b/90-maintenance/pending-changes/20260929191953-a9c3f690.json @@ -0,0 +1,19 @@ +{ + "id": "20260929191953-a9c3f690", + "kind": "doc", + "target": "10-systems/networks/pfsense-router.md", + "summary": "Document pfSense SSH key location on gmikcon PC and ai_agent_ro log-read limitations", + "reason": "Discovered 2026-09-29: pfSense SSH key location (gmikcon PC, ~/.ssh/gnexus_book_pfsense_ro) and that ai_agent_ro cannot read /var/log (root-only, no sudo/clog) — verified live over SSH.", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-09-29\nreview_interval: 90d\nconfidence: high\nsource_of_truth: owner-confirmed-and-ssh-pfsense\n---\n\n# pfSense Router\n\nCentral router and firewall for the local network.\n\n## Access\n\n- Web UI: `https://192.168.1.1/`\n- SSH: `ai_agent_ro@192.168.1.1:22`, read-only access for documentation agents.\n- SSH authentication: owner-managed key. The private key `gnexus_book_pfsense_ro` is stored on the owner's PC `gmikcon` (192.168.1.129, dynamic DHCP address) at `~/.ssh/gnexus_book_pfsense_ro`. Agents without direct access can reach pfSense through that PC over SSH (password auth, see gnexus-creds secret `gbook-creds`).\n- Secret values are not stored in this repository.\n\n### Read-only account limitations (verified 2026-09-29)\n\n- `ai_agent_ro` (uid 2000, group nobody) can run basic commands (`date`, `ls`, `id`, `cat /etc/ssh/sshd_config`) but CANNOT read `/var/log/*` — all logs are `root:wheel` mode 600.\n- No `sudo`, no `clog` binary in PATH, no Match/ForceCommand block in sshd_config — the restriction is plain file permissions.\n- WAN outage analysis must therefore use alternative sources: NetworkManager connectivity logs on LAN hosts (`journalctl | grep \"state is now\"`), OpenVPN reconnect logs on tunnel endpoints, or the pfSense Web UI (owner).\n\n## Role\n\n- Local network edge.\n- Firewall and routing point for internal infrastructure.\n- DHCP server for `home-lan` and `home-iot-lan`.\n- Local DNS resolver through Unbound.\n- Local NTP endpoint.\n- Part of the path between local infrastructure and services reachable through trusted network paths.\n\n## Platform\n\n- Hostname: `pfSense.home.arpa`.\n- OS: pfSense CE `2.7.2`.\n- Base system observed over SSH: FreeBSD `14.0-CURRENT`, amd64.\n\n## Interfaces\n\n| Interface | Description | Role | Address | MAC | Status |\n| --- | --- | --- | --- | --- | --- |\n| `re0` | `LANTECH` | `home-iot-lan` | `192.168.2.1/24` | `00:e0:4c:68:07:9f` | active, 1000baseT full-duplex |\n| `re1` | none | unused | none | `00:e0:4c:68:39:03` | no carrier |\n| `re2` | `LANMAIN` | `home-lan` | `192.168.1.1/24` | `00:e0:4c:68:35:ba` | active, 1000baseT full-duplex |\n| `re3` | `WAN` | WAN uplink | `172.32.2.78/24` | `70:85:c2:24:ee:4b` | active, 1000baseT full-duplex |\n\n## Routing\n\nObserved routes:\n\n- Default route: `172.32.2.1` through `re3`.\n- `192.168.1.0/24` is directly connected through `re2`.\n- `192.168.2.0/24` is directly connected through `re0`.\n- Host routes for `8.8.8.8` and `2.2.2.2` are present through `re3`.\n\n## Local Services\n\nObserved listening services:\n\n- SSH: `*:22`.\n- Web UI through nginx: `*:80`, `*:443`.\n- DHCPv4 through Kea: `192.168.1.1:67`, `192.168.2.1:67`.\n- DNS resolver through Unbound: `*:53`.\n- Unbound control: `127.0.0.1:953`.\n- Syslog: UDP `*:514`.\n- NTP: UDP `*:123`, including bindings on `192.168.1.1`, `192.168.2.1`, `172.32.2.78`, and `127.0.0.1`.\n\nResolver configuration:\n\n- `127.0.0.1`\n- `8.8.8.8`\n- `2.2.2.2`\n- Search domain: `home.arpa`\n\n## Local Network Topology\n\nThe home network currently consists of two local networks implemented through one custom router with multiple network interfaces.\n\nEach local network goes from the router into a switch and then is distributed through the home. The access layer includes wired TVs, PCs, servers, and Wi-Fi access points.\n\n### Home LAN\n\n- Inventory id: `home-lan`.\n- CIDR: `192.168.1.0/24`.\n- Gateway: `192.168.1.1`.\n- Router interface: `re2` / `LANMAIN`.\n- Main Wi-Fi SSID: `home`.\n- Wi-Fi mode: access points, not a separate routed Wi-Fi network.\n- Access points: 2 nodes.\n- Mesh mode: enabled for the main Wi-Fi nodes.\n\n### Home IoT LAN\n\n- Inventory id: `home-iot-lan`.\n- CIDR: `192.168.2.0/24`.\n- Gateway: `192.168.2.1`.\n- Router interface: `re0` / `LANTECH`.\n- Purpose: service network for smart-home and IoT devices.\n- Wi-Fi mode: access points.\n- Mesh mode: intentionally disabled.\n- IoT Wi-Fi nodes:\n - `home_iot_0`\n - `home_iot_1`\n - `home_iot_2`\n\n### Current And Planned Policy\n\nCurrent policy:\n\n- full access between `home-lan` and `home-iot-lan`;\n- IoT internet access is currently allowed.\n\nPossible future policy:\n\n- isolate the two networks from each other;\n- cut off the IoT network from the internet.\n\n## Dual-Homed Smart Home Server\n\nThe smart-home server is present in both networks:\n\n- `192.168.1.101` on `home-lan`;\n- `192.168.2.101` on `home-iot-lan`.\n\nFurther details still need to be documented: firewall rules, port forwards, VPN routes, DHCP static mappings, and DNS host overrides." + }, + "status": "applied", + "created_at": "2026-09-29T19:19:53Z", + "updated_at": "2026-09-29T19:19:55Z", + "applied_at": "2026-09-29T19:19:55Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}