Burton Strauss wrote:
What's in the log further back
Fri Jun 10 14:05:08 2005 Initializing ntop
Fri Jun 10 14:05:08 2005 No default device configured. Using dc0
Fri Jun 10 14:05:08 2005 NONBLOCK: pcap_setnonblock(), device 0, succeeded
Fri Jun 10 14:05:08 2005 **WARNING** NONBLOCK: cpu usage may be high -
see man page and FAQ
Fri Jun 10 14:05:08 2005 Checking dc0 for additional devices
Fri Jun 10 14:05:08 2005 Resetting traffic statistics for device dc0
Fri Jun 10 14:05:08 2005 DLT: Device 0 [dc0] is 1, mtu 1514, header 14
Also, what kind of device is tun0? If it's an artificial device, libpcap
may be capturing against the base - does tcpdump work??
tun0 is a software interface, in this case being used by the usermode
PPP daemon. tcpdump works fine against it. Also, dc0 and tun0 have
nothing to do with each other; the PPPoE link that tun0 is handling goes
over de0. dc0 is an internal LAN interface.
There is some special handing
#if defined(__FreeBSD__)
if(strncmp(myGlobals.device[deviceId].name, "tun", 3) == 0) {
myGlobals.device[deviceId].datalink = DLT_PPP;
traceEvent(CONST_TRACE_NOISY, "DLT: Device %d [%s] is \"tun\", treating
as DLT_PPP",
deviceId,
myGlobals.device[deviceId].name);
} else
Do you see that message?
No, I don't...in fact, ntop never mentions tun0 at all. It seems to be
totally ignoring the interface I specified on the command line.
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
