-
Notifications
You must be signed in to change notification settings - Fork 673
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
NTOPNG detects only drops on eth1 #159
Comments
Looks like an old ntopng. Please update first and if not working please specify how you started ntopng |
Unfortunately, updating to "2.0.150911" didn't help. -G=/var/tmp/ntopng.pid #save messages into the system log #sets the directory that ntop runs from #--data-dir=/var/tmp/ntopng #the amount and severity of messages that ntop will put out #limit ntop to listening on a specific interface and port #disables "phone home" behavior #Set the protocol list (name and ports to be monitored) #Interface(s) that ntop will capture on (default: eth0) --no-interface-merge --dns-mode=1 #Sets program to run as a daemon -e #verbose #0 - No aggregations (default) #enable historical data -m=10.163.130.0/24 |
I can't follow you. In this example you are capturing from eth1, so I do not understand what is the problem with eth0 |
Please reopen the bug if you can reproduce it |
I need some help to get to the source of this issue:
NTOPNG detects only drops on eth1 but traffic on eth0 is being recognized, as well as the tcpdump file from eth1 ().
Strange, isn't it? What can cause drops to occur?
System is RHEL6 on VMWare:
{
"stats_bytes":0,
"flows":0,
"networkinterface":"eth1",
"version_ndpi":"1.6.0-dev-66-12f89ff",
"gathering":"pcap",
"uptime":684,
"aggregations":0,
"kernel_ver":"2.6.32-573.1.1.el6.x86_64",
"installdir":"/usr/share/ntopng",
"version_ntop":"2.0.150611 ",
"workingdir":"/var/tmp/ntopng",
"packets":0,
"drops":48868
}
The text was updated successfully, but these errors were encountered: