Kaiser, Thanks for reporting. There was an issue with a parameter passed in that page. Everything is fixed now.
Simone > On 1 Jun 2020, at 10:07, Kaiser Cheng <kai...@gentrice.net> wrote: > > Dear sir, > > In Ntopng, we could have flow output via host assignment, for example, we > hope to see the host = 192.168.3.17 > > http://192.168.135.42:60080/lua/host_details.lua?host=192.168.3.17&flow_status=alerted&page=flows# > > In the output flows, it contains the given IP, but it also contains the wrong > IP peers. How could we fix it? > > One of mismatch flow from the query above with a given host=192.168.3.17: > Flow Peers [ Client / Server ] 192.168.141.66:35658 [ > 10:7B:44:92:73:E8 ] 192.168.141.61:9300 [ 00:0C:29:0B:7A:F3 ] > > System:ntopng Enterprise M Edition v.4.1.200601 > > Br, > Kaiser > _______________________________________________ > 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
