Support multiple IPs and MACs per host and Docker container in database schema

[karam-ajaj]

Idea

Currently, the database schema for hosts and Docker containers assumes each entity has a single IP and MAC address. However, in real-world scenarios:

• Hosts and Docker containers can have multiple IPs (e.g., multiple network interfaces).
• Some IPs or MACs may be duplicated (e.g., bridged networks, aliases).

Proposal:

• Change the database schema to allow multiple IPs and MACs per host and per container.
• Allow tracking and displaying duplicated IPs.
• Update all scans, normalization, and UI components to handle multiple IPs/MACs per host/container.
• Ensure API endpoints and CSV exports are compatible.

Motivation

• More accurately represent real networks and modern Docker setups.
• Diagnose network issues and IP/MAC conflicts more effectively.
• Enable advanced filtering and grouping in the UI.

Implementation Outline

1. Database Changes
   • Change hosts and docker_hosts tables to allow multiple IPs and MACs per row (e.g., via a new table or array/blob column).
   • Add support for duplicated IPs/MACs.
2. Scanning Logic
   • Update scan routines to discover and store all IPs/MACs for each host/container.
3. UI Changes
   • Update Hosts Table and related components to display multiple IPs/MACs and highlight duplicates.
   • Improve filtering to handle multi-value fields.
4. API Changes
   • Update /hosts and related endpoints to return arrays of IPs/MACs.
   • Ensure backward compatibility for existing consumers.
5. Documentation
   • Document new schema, API changes, and usage in README.

---

This will be a significant change and may require updates across Go scanning logic, React UI, and database migration scripts.

---

Related idea: Deepscan with hardcoded ip network

---

Feel free to add design notes, database migration plans, or proposed schema sketches in comments below.