ifnum is not recognized as valid param. Since it's unknown, I guess ntopng is replying with host statistics related to the currently active interface. Check hosts statistics against the active interface.
Simone On Mon, Mar 7, 2016 at 4:46 PM, Ajit Sarnaik <[email protected]> wrote: > Hello Simone, > > Here is the request, > > "http://localhost:6398/lua/host_get_json.lua?ifnum=4&host=172.25.3.130"; > > We do get the Tx stats, but Rx (response from server) is 0. > > Regards, > > Ajit > > On Mon, Mar 7, 2016 at 7:05 AM, Simone Mainardi <[email protected]> wrote: > >> Ajit, are you calling the http "host_get_json.lua" endpoint directly? >> Could you please post the full http request you make? >> >> simone >> >> On Mon, Mar 7, 2016 at 3:51 AM, Ajit Sarnaik <[email protected]> >> wrote: >> >>> Hello Folks, >>> >>> Just starting using ntop. We would like to capture network statistics >>> for bidirectional traffic and we are using "host_get_json.lua" script to >>> accomplish this. What we are noticing is that the Tx traffic stats are >>> appropriate, where as the Rx traffic stats are 0. We have done a tcpdump to >>> determine if the response are being received on the interface, and they are >>> coming in. Below is the snippet of he config file. >>> >>> # Specifies the network interface or collector endpoint to be >>> used by ntopng for network >>> # monitoring. On Unix you can specify both the interface name >>> (e.g. lo) or the numeric >>> # interface id as shown by ntopng -h. On Windows you must use the >>> interface number instead. >>> # Note that you can specify -i multiple times in order to >>> instruct ntopng to create multi‐ >>> # ple interfaces. >>> # >>> --interface eth0 >>> --interface eth1 >>> # >>> # -w|--http-port >>> # Sets the HTTP port of the embedded web server. >>> # >>> --http-port 6398 >>> # >>> # -m|--local-networks >>> # ntopng determines the ip addresses and netmasks for each active >>> interface. Any traffic on >>> # those networks is considered local. This parameter allows the >>> user to define additional >>> # networks and subnetworks whose traffic is also considered local >>> in ntopng reports. All >>> # other hosts are considered remote. If not specified the default >>> is set to 192.168.1.0/24. >>> # >>> # Commas separate multiple network values. Both netmask and >>> CIDR notation may be used, >>> # even mixed together, for instance " >>> 131.114.21.0/24,10.0.0.0/255.0.0.0". >>> # >>> --local-networks "172.25.1.0/24,172.25.2.0/24,172.25.3.128/25" >>> # >>> # -n|--dns-mode >>> # Sets the DNS address resolution mode: 0 - Decode DNS responses >>> and resolve only local >>> # (-m) numeric IPs 1 - Decode DNS responses and resolve all >>> numeric IPs 2 - Decode DNS >>> # responses and don't resolve numeric IPs 3 - Don't decode DNS >>> responses and don't resolve >>> # >>> -n=3 >>> >>> Have any of you seen this behavior. Would appreciate any help in this >>> regards. Any pointers to FAQs would also be helpful. >>> >>> Regards, >>> >>> -- >>> Ajit Sarnaik >>> >>> _______________________________________________ >>> Ntop mailing list >>> [email protected] >>> http://listgateway.unipi.it/mailman/listinfo/ntop >>> >> >> >> _______________________________________________ >> Ntop mailing list >> [email protected] >> http://listgateway.unipi.it/mailman/listinfo/ntop >> > > > > -- > Ajit Sarnaik > > _______________________________________________ > Ntop mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop >
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
