From netramet-owner Fri Oct 27 14:14:27 2000
Received: (from majordom@localhost)
by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id OAA04140
for netramet-outgoing; Fri, 27 Oct 2000 14:11:10 +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.2/8.9.2/8.9.2-ua) with SMTP id OAA04102;
Fri, 27 Oct 2000 14:10:55 +1300 (NZDT)
From: Nevil Brownlee <
[email protected]>
To: Hendrik Visage <
[email protected]>
Cc:
[email protected]
Subject: Re: NetraMet development question
In-Reply-To: <
[email protected]>
Message-ID: <
[email protected]>
Date: Fri, 27 Oct 2000 14:11:00 +1300 (New Zealand Daylight Time)
Priority: NORMAL
X-Mailer: Simeon for Win32 Version 4.1.4 Build (40)
X-Authentication: IMSP
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender:
[email protected]
Precedence: bulk
Hello Hendrik:
> I'd like to add some more functionality to the NetFlowMet et.al. to
> be able report on more NetFlow V5 data. (Possible V8 data too).
>
> Which version should I do the changes to be able to put it back into
> NetraMet quick & cleanly as possible??
You should use 44b8; that's the latest beta. Send me your patches
and I'll merge them in.
> BTW: What's the expected release date of 4.4, ie. moving out of beta?
I'd like to release 4.4 before the December IETF, i.e. about 20 Nov 00.
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 Sat Oct 28 04:27:15 2000
Received: (from majordom@localhost)
by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id EAA08723
for netramet-outgoing; Sat, 28 Oct 2000 04:23:34 +1300 (NZDT)
Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100])
by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id EAA08712
for <
[email protected]>; Sat, 28 Oct 2000 04:23:31 +1300 (NZDT)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA26115
for <
[email protected]>; Fri, 27 Oct 2000 11:22:54 -0400 (EDT)
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA08385
for <
[email protected]>; Fri, 27 Oct 2000 11:22:53 -0400 (EDT)
Received: from vsb014.mitre.org (129.83.21.14) by mailhub2.mitre.org with SMTP
id 4881635; Fri, 27 Oct 2000 11:22:50 -0400
Message-ID: <
[email protected]>
Date: Fri, 27 Oct 2000 10:17:58 -0500
From: David Burgess <
[email protected]>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.75 [en]C-20000818M (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To:
[email protected]
Subject: Re: NetraMet development question
References: <
[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender:
[email protected]
Precedence: bulk
I've recently started using NeTraMet again (I took a year or so off)
and found a small operational problem. I tried to use the -F option
on NeMaC to append flow data to the existing flow data file. The new
file overwrote the old file, which wasn't exactly what I was hoping
for.
I looked at the code and understand that the '##' record at the
beginning is problematic, but I'm a little unclear on why. I've
looked through the archive and didn't see anything that succinctly
explained why.
To avoid deleting my live data by accident in the future, I made a
small change to the code which 'versions' the -F file name instead
of just opening for write.... Is there some value to sending this
as a patch, or is there a really good reason to leave the filenaming
convention (and attendant file destruction) the way it currently works?
Nevil Brownlee wrote:
>
> Hello Hendrik:
>
> > I'd like to add some more functionality to the NetFlowMet et.al. to
> > be able report on more NetFlow V5 data. (Possible V8 data too).
> >
> > Which version should I do the changes to be able to put it back into
> > NetraMet quick & cleanly as possible??
>
> You should use 44b8; that's the latest beta. Send me your patches
> and I'll merge them in.
>
> > BTW: What's the expected release date of 4.4, ie. moving out of beta?
>
> I'd like to release 4.4 before the December IETF, i.e. about 20 Nov 00.
>
> 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
