




















|
 |

| Mon Sep 11 18:24:30 EDT 2006
(carter@qosient.com) |
2.x backward compatibility testing almost complete, with a lot of emphasis focused on
correctness. This testing has revealed some 2.x bugs, all related to directionality.
Argus-3.0 should be considered the new reference and sites should seriously consider
upgrading as soon as the base code is released. The next phase of testing will validate
issues in protocol transaction state reporting, after which we will release argus-3.0.0
as a stable release!!!!
Argus-3.0 is now stable enough for general testing. Client testing should be on everyones
list, and we still need to work on documenation, so again, don't be shy!!!!!!
|
| Wed Jul 12 12:56:58 EDT 2006
(carter@qosient.com) |
All known fatal errors and basic functionality issues have been resolved!!!
Argus-3.0 testing is now focused on argus-2.x backward compatibility, with most data elements
generating the same data types, values and formats. This is very important as it
establishes a certified codebase from which we can make future changes. Once this
phase is complete, we'll transition data elements, such as protocol transaction state
status id's to their new values. After this is, we will release argus-3.0.0
as a stable release, hopefully by the end of the month!!!!
Argus-3.0 is now stable enough for general testing!!!
|
| Mon Jun 19 12:24:38 EDT 2006
(carter@qosient.com) |
Argus-3.0 testing has progressed to where the server and clients software compiles on most
target platforms, which currently include Linux, FreeBSD, NetBSD, OpenBSD, Solaris, IRIX.
Currently, the effort on the mailing list is centered on 2.0 -> 3.0 client consistency checks.
Argus-3.0 supports IPv6 tracking, and so if any users have any IPv6 traffic, it would be good
to get some feedback on these new features. Outstanding IPv6 issues include completing the
ICMPv6 support to make sure its complete, and to deal with NDA and NDR discovery flows.
I've gotten argus to compile on CYGWIN, using winpcap, but currently there are run time
problems, so we need to address those issues.
|
| Fri Jun 16 14:21:58 EDT 2006
(carter@qosient.com) |
The
first round of testing for argus-3.0 started with a bang, and the code is shaping up. If
you would like to test drive, check out the
Argus 3.0 development directory and get the
latest release candidate software "rc". Argus-3.0 supports IPv6, and 64-bit processing,
including 64-bit counters for all values.
|
| Fri Jun 9 14:21:10 EDT 2006
(carter@qosient.com) |
Argus-3.0 software testing is ongoing and active. Track all the fun in argus mailing archive.
http://news.gmane.org/gmane.network.argus
The effort currently involves porting issues, but is not limited to that. A lot of code
has changes, as this is a major version change, and so a lot of silly things, like default
field formats, column names, the way you specify output formats, etc...., have all been modified
to deal with issues that came up in argus-2.0. There are man pages for all the programs in
the release candidate software, so please take a look, and comment on the argus-mailing list.
|
| Wed Jun 7 17:17:59 EDT 2006
(carter@qosient.com) |
Argus-3.0 software available for testing, this includes both server and client software. It
is available from the
Argus 3.0 development directory. What needs to be done? We need
to just do the basics, install, run, validate the basics, and run through the man pages
to see what needs to updated, corrected, whatever. The supporting files should be up to
date, such as configurations, etc, but argus-3.0 is not compatible with argus-2.0, so you
will have to change some things to get it going.
|
faq +
how-to + manuals
+ credits + license
+ copyright

changes + cvs
+ wish list + registration
+ mailing lists
© Copyright 2000 - 2006 QoSient, LLC. All rights reserved.
|
| |
|
|
  |