Hi all, I dug deeper into this problem and I think I
found a clue about its cause. I have two network
adapters: \Device\NPF_GenericDialupAdapter Generic
dialup adapter_0, and
\Device\NPF_{0D3DE3E0-B660-4419-8E4B-AAB87EF7D6A1}
Broadcom NetXtreme Gigabit Ethernet Driver_1The first is my modem. The second is my NIC. When I run ntop /c -i 0,1 -M -t 6 --no-fc --ipv4 --skip-version-check ntop creates separate subdirectories for each of my network interfaces under C:\MinGW\ntop3.1\ntop\rrd\interfaces: Generic dialup adapter_0 and Broadcom NetXtreme Gigabit Ethernet Driver_1. As described in the bug report below and in graphs.zip available at http://savefile.com/projects.php?pid=420840, my modem has per-protocol graphs and network load working fine, whereas my NIC does not. I conclude the program logic is 100% correct, so I must investigate where my NIC differs from my NIC: Its name is longer. The length of "Broadcom NetXtreme Gigabit Ethernet Driver_1" is 44 characters; the length of "Generic dialup adapter_0" is 24 chars. So I fired up File Monitor from SysInternals (it's free, get it at http://www.sysinternals.com/Utilities/Filemon.html) and saw that ntop.exe ntop manages to open C:\MinGW\ntop3.1\ntop\rrd\interfaces\Generic dialup adapter_0 with no problems at all, but does NOT open C:\MinGW\ntop3.1\ntop\rrd\interfaces\Broadcom NetXtreme Gigabit Ethe\ - and that's understandable because it does not exist. It should try to open C:\MinGW\ntop3.1\ntop\rrd\interfaces\Broadcom NetXtreme Gigabit Ethernet Driver_1, which exists and has several RRD files in it. Pay attention that the length of "Broadcom NetXtreme Gigabit Ethe\" is 32 characters - I believe that somewere in the code ntop only allows an interface name to have up to 32 characters in its name. Fine on Linux, where we have short names like eth0, but not on Windows. I looked at the code, but there are MANY MANY places using [32] arrays, and I couldn't really figure it out. So I report the clue here, in the hope that I'm right and this is root cause of the problem. I'll get the chance and report we're missing the EMC and JNI icons in http://localhost:3000/textinfo.html, too. Sorry for the long text, I'm just trying to be comprehensive. Regards, Georger --- Georger Araujo <[EMAIL PROTECTED]> escreveu: > n t o p v e r s i o n '3.1' p r o b l e m r e > p > o r t > > From: Georger Araujo________________ > > EMail: georger_br @t yahoo dot com dot br_______ > > Date: 08/09/05 17:35:52 > > Problem Report Id: PR_TWTATGB > > ---------------------------------------------------------------------------- > Summary > > no Historical Protocol View nor Network Load graphs > for LAN cards on Windows > Network: > Network Interface 0 > \Device\NPF_GenericDialupAdapter Generic dialup > adapter_0 > Network Interface 1 > \Device\NPF_{0D3DE3E0-B660-4419-8E4B-AAB87EF7D6A1} > Broadcom NetXtreme Gigabit Ethernet Driver_1 ---------------------------------------------------------------------------- > Problem Description > > ntop doesn't show Historical Protocol View graphs on > Global TCP/UDP Protocol Distribution > screen for LAN cards on Windows, nor Network Load. > Modem works fine. > Get the PDFs from file graphs.zip on > http://savefile.com/projects.php?pid=420840/projects.php?pid=420840 > to see exactly what is happening. __________________________________________________ Converse com seus amigos em tempo real com o Yahoo! Messenger http://br.download.yahoo.com/messenger/ _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
