bug list/alpha status
Last updated:
Fri Mar 31 10:49:57 EST 2000
What's the status of the alpha release? This web page will keep
track of that. The bug descriptions are for my own use, so don't
expect them to be particularly informative. The length of the
list is really the most important factor from your viewpoint...
Bug reporting
A temporary mail alias for alpha bug reports only has been
set up. Send bug reports on 1.4a and 2.0a only
to:
nistnet-bugs@antd.nist.gov.
For the bug reports to be useful, keep the following points in mind:
- Always make sure you have the latest version before reporting a bug.
- Check whether the bug is already listed below. In that case,
only send a report if you have additional information to provide.
- In general, the more information you can provide on a bug, the
better. Good things: simple setup to reproduce bug, any kernel
messages (use dmesg to print). Better things: point out the area
of the code with the flaw.
- Don't expect a direct response unless I need more information or
can't verify the bug. If I can verify it, it will appear in the list
below.
Items to be fixed before alpha release
The following items all must be addressed before the alpha release.
In other words, the alpha release is not going to occur until this
list is zero in length.
- No killer bugs known at this time! Just documentation and
release packaging left.
Items that will not be fixed before alpha release
The following items/new features will not get fixed/implemented
before the alpha release. Expect them to be addressed over the
next month.
- Stats are definitely off for very small values or very large
variances. This can be fixed by improving the table and making
the conversion routines a little better behaved.
- X interface - need to tab-chain the text input fields.
- X interface - possible memory leak needs investigating. This may
be a bogus complaint from dmalloc.
- X interface - gets confused when you make duplicate entries,
then remove one of the duplicates. Rather than report repeated
errors on stat, it should either remove the others, or silently
ignore them.
- Missing these mask combinations: host:.prot to any and vice versa.
Might be nice to add.
- Lib doesn't parse igmp groups properly.
- Don't use getservbyport() on protocols other than tcp and udp.
- Other protocols need fleshing out and testing. In particular,
ipip tunnels need to handle tunneled IP addresses.
- Old demo addons (linmunge, nistspy) need more updating to work
effectively with new setup.
- Thorough cleanout of redundant and unused code. Reduce size
and improve performance.
- New widget updates are a little slow. Try to speed up.
- 2.0 version should use more "principled" packet interception
- Documentation needs updating.
Comments? Questions? Let us know at
nistnet-dev@antd.nist.gov.
[
Home Page]
[Installing NISTNet]
[Using NISTNet]
[NISTNet FAQ]