---
owner: gmikcon
status: active
last_reviewed: 2026-05-10
review_interval: 30d
confidence: medium
source_of_truth: nmap-observed
---

# Local Network Scan 2026-05-10

This document records observed local network facts. These observations are not automatically canonical inventory records.

Scan scope:

- `192.168.1.0/24`

Scan mode:

- Host discovery: `nmap -sn 192.168.1.0/24`
- Service sample: `nmap -sV --version-light -T3 --top-ports 50 ...`

## Active Hosts

| Address | Name | Notes |
| --- | --- | --- |
| `192.168.1.1` | `pfSense.home.arpa` | Router/firewall. |
| `192.168.1.2` | unknown | Web UI on `80` and `8443`; likely network device or access point. |
| `192.168.1.3` | unknown | Web UI on `80` and `8443`; likely network device or access point. |
| `192.168.1.75` | local workstation | SSH, nginx, MariaDB. |
| `192.168.1.76` | possible `gbook` | Dynamic address; SSH, Apache/PHP, Ajenti. |
| `192.168.1.101` | `panel.smarthome.arp` | Smart-home server, SSH/nginx/rpcbind. |
| `192.168.1.102` | Klipper printer | Modified Creality Ender 2 V3 controller; SSH, Mainsail/nginx, Moonraker. |
| `192.168.1.130` | known server | HP/libvirt host. |
| `192.168.1.131` | unknown Ubuntu host | SSH/nginx/rpcbind. |
| `192.168.1.150` | unknown Ubuntu host | SSH/nginx/HTTPS. |
| `192.168.1.151` | unknown Ubuntu host | SSH/Apache. Upstream for `gnexus.space`. |
| `192.168.1.152` | unknown Ubuntu host | SSH/Apache/rpcbind. Upstream for `cloud.gnexus.space`. |
| `192.168.1.153` | unknown Ubuntu host | SSH/rpcbind. Upstream for `jellyfin.gnexus.space:8096`. |
| `192.168.1.154` | unknown Ubuntu host | SSH/rpcbind. Upstream for `transmission.gnexus.space:3000`. |
| `192.168.1.155` | unknown Ubuntu host | SSH/Apache. Available upstream for `anicusi.gnexus.space`. |
| `192.168.1.156` | unknown Ubuntu host | SSH/Jetty. Upstream for `git.gnexus.space`. |
| `192.168.1.157` | unknown Ubuntu host | SSH/Apache/rpcbind. Upstream for `files.gnexus.space`. |
| `192.168.1.159` | unknown Ubuntu host | SSH/nginx. |
| `192.168.1.167` | unknown Ubuntu host | SSH/nginx. Upstream for `auth.gnexus.space` and available `lytvak.gnexus.space`. |
| `192.168.1.168` | unknown Ubuntu host | SSH/nginx/Uvicorn/Gunicorn. Upstream for `navi.gnexus.space:8000`. |
| `192.168.1.169` | unknown Ubuntu host | SSH/rpcbind. |
| `192.168.1.174` | unknown Ubuntu host | SSH/nginx/Uvicorn/Gunicorn. |
| `192.168.1.191` | unknown Ubuntu host | SSH only in sampled ports. |
| `192.168.1.226` | internal proxy VPS | SSH/nginx. |
| `192.168.1.245` | likely dynamic/IoT | `49152/tcp` tcpwrapped. |
| `192.168.1.251` | likely dynamic/IoT | No open top-50 TCP ports in sample. |

## Notes

- TVs, phones, and other household devices should not be promoted to canonical inventory unless they become infrastructure-relevant.
- Addresses on dynamic household devices may change and should be treated as observations only.
- Unknown Ubuntu hosts are good candidates for SSH-based identification before being added to `hosts.yml`.
- `192.168.1.102` was promoted to canonical inventory as `klipper-3d-printer`.
- `192.168.1.76` was promoted to canonical inventory as dynamic host `gbook`.

## gbook Discovery

The Arch Linux laptop `gbook` does not have a static IP address.

Current observed candidate on `home-lan`:

- Address: `192.168.1.76`.
- SSH on TCP `22`, OpenSSH 10.2.
- HTTP on TCP `80`, Apache httpd 2.4.66 with PHP 8.5.4.
- Ajenti on TCP `5000`.

pfSense ARP also showed the same MAC on `192.168.2.49`, but that IoT-network presence needs confirmation before treating it as a normal operating address.

## Printer Discovery

The Klipper printer was found at `192.168.1.102` on `home-lan`.

Observed services:

- SSH on TCP `22`, OpenSSH 9.2p1 Debian.
- Mainsail UI on TCP `80`, nginx 1.22.1.
- Moonraker API on TCP `7125`, Tornado 6.5.4.

Read-only Moonraker `/server/info` response confirmed:

- `klippy_connected`: `true`.
- `klippy_state`: `ready`.
- Moonraker version: `v0.10.0-9-g3fbe6ee`.
- API version: `1.5.0`.

## pfSense ARP Snapshot

Observed from `pfSense.home.arpa` over read-only SSH. These are observations, not canonical inventory records.

Home LAN on `re2`:

- `192.168.1.2`
- `192.168.1.3`
- `192.168.1.75`
- `192.168.1.76`
- `192.168.1.102`
- `192.168.1.130`
- `192.168.1.150`
- `192.168.1.152`
- `192.168.1.154`
- `192.168.1.168`
- `192.168.1.191`
- `192.168.1.202`
- `192.168.1.204`
- `192.168.1.226`
- `192.168.1.245`
- `192.168.1.251`

IoT LAN on `re0`:

- `192.168.2.17`
- `192.168.2.21`
- `192.168.2.32`
- `192.168.2.43`
- `192.168.2.50`
- `192.168.2.55`
- `192.168.2.57`
- `192.168.2.66`
- `192.168.2.71`
- `192.168.2.75`
- `192.168.2.80`
- `192.168.2.101`
- `192.168.2.110`
- `192.168.2.115`
- `192.168.2.116`
- `192.168.2.118`
- `192.168.2.124`
- `192.168.2.128`
- `192.168.2.133`

## Candidates For Follow-Up

- `192.168.1.131`
- `192.168.1.150`
- `192.168.1.159`
- `192.168.1.169`
- `192.168.1.174`
- `192.168.1.191`

No raw credentials are documented here.