owner: gmikcon status: active last_reviewed: 2026-10-03 review_interval: 90d confidence: high
Central router and firewall for the local network.
https://192.168.1.1/ai_agent_ro@192.168.1.1:22, read-only access for documentation agents.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).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.sudo, no clog binary in PATH, no Match/ForceCommand block in sshd_config — the restriction is plain file permissions.journalctl | grep "state is now"), OpenVPN reconnect logs on tunnel endpoints, or the pfSense Web UI (owner).ai_agent_ro is csh; complex one-liners must be wrapped as sh -c '...' (nested quoting is fragile — build the command programmatically).home-lan and home-iot-lan.pfSense.home.arpa.2.7.2.14.0-CURRENT, amd64.| Interface | Description | Role | Address | MAC | Status |
|---|---|---|---|---|---|
re0 |
LANTECH |
home-iot-lan |
192.168.2.1/24 |
00:e0:4c:68:07:9f |
active, 1000baseT full-duplex |
re1 |
none | unused | none | 00:e0:4c:68:39:03 |
no carrier |
re2 |
LANMAIN |
home-lan |
192.168.1.1/24 |
00:e0:4c:68:35:ba |
active, 1000baseT full-duplex |
re3 |
WAN |
WAN uplink | 172.32.2.78/24 |
70:85:c2:24:ee:4b |
active, 1000baseT full-duplex |
Observed routes:
172.32.2.1 through re3.192.168.1.0/24 is directly connected through re2.192.168.2.0/24 is directly connected through re0.8.8.8.8 and 2.2.2.2 are present through re3.The WAN interface re3 (172.32.2.0/24) shares a flat, unfiltered L2 segment with other ISP clients — it is not an isolated point-to-point uplink.
Evidence from arp -a over SSH (ai_agent_ro):
re3 (including own address 172.32.2.78 and gateway 172.32.2.1 at d4:01:c3:6b:86:b9); roughly 160+ distinct neighbor MACs of other ISP clients.172.32.2.5 → 54:ef:33:4b:5a:3d, 172.32.2.46 → 20:32:33:ea:b3:5a, 172.32.2.104 → 54:ef:33:4b:5a:a3, 172.32.2.106 → 00:e0:4c:8d:6b:06, 172.32.2.141 → d4:da:21:1d:ba:f0, 172.32.2.195 → 48:8f:5a:3b:3c:32.A friend of the owner is on the same ISP and the same WAN L2 segment, enabling a direct low-latency peer link.
172.32.2.120, MAC 24:2f:d0:7e:96:d9 (TP-Link Archer C6, stock firmware; hardware version to be confirmed from the bottom sticker).192.168.0.0/24, gateway 192.168.0.1 (from his tracert to 8.8.8.8).ping 172.32.2.78; the log showed a wall of ICMP echo-requests from 172.32.2.120 to 172.32.2.78 blocked by the default deny rule (1000000103) every second.172.32.2.120 also get no replies (his router filters inbound ICMP) — inbound TCP to forwarded ports is NOT filtered by the ISP (verified: other segment neighbors answer on TCP ports).192.168.1.0/24 for bidirectional access.172.32.2.120/32.wg binary in base system, /boot/kernel/if_wg.ko module present, WireGuard built into pfSense 2.7.2 Web UI). Our WAN is DHCP (dhclient on re3) — both endpoints may change IP.24:2f:d0:7e:96:d9 is the stable identifier. The pfSense WAN DHCP lease file (/var/db/dhclient.leases.re3) is root-only readable through ai_agent_ro, so lease duration is unknown — assume the friend's lease can change at any time.172.32.2.78; the owner reads the pfSense firewall log (Status → System Logs → Firewall, filter ICMP) — the source IP of the ICMP wall is his new WAN address.nmap -sn 172.32.2.0/24 from a LAN host), then read arp -a on pfSense re3 and match the MAC prefix 24:2F:D0 (TP-Link OUI). Other TP-Link routers in the segment may share the prefix — verify candidates with the ping-trap from step 1.Observed listening services:
*:22.*:80, *:443.192.168.1.1:67, 192.168.2.1:67.*:53.127.0.0.1:953.*:514.*:123, including bindings on 192.168.1.1, 192.168.2.1, 172.32.2.78, and 127.0.0.1.Resolver configuration:
127.0.0.18.8.8.82.2.2.2home.arpaThe home network currently consists of two local networks implemented through one custom router with multiple network interfaces.
Each 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.
home-lan.192.168.1.0/24.192.168.1.1.re2 / LANMAIN.home.home-iot-lan.192.168.2.0/24.192.168.2.1.re0 / LANTECH.home_iot_0home_iot_1home_iot_2Current policy:
home-lan and home-iot-lan;Possible future policy:
The smart-home server is present in both networks:
192.168.1.101 on home-lan;192.168.2.101 on home-iot-lan.Further details still need to be documented: firewall rules, port forwards, VPN routes, DHCP static mappings, and DNS host overrides.