diff --git a/90-maintenance/discovery-observations/local-network-scan-2026-09-03.md b/90-maintenance/discovery-observations/local-network-scan-2026-09-03.md new file mode 100644 index 0000000..16f7608 --- /dev/null +++ b/90-maintenance/discovery-observations/local-network-scan-2026-09-03.md @@ -0,0 +1,39 @@ +--- +owner: gmikcon +status: active +last_reviewed: 2026-09-03 +review_interval: 30d +confidence: medium +source_of_truth: nmap-observed +--- + +# Local Network Scan 2026-09-03 + +Purpose of this scan: locate the owner's PC referenced as `gmikcon`. No host with that name was found; observations below record what was verified instead. + +## Method + +- `nmap -sn` sweeps of `192.168.1.0/24` (34 live hosts) and `192.168.2.0/24` (31 live hosts). +- `nbstat.nse` NetBIOS name query on every live host in both subnets: no NetBIOS names registered anywhere. +- mDNS lookups (`getent hosts *.local`, multicast dig): no results. +- rDNS via `nmap -sL`: only `pfSense.home.arpa` (`.1`), `smart-home-server.local` (`.75`), `panel.smarthome.arp` (`.101`), `navi` (`.168`, `.253`). +- OUI lookup for candidate MACs via macvendors API. +- nginx access log on `internal-proxy-vps` (`192.168.1.226`) for client-source correlation. + +## Key Findings + +- No host named `gmikcon` resolves via DNS, mDNS, NetBIOS, or rDNS, and no canonical inventory entry with that hostname exists. The name `gmikcon` appears in the knowledge base only as an owner tag. +- New versus the 2026-05-10 scan: `192.168.1.129` (MAC `74:56:3c:b4:cb:18`, GIGA-BYTE NIC — desktop-motherboard Ethernet). Open TCP: `22` (OpenSSH 10.3), `80` (nginx default page), `8000`, `8080` (empty HTTP responses). No Windows SMB/RDP ports. Best current candidate for the owner's desktop PC; not present in inventory. +- `192.168.1.146` (MAC `8c:a9:82:cd:6a:36`, Intel Corporate NIC) is a known SSH target in navi's `known_hosts` but was offline during this scan. Second candidate for a personal computer. +- Documented `gbook` candidates `192.168.1.75` and `192.168.1.76` were both offline; the laptop's current address is unknown. +- rDNS anomaly: `192.168.1.75` resolves to `smart-home-server.local`, while the smart-home server is documented at `192.168.1.101` (`panel.smarthome.arp`). Needs follow-up. +- The owner's live web session to `navi.gnexus.space` reaches the internal proxy from WAN IP `46.231.231.174` (home NAT). The LAN address of the client browser is not visible in proxy or uvicorn logs (no X-Forwarded-For logging). +- SSH to pfSense as `ai_agent_ro@192.168.1.1` failed with the keys available on navi; the owner-managed key is required for router-side ARP/DHCP-lease inspection. + +## Candidates For Follow-Up + +- Identify `192.168.1.129` via SSH (OpenSSH 10.3) once credentials are available, then promote to canonical inventory if it is the owner's PC. +- Confirm whether `192.168.1.146` is the owner's PC when it comes online. +- Resolve the `192.168.1.75` rDNS anomaly against the documented smart-home address `192.168.1.101`. + +No raw credentials are documented here.