Markus -- I think I'm on to something.
Try deleting the cache (dnsCache.db) before the start of the run. While it won't fix the problem it may hide it. Let me know. I think I know the pattern to look for. If you build with CMPFCTN_DEBUG (or better yet, just make the single case in _setResolvedName() active), you may see this in the log: CMPFCTN_DEBUG: setResolvedName(0x0836e5f8) 0 -> 29 c-67-166-195-111.client.comcast.net - address.c(69) ... CMPFCTN_DEBUG: setResolvedName(0x08442008) 0 -> 9 ADAPTEC INCORPORATED:EF:02:D0 - hash.c(1182) CMPFCTN_DEBUG: setResolvedName(0x08442008) 9 adaptec incorporated:ef:02:d0 -> 19 67.166.195.111 - pbuf.c(3241) It's seeing the IP and resolving it from the cache, then building a separate record when it sees the MAC address (fair enough, it doesn't know the IP yet), followed by an IP record when it does learn the IP. Now you have two records, not one. Eventually the 2nd gets name resolved (29) and you have two hosts. For a real solution, either we need to add the MAC to the cache so the initial record is populated, or we need to figure out how to merge them on the 9->19 transition. Neither is very clean - I'm still looking into it. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Burton M. Strauss III > Sent: Sunday, February 29, 2004 2:52 PM > To: [EMAIL PROTECTED] > Subject: RE: [Ntop-dev] Duplicated name entries in the eth0 host lists > (orig. from eth0 and NerFlow-Device) > <snip /> _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
