Hello.

I checked out the CVS-version of ntop at ~22:00 (GMT +1) on 13/5, and compiled it this 
morning. The inability to view active TCP-sessions via NetFlow in ntop 3.0 is now 
fixed, but another rather irritating bug is... bugging me.

The problem is name resolution. While ntop 3.0 had no problems with resolving, 
CVS-ntop appears to be unable to resolve IPs. It can however sniff what hostnames 
other applications on the same machine is talking to and use for itself. If I for 
example ping a hostname, ntop knows this and uses the info.
If i look under the About->Configuration tab and scroll down to the DNS info, I (at 
the moment) see the following:

DNS Packets Sniffed: 59303
DNS Packets Processed: 29318
Stored in cache (Including aliases): 29318

...

DNS resolution attempts: 264
...Success:Resolved: 0
...Failed: 264
DNS lookups stored in cache: 234
Host addresses kept numeric: 264

My Ntop currently keeps an eye on 2340 hosts, of which 8 are resolved because I've at 
some point had contact with them via some other application. I also have an nBox 
running with the ntop 3.050 that came with it, and it runs perfectly.

Niklas Berggren
Volvo IT
Sk�vde, Sweden.
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to