I am using ntop-01-11-08, and it is installed on an internal web cache (to watch how traffic is distributed internally) and on our firewall.
On the web cache, ntop resolves all of internal IP addresses almost instantly. There are sometimes a couple of addresses that can't be resolved because they don't have names, but that's not a problem. On the firewall, many of the internal IP addresses are not resolved. This bugs me. :-) The only difference I can think of between the two machines is that the firewall sees a lot more addresses that don't have domain names. Well, it probably sees a lot more sites, period. Are all addresses supposed to be resolved in a fairly short time? Is there something about the resolving process that if too many names are not resolveable that it gives up before resolving all of the names? Is the resolving process somehow lower priority? Does it lose track while trying to resolve addresses? Are the addresses being resolved but not being recorded or not being displayed? Is there some debugging information I can see about how the resolving is going? ---- Russell Mosemann, Ph.D. * Computing Services * Concordia University, Nebraska "It's mind over matter. If you don't have a mind, it doesn't matter." _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop
