You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For local hosts ntopng uses the IP address as key. This is wrong for local broadcast domain hosts as if there are hosts with dynamic address (e.g. DHCP) the IP address information does NOT represent the information of the IP when 'impersonated' by the MAC. The result is (for instance) that with DHCP hosts, the IP address graph is a mix of all hosts that had such IP assigned.
It is requested for hosts in the local broadcast domain to use as 'anchor' for historical information (i.e. alerts, graphs, and serialised information on redis) the MAC address and not the IP as it is today. Please note that for IPv6 a host can have multiple addresses. Furthermore the same host can have an IPv4 address, so using as 'anchor' just the MAC without other ancillary data might not be enough to identify the information we're looking for.
The text was updated successfully, but these errors were encountered:
For local hosts ntopng uses the IP address as key. This is wrong for local broadcast domain hosts as if there are hosts with dynamic address (e.g. DHCP) the IP address information does NOT represent the information of the IP when 'impersonated' by the MAC. The result is (for instance) that with DHCP hosts, the IP address graph is a mix of all hosts that had such IP assigned.
It is requested for hosts in the local broadcast domain to use as 'anchor' for historical information (i.e. alerts, graphs, and serialised information on redis) the MAC address and not the IP as it is today. Please note that for IPv6 a host can have multiple addresses. Furthermore the same host can have an IPv4 address, so using as 'anchor' just the MAC without other ancillary data might not be enough to identify the information we're looking for.
The text was updated successfully, but these errors were encountered: