owner: gmikcon status: active last_reviewed: 2026-05-10 review_interval: 90d confidence: medium
The smart-home server is an Intel NUC mini PC that is present in both local networks and hosts the custom smart-home platform.
intel-nuc-shome.shome.mmcblk0, mounted at /home/shome/backups.System state observed 2026-05-10:
192.168.1.101.192.168.2.101.Interfaces:
enp3s0: 192.168.1.101/24, home-lan.enx98fc84e6a61f: 192.168.2.101/24, home-iot-lan.wlp2s0: up, IPv6 link-local only.br0: down.Default routes are currently present through both 192.168.1.1 and 192.168.2.1.
Observed during SSH inspection:
22, OpenSSH 9.6p1 Ubuntu.80, nginx 1.24.0 on Ubuntu.443, nginx 1.24.0 on Ubuntu.111.2049.127.0.0.1:3306.127.0.0.1:33060.5201.Running systemd services include:
nginx.servicephp8.3-fpm.servicemysql.servicenfs-mountd.servicerpcbind.servicehostapd.serviceiperf3.servicessh.servicenginx serves:
/home/shome/smart-home-server/serverpanel.smarthome.arp web client root: /home/shome/smart-home-server/webclientunix:/run/php/php8.3-fpm.sock/home/shome/ca/panel.crtThe deployed application repository is:
/home/shome/smart-home-serverhttps://git.gnexus.space/git/root/smart-home-server.gitmaster4ef1bfa (Fix resilient device state)The working tree was dirty during inspection:
server/ControlScripts/Common.phpserver/ControlScripts/Scopes/LightHubScope.phpwebclient/config.phpDo not overwrite or revert these files without explicit owner approval.
NFS export:
/home/shome/backups192.168.1.0/24rw, async, no_subtree_check, no_root_squash/dev/mmcblk0p1This host bridges the operational smart-home context across:
home-lan (192.168.1.0/24);home-iot-lan (192.168.2.0/24).The current policy allows full access between the two local networks. A future policy may isolate the IoT LAN from the home LAN and possibly deny IoT internet access.
No raw credentials are documented here.