I've added some new messages to the ntop startup log. Really early in the process
NOTE: device 0(eth0) DLT_ is 1, assuming mtu 1514, header 14 NOTE: device 1(eth1) DLT_ is 1, assuming mtu 1514, header 14 They show the value of the datalink variable and the derived values for mtu and header size. Other messages may appear: Device %d(%s) is loopback, treating as DLT_NULL AIX only - because of a broken libpcap - do we even have any AIX users? Is libpcap still broken?? Device %d(%s) is "t...", treating as DLT_IEEE802 (TokenRing) Device %d(%s) is loopback, treating as DLT_NULL Device %d(%s), treating as DLT_EN10MB (Ethernet) FreeBSD only - Device %d(%s) is "tun", treating as DLT_PPP Finally, there are warning messages if the values are out of bounds: WARNING: Device %d(%s) DLT_ value, %d, exceeds highest known value. Processing continues OK. Please report this to the ntop-dev list. WARNING: MTU value for DLT_ %d, is zero or unknown. Processing continues OK. Please report your MTU values (e.g. ifconfig) to the ntop-dev list NOTE: Header value for DLT_ %d, is zero. Processing continues OK - don't use the nfs plugin. Please report this to the ntop-dev list. If you get one of those, well, please do as it says... -----Burton _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
