(1) Why 64 ... Is it that it's big enough for your renamed network cards? Or is that the actual size limit on A network card name?
(2) You were going to send me the updated instructions and diffs, with an eye to getting this stuff into 3.2, but you are running out of time. I want to create rc1 in the next 24 hrs. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Georger Araujo Sent: Tuesday, August 16, 2005 11:36 AM To: [email protected]; [email protected] Subject: Re: [Ntop-dev] PR_TWTATGB - no Historical Protocol View nor NetworkLoad graphs for LAN cards on Windows Problem solved. Just had to change rrdInterface[32] to rrdInterface[64] in line 2066 of plugins/rrdplugin.c and recompile. If anyone is interested I made the mingw-compatible source available at http://savefile.com/projects.php?pid=420840 - it's up-to-date with CVS and running rock solid on my Windows XP Pro SP2 notebook for 1h20mins now. Now I think I'll take a look at arbitrary graphs - ntop CVS still goes down in flames with those. Regards, Georger --- Georger Araujo <[EMAIL PROTECTED]> escreveu: > 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_1 > > The 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 _______________________________________________________ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
