Thank you, Mathieu, please submit a pull request and we'll be happy to consider it for inclusion in the main dev branch
simone On Wed, Jul 13, 2016 at 5:27 PM, Mathieu Fourcroy < mathieu.fourc...@gmail.com> wrote: > Hello and thank you for your answer, > > I will contribute for sure. I have modified and added some features and I > would gladly share them if it can be useful. Github is a best place for > such things. > > 2016-07-13 10:28 GMT+02:00 Simone Mainardi <maina...@ntop.org>: > >> Mathieu, >> >> You already asked a similar question some time ago in the same mailing >> list. The behaviors you described are consistent with the present >> implementation. If you would like to handle dynamic IP-MAC associations, >> then please feel free to post a feature request on github and we'll try and >> accomodate it. Alternatively, if you would like to contribute with some >> code, that would be awesome. >> >> Thank you, >> Simone >> >> On Tue, Jul 12, 2016 at 10:28 PM, Mathieu Fourcroy < >> mathieu.fourc...@gmail.com> wrote: >> >>> Hello, >>> >>> I am just wondering how ntopng handle dynamic IP addresses modification. >>> So I test with two computers. I do the following: >>> - Set 192.168.1.1 on computer A >>> > ntopng associate computer A with IP 192.168.1.1 >>> - Set 192.168.1.2 on computer A >>> > ntopng associate computer A with IP 192.168.1.2 so that there is now >>> two entries for the same computer >>> - Set 192.168.1.1 on computer B >>> > ntopng do not associate computer B with IP 192.168.1.1. Instead, it >>> keeps thinking that it is computer A and continue monitoring traffic as if >>> it comes from/to computer A. >>> >>> Also when ntopng restore a host it do not check for its MAC address but >>> only for its IP address. So I set 192.168.1.1 on computer A then shutdown >>> ntopng and let it dump the redis data. Then I set 192.168.1.1 on computer B >>> and start ntopng again, it sees computer B with IP 192.168.1.1 and restore >>> the stats from redis wich belongs to computer A. >>> >>> So my question is: is this a desired features ? Is there a plan to >>> modify this behavior (I am actually planing to change it) ? >>> >>> Thank you, >>> Mathieu >>> >>> _______________________________________________ >>> Ntop mailing list >>> Ntop@listgateway.unipi.it >>> http://listgateway.unipi.it/mailman/listinfo/ntop >>> >> >> >> _______________________________________________ >> Ntop mailing list >> Ntop@listgateway.unipi.it >> http://listgateway.unipi.it/mailman/listinfo/ntop >> > > > _______________________________________________ > Ntop mailing list > Ntop@listgateway.unipi.it > http://listgateway.unipi.it/mailman/listinfo/ntop >
_______________________________________________ Ntop mailing list Ntop@listgateway.unipi.it http://listgateway.unipi.it/mailman/listinfo/ntop
