Original Summary

I built this because I was tired of manually maintaining Excel sheets and Visio diagrams for my homelab documentation.<p>The core idea is automated discovery via Nmap, but without sending plaintext network data to a hosted backend. It uses strict client-side Zero-Knowledge End-to-End Encryption.<p>The Architecture:<p>The Scanner: A lightweight Python agent running locally in a Docker container. It uses Nmap to scan the local subnet.<p>The Encryption: The payload is encrypted locally before it ever leaves the network. The backend (FastAPI&#x2F;PostgreSQL) only receives and stores encrypted blobs.<p>The Frontend: Decryption happens entirely client-side in the browser (Angular), rendering the topology using vis-network.<p>Technical Hurdles &amp; Limitations I&#x27;m currently facing:<p>Hostname Discovery is a nightmare: Across different vendors, devices handle broadcast differently (mDNS, NetBIOS, pure DNS). The agent catches what it can, but often falls back to raw IPs because reliable local resolution is incredibly inconsistent.<p>Physical Connections: While Nmap easily discovers the devices and open ports on the subnet, mapping the exact physical connections (which switch port goes where, device types, Wi-Fi details) still requires manual linking in the UI.<p>Links:<p>Live App: <a href="https:&#x2F;&#x2F;app.vnetmap.com" rel="nofollow">https:&#x2F;&#x2F;app.vnetmap.com</a><p>GitHub (Docs &amp; Agent Setup): <a href="https:&#x2F;&#x2F;github.com&#x2F;vNetMap&#x2F;vnetmap-issues" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vNetMap&#x2F;vnetmap-issues</a><p>I&#x27;m curious to hear how you handle automated discovery in your homelabs, especially regarding the hostname resolution issue, or if you spot any flaws in this E2E approach.

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/9/19 03:21:59