Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAC and IP historical information are mixed #2369

Closed
lucaderi opened this issue Feb 13, 2019 · 5 comments
Closed

MAC and IP historical information are mixed #2369

lucaderi opened this issue Feb 13, 2019 · 5 comments

Comments

@lucaderi
Copy link
Member

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.

@lucaderi
Copy link
Member Author

Please note that this ticket depends on #2390.

@emanuele-f
Copy link
Contributor

Initial work for host statistics and graphs: dd37caf

@emanuele-f
Copy link
Contributor

With 387543f top senders and receivers are now calculated with the tskey as identifier

@emanuele-f
Copy link
Contributor

After further testing, we need to document this and then the issue could be closed

@emanuele-f
Copy link
Contributor

Documented in 0f2f6a7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants