Difference between revisions of "Cartographer Project Release Notes"
From Krupczak.org
(→Release 1) |
|||
| Line 3: | Line 3: | ||
= Release 1 = | = Release 1 = | ||
| − | The first, initial release consists of the following components/versions. | + | The first, initial release consists of the following components/versions. Consequently, everything is "new" in this release. While it is the first publicly available release, the software has been in continuous usage for quite some time (see the different copyright dates in various source files) and is stable. |
| + | |||
| + | Why are the version numbers less than one when this release is termed ''Release 1''? Version 1.x will signify a stable API and protocol. Since this is the first release available publicly, we felt it best to gather community feedback prior to codifying 1.0. | ||
* Cartographer GUI version 0.27 | * Cartographer GUI version 0.27 | ||
Revision as of 17:27, 11 November 2008
Contents |
Release 1
The first, initial release consists of the following components/versions. Consequently, everything is "new" in this release. While it is the first publicly available release, the software has been in continuous usage for quite some time (see the different copyright dates in various source files) and is stable.
Why are the version numbers less than one when this release is termed Release 1? Version 1.x will signify a stable API and protocol. Since this is the first release available publicly, we felt it best to gather community feedback prior to codifying 1.0.
- Cartographer GUI version 0.27
- Agent engine (xmpd) version 0.72
- MIB2 plugin version 0.91
- Cartographer plugin version 0.41
Known Issues in Release 1
- Some default installations of 64-bit Linux do not automatically include 32-bit versions of libxml and libz and thus need to be installed by hand.
- Some default installations of 64-bit Linux do not automatically include a 32-bit libgcc_s which is required by pthreads_cancel(). If not present, the library can be installed by hand.
- Occasional segmentation-fault on UNIX.
- New and improved Windows Vista security makes running ntsetup and cartographertray a real chore.
- Automatic upgrades sometimes (very rarely) fail because agent engine takes too long to stop and re-start.
- Windows use of reserved ports during dynamic binding fools some dependency determination. For example, an application may ask for a dynamically-bound TCP port and be assigned the well-known and/or reserved port of 1812 thus triggering a false Radius dependency.
- Dependencies determined via TCP port allocation may be missed of the connections are short-lived.
- XML DTDs or Schemas are needed for XMP and MIBs.
- IPv6 support is included but still needs more work with respect to DNS.
- NAT'ing routers obstruct inward-bound XMP communication.
