From netramet-owner Wed Oct 7 12:58:22 1998 Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id MAA20758 for netramet-outgoing; Wed, 7 Oct 1998 12:55:58 +1300 (NZDT) Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79]) by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with SMTP id MAA20750 for ; Wed, 7 Oct 1998 12:55:53 +1300 (NZDT) From: Nevil Brownlee To: netramet@auckland.ac.nz Subject: Re: NeMaC and write community Message-ID: Date: Wed, 7 Oct 1998 12:56:37 +1300 (New Zealand Daylight Time) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1.4 Build (40) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: netramet-owner@auckland.ac.nz Precedence: bulk Hello Nicolai: > ==[Meter - runs OK]== > bash-2.01$ sudo ./NeTraMet -m 2000 -r read -w write > NeTraMet: Network Meter v4.2 > Running on guerilla, interface eth0 > > ==[Manager - cannot write to meter]== > bash-2.01$ ./NeMaC -m 2000 -v guerilla write > Using MIB file: mib.txt > 12:52:58 Mon 5 Oct 1998 -- guerilla: NeTraMet: Network Meter v4.2 > Up 0:00:00 (since 12:52:58 Mon 5 Oct 1998) > Community write doesn't have write access to meter guerilla! > Collections won't trigger recovery of idle flows <<< The write community name is a write-access password for an SNMP agent, in this case the NeTraMet meter. You've found an interesting bug in NeMaC 4.2. Using your command lines above, I get the same result as you. If I change the NeMaC line to ./NeMaC -m 2000 -v -r rules.nifty guerilla write ^^^^^^^^^^^^^^ it works just fine. Seems that NeMaC 4.2 won't work properly if you don't specify a rule file for it. I'll have a closer look and make it give a sensible error message. Thanks, Nevil +---------------------------------------------------------------------+ | Nevil Brownlee Director, Technology Development | | Phone: +64 9 373 7599 x8941 ITSS, The University of Auckland | | FAX: +64 9 373 7021 Private Bag 92019, Auckland, New Zealand | +---------------------------------------------------------------------P From netramet-owner Thu Oct 29 13:47:52 1998 Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id NAA03184 for netramet-outgoing; Thu, 29 Oct 1998 13:43:06 +1300 (NZDT) Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79]) by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with SMTP id NAA03172; Thu, 29 Oct 1998 13:43:01 +1300 (NZDT) From: Nevil Brownlee To: Philip Smith Cc: netramet@auckland.ac.nz Subject: Re: NeTraMet 4.2.1 build In-Reply-To: <199810282359.PAA14251@mailman.cisco.com> Message-ID: Date: Thu, 29 Oct 1998 13:50:22 +1300 (New Zealand Daylight Time) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1.4 Build (40) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: netramet-owner@auckland.ac.nz Precedence: bulk Hello Philip: > I'm trying to build NeTraMet 4.2.1 and the build is failing with this message: > > cd apps; make > make[1]: Entering directory > `/home/local/src/NeTraMet/NeTraMet421/autoconf/apps' > gcc -o snmptest snmptest.o -lresolv -lnsl -lm -L/usr/local/lib > ../snmplib/libsnmp.a > snmptest.o: In function `main': > /home/local/src/NeTraMet/NeTraMet421/autoconf/apps/../src/apps/snmptest.c:20 > 6: the `gets' function is dangerous and should not be used. > ../snmplib/libsnmp.a(mib.o): In function `init_mib': > /home/local/src/NeTraMet/NeTraMet421/autoconf/snmplib/../src/snmplib/mib.c:6 > 00: undefined reference to `log_msg' > > Release 4.2 builds fine, and as far as I can see, the main difference > between src/snmplib/mib.c (and other programmes in snmplib) in 4.2 and > 4.2.1 is that the function fprintf has been replaced with log_msg. > > Others may have run into this one too... Yes, several people have reported this problem, but thanks very much for the bug report. I bungled when making the 4.2.1 distribution file, in that although I changed everything in the snmplib, meter and manager directories to use log_msg to report errors, I forgot to do the same for the apps directory. I've just (today) put a new distribution file into the beta-versions subdirectory of the ftp site: NeTraMet43b1.tar.gz This fixes the above problem, and also correctly fixes the memory leak problem first noticed in 4.2. As well, it has a reorganised directory structure, and a much simpler install procedure - more like ordinary GNU applications. 4.3b1 is an early beta for the 4.3 version, which of course means I haven't yet updated the documentation! Have a look at the README and INSTALL files (as well as the doc/NeTraMet/version.history file) before you try to install it. As usual, I'd appreciate any bug reports, comments or suggestions. Cheers, Nevil +---------------------------------------------------------------------+ | Nevil Brownlee Director, Technology Development | | Phone: +64 9 373 7599 x8941 ITSS, The University of Auckland | | FAX: +64 9 373 7021 Private Bag 92019, Auckland, New Zealand | +---------------------------------------------------------------------P From netramet-owner Thu Oct 29 14:07:00 1998 Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id OAA06189 for netramet-outgoing; Thu, 29 Oct 1998 14:06:37 +1300 (NZDT) Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79]) by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with SMTP id OAA06180 for ; Thu, 29 Oct 1998 14:06:34 +1300 (NZDT) From: Nevil Brownlee To: netramet@auckland.ac.nz Subject: fwd: Re: NeTraMet 4.2.1 build Message-ID: Date: Thu, 29 Oct 1998 14:13:55 +1300 (New Zealand Daylight Time) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1.4 Build (40) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: netramet-owner@auckland.ac.nz Precedence: bulk --- Begin Forwarded Message --- Date: Thu, 29 Oct 1998 13:50:22 +1300 (New Zealand Daylight Time) From: Nevil Brownlee Subject: Re: NeTraMet 4.2.1 build To: Philip Smith Cc: netramet@auckland Hello Philip: > I'm trying to build NeTraMet 4.2.1 and the build is failing with this message: > > cd apps; make > make[1]: Entering directory > `/home/local/src/NeTraMet/NeTraMet421/autoconf/apps' > gcc -o snmptest snmptest.o -lresolv -lnsl -lm -L/usr/local/lib > ../snmplib/libsnmp.a > snmptest.o: In function `main': > /home/local/src/NeTraMet/NeTraMet421/autoconf/apps/../src/apps/snmptest.c:20 > 6: the `gets' function is dangerous and should not be used. > ../snmplib/libsnmp.a(mib.o): In function `init_mib': > /home/local/src/NeTraMet/NeTraMet421/autoconf/snmplib/../src/snmplib/mib.c:6 > 00: undefined reference to `log_msg' > > Release 4.2 builds fine, and as far as I can see, the main difference > between src/snmplib/mib.c (and other programmes in snmplib) in 4.2 and > 4.2.1 is that the function fprintf has been replaced with log_msg. > > Others may have run into this one too... Yes, several people have reported this problem, but thanks very much for the bug report. I bungled when making the 4.2.1 distribution file, in that although I changed everything in the snmplib, meter and manager directories to use log_msg to report errors, I forgot to do the same for the apps directory. I've just (today) put a new distribution file into the beta-versions subdirectory of the ftp site: NeTraMet43b1.tar.gz This fixes the above problem, and also correctly fixes the memory leak problem first noticed in 4.2. As well, it has a reorganised directory structure, and a much simpler install procedure - more like ordinary GNU applications. 4.3b1 is an early beta for the 4.3 version, which of course means I haven't yet updated the documentation! Have a look at the README and INSTALL files (as well as the doc/NeTraMet/version.history file) before you try to install it. As usual, I'd appreciate any bug reports, comments or suggestions. Cheers, Nevil +---------------------------------------------------------------------+ | Nevil Brownlee Director, Technology Development | | Phone: +64 9 373 7599 x8941 ITSS, The University of Auckland | | FAX: +64 9 373 7021 Private Bag 92019, Auckland, New Zealand | +---------------------------------------------------------------------P --- End Forwarded Message --- +---------------------------------------------------------------------+ | Nevil Brownlee Director, Technology Development | | Phone: +64 9 373 7599 x8941 ITSS, The University of Auckland | | FAX: +64 9 373 7021 Private Bag 92019, Auckland, New Zealand | +---------------------------------------------------------------------P From netramet-owner Fri Oct 30 14:27:59 1998 Received: by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) id OAA06424 for netramet-outgoing; Fri, 30 Oct 1998 14:23:15 +1300 (NZDT) Received: from n.browlee5.itss.auckland.ac.nz (n.brownlee5.itss.auckland.ac.nz [130.216.4.79]) by mailhost.auckland.ac.nz (8.9.1/8.9.1/8.9.1-ua) with SMTP id OAA06410 for ; Fri, 30 Oct 1998 14:23:07 +1300 (NZDT) From: Nevil Brownlee To: netramet@auckland.ac.nz Subject: Packet loss on FreeBSD meters using BPF Message-ID: Date: Fri, 30 Oct 1998 14:30:47 +1300 (New Zealand Daylight Time) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1.4 Build (40) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: netramet-owner@auckland.ac.nz Precedence: bulk --- Begin Forwarded Message --- Date: Fri, 30 Oct 1998 12:51:56 +1300 (NZDT) From: Daniel Ayers To: netramet@auckland.ac.nz Subject: Packet loss on FreeBSD meters using BPF I have done some testing with FreeBSD 2.2.7 and NeTraMet 4.2, 4.2.1 and 4.3b1. My system also reported lost packets ("lsp=" in the "#Stats:" line in the flow files), so I decided to look through the NeTraMet and FreeBSD sources to find out what was behind that number. I was generating a peak load of 12kpps (on 10mbit) and losing about 400-500 packets per minute, with collections every 60 seconds. (I tried raising the priority of the NeTraMet process to make sure it was processing the packets fast enough, but that didn't help). The short explaination is that BPF has a small internal buffer where incoming packets are stored. On my system (FreeBSD 2.2.7) that buffer is 4k. If the buffer is full, packets are discarded. I haven't done any analysis to justify a better value for the buffer size, I just added a zero to make it 40k. ;-) When I reran the tests, there wasn't a single packet dropped in 15 hours worth of 12kpps load. I'm not well-versed in tuning FreeBSD (I'm more familiar with Linux), all I did was change line 99 of net/bpf.c from: #define BPF_BUFSIZE 4096 to: #define BPF_BUFSIZE 40960 Reconfigured, recompiled and it worked fine. NeTraMet on my system (P2-350MHz) uses 8% of the CPU metering the 12kpps load. I've also configured it for 200000 flows... :-) Daniel. ------------------------------------------------------------------------------ Daniel Ayers, B.Sc (Hons), M.Sc Email: daniel.ayers@netlink.co.nz Network Security Specialist DDI Phone: +64-4-916-5622 Netlink Fax: +64-4-916-5300 23 Waring Taylor St, PO Box 5358 Mobile: +64-21-387-334 Wellington, New Zealand URL: http://www.netlink.co.nz --- End Forwarded Message ---