Newer
Older
gnexus-book / 40-inventory / hardware.yml
---
- id: hp-proliant-dl380-g6
  name: HP ProLiant DL380 G6
  type: physical-server
  status: active
  location: home
  hardware_role:
  - virtualization-host
  os: Ubuntu 22.04.4 LTS
  kernel: 5.15.0-176-generic
  management:
    cockpit:
      url: https://192.168.1.130:9090/system
      version: 310.1-1~bpo22.04.1
  virtualization_stack:
    type: kvm-libvirt
    connection: qemu:///system
    libvirt_version: 8.0.0
    management_tools:
    - virsh
    - cockpit-machines
  network_interfaces: []
  runs_hosts:
  - ovpn
  - gitbucket
  - alex
  - anicusi
  - navi
  - mctl
  - jellyfin
  - gnexus-home
  - nextcloud
  - ovpn_reserv
  - home
  - transmission
  - files
  - gnauth
  - cats
  - fdroid
  - kitan
  - m1connect
  - mail-server
  - mine
  - radio
  - shome
  - topics
  - unmanic
  - vec_search
  - yt
  docs: ../10-systems/hardware/hp-proliant-dl380-g6.md
  last_reviewed: 2026-05-09
  source_of_truth: ssh-libvirt
- id: pfsense-router
  name: pfSense Router
  type: router-firewall
  status: active
  location: home
  hardware_role:
  - router
  - firewall
  - local-network-edge
  - dhcp-server
  - dns-resolver
  - ntp-server
  os: pfSense CE 2.7.2
  kernel: FreeBSD 14.0-CURRENT
  management:
    web:
      url: https://192.168.1.1/
    ssh:
      host: 192.168.1.1
      port: 22
      user: ai_agent_ro
      access: read-only
      auth: ssh-key
      credential_reference: owner-managed
  network_interfaces:
  - name: re0
    description: LANTECH
    role: home-iot-lan
    mac: 00:e0:4c:68:07:9f
    ipv4: 192.168.2.1/24
    status: active
    media: 1000baseT full-duplex
  - name: re1
    role: unused
    mac: 00:e0:4c:68:39:03
    status: no-carrier
    media: 10baseT half-duplex
  - name: re2
    description: LANMAIN
    role: home-lan
    mac: 00:e0:4c:68:35:ba
    ipv4: 192.168.1.1/24
    status: active
    media: 1000baseT full-duplex
  - name: re3
    description: WAN
    role: wan-uplink
    mac: 70:85:c2:24:ee:4b
    ipv4: 172.32.2.78/24
    status: active
    media: 1000baseT full-duplex
  runs_hosts: []
  docs: ../10-systems/networks/pfsense-router.md
  last_reviewed: 2026-05-10
  source_of_truth: ssh-pfsense
- id: klipper-3d-printer
  name: Modified Creality Ender 2 V3
  type: 3d-printer
  status: active
  location: home
  vendor: Creality
  base_model: Ender 2 V3
  modification_level: deep
  hardware_role:
  - fabrication-device
  - network-device
  controller:
    type: raspberry-pi
    firmware_stack: Klipper
    web_ui: Mainsail
    api: Moonraker
    moonraker_version: v0.10.0-9-g3fbe6ee
    moonraker_api_version: 1.5.0
    klippy_state: ready
  network_interfaces:
  - network: home-lan
    ipv4: 192.168.1.102
    observed_ports:
    - 22
    - 80
    - 7125
  runs_hosts: []
  docs: ../10-systems/hardware/3d-printers.md
  last_reviewed: 2026-05-10
  source_of_truth: owner-described-and-network-observed
- id: bambulab-a1-3d-printer
  name: Bambu Lab A1
  type: 3d-printer
  status: active
  location: home
  vendor: Bambu Lab
  model: A1
  hardware_role:
  - fabrication-device
  - network-device
  access_model:
    ssh: not-expected
    local_control: Bambu LAN access code / Bambu Studio ecosystem
    notes: Treat as a closed appliance unless local endpoints are explicitly discovered.
  network_interfaces: []
  runs_hosts: []
  docs: ../10-systems/hardware/3d-printers.md
  last_reviewed: 2026-05-10
  source_of_truth: owner-described
- id: intel-nuc-shome
  name: Intel NUC Smart Home Server
  type: mini-pc
  status: active
  location: home
  vendor: Intel Corporation
  model: NUC6CAYH
  firmware_version: AYAPLCEL.86A.0043.2017.1123.1559
  hardware_role:
  - smart-home-controller
  - dual-homed-network-host
  - nfs-backup-target
  os: Ubuntu 24.04.3 LTS
  kernel: 6.8.0-110-generic
  resources:
    memory: 3.7GiB
    root_disk: 111.8GB SATA disk with LVM root volume
    backup_media: 58GB mmcblk0 mounted at /home/shome/backups
  network_interfaces:
  - name: enp3s0
    role: home-lan
    ipv4: 192.168.1.101/24
    status: active
  - name: enx98fc84e6a61f
    role: home-iot-lan
    ipv4: 192.168.2.101/24
    status: active
  - name: wlp2s0
    role: wifi
    ipv4: none
    status: active
  - name: br0
    role: bridge
    status: down
  runs_hosts:
  - smart-home-server
  docs: ../10-systems/servers/smart-home-server.md
  last_reviewed: 2026-05-10
  source_of_truth: ssh-host
- id: s10e-navi-node
  addresses:
    home-lan:
    - 192.168.1.22
  docs: ../10-systems/hardware/s10e-navi-node.md
  environment: home
  hardware_role:
  - android-execution-node
  - network-device
  - navi-capability
  last_reviewed: '2026-09-29'
  location: home
  model: SM-G970F (beyond0lte)
  name: Samsung Galaxy S10e — Navi Android node
  os: Android 12 (SDK 31, One UI)
  runs_hosts: []
  serial: RF8MA0TYJMF
  source_of_truth: adb-verified
  status: active
  type: smartphone
  vendor: Samsung
  notes: '2026-10-07: на S10e зарегистрирован собственный Telegram-аккаунт Navi (tg_user_id
    8781031814, phone 380939126548, username @navi_gnexus, premium). Управление через
    tgclient MCP account_id=2. SMS-канал проверен: termux-sms-send работает (SEND_SMS
    выдан com.termux.api), чтение входящих — adb content query --uri content://sms/inbox
    (строки не отсортированы по дате). Username выставлен через ADBKeyboard (ADB_INPUT_B64)
    в настройках приложения.'