This is a quick description of the present status of the MIT LCS Interactive
Network Map program.  For more information on what needs to be done look in
the ToDo file.




This is the Beta release of the MIT LCS Interactive Network Map program.
------------------------------------------------------------------------------


This phase of testing is intended to collect bug reports (and fixes),
suggestions for optimizations, other algorithms, doublecheck of correctness of
the behaviour of the various parts of the program, new useful features, etc.
In other words, everything is being polished except for porting to alien
environments, although I do solicit reports on portability problems built in
to the existing code and reports on porting to environments similar to those
presently working

Since this code is still undergoing development, I recommend you get yourself
put on one of the mailing lists described in the ReadMe file (I recommend
Magratheans, unless you want to hear unsolved bug reports).  General comments
and discussions related to the program should go to the Magratheans list.  Bug
reports of general interest (particularly if they include fixes) may go here
too, more directed ones (particularly if you haven't looked for a fix) to the
Bug-Map mailing list.  I will gather fixes and mail out "official" patches as
necessary.  Therefore you are advised to keep around a clean version of the
distribution; i.e. one containing only sanctioned patches.  If/when you modify
files, I advise you to keep track of your hacking so future releases can be
handled.

Any and all comments/critique will be appreciated, especially if constructive.


------------------------------------------------------------------------------
Contributions to this program have come from many sources, but some
special thanks goes to:

Chuck Davin	MIT				jrd@LCS.MIT.Edu
Dan Long	Bolt Beranek and Newman Inc.	long@bbn.com
Paul O'Neill	Oregon State Univ.		pvo@oce.orst.edu
Karl Owen	Data General			owen@dg-rtp.dg.com
Chris Tengi	Princeton Univ.			tengi@princeton.edu
Barry Margolin	Thinking Machines		barmar@think.com

Quick summary of known compatibilities:
------------------------------------------------------------------------------

This is a list of all the equipment (both hardware and software) that the
system has been known to run on out-of-the-box.  Not all combinations have
been tried, but I see no reason that they shouldn't work.  Some of these have
not been tried for several revisions of the program and so they may need a
little work to operate with the most recent version, but this should not be
much.  If you run the program on some equipment (either hardware or software)
not listed here, please drop a note to Map-Request@LCS.MIT.Edu and I will add
it to the list.  If you port the program to any new environments, we would all
like to hear, send reports to Magratheans@LCS.MIT.Edu and if you can supply
code that is upward compatible or compile time configurable that would be
ideal.



Systems (H/W, S/W):
	DEC MicroVAX running UNIX (4.3BSD+tahoe+LCS) or Ultrix (3.1)
	DECstation 3100 running Ultrix (3.1 and 4.1 reported)
	IBM-RT model 125 running AIS (4.3BSD UNIX)
	Tektronix 4317 running UTek
	Sun (at least Sun 4/110 w/SunOS 4.0.1 reported, I believe
		all [at least most] models/systems work)

Displays (one display type must be selected):
	X10: DEC GPX (Color), VS2000 (Color, B&W)
		Note: X10 support hasn't been tested in quite a while.
	X11: DEC GPX (Color); IBM-RT, IBM-RT w/ megapel display,
	     Sun4 (X11 or OpenWindows)

Window managers:
	uwm, twm, dxwm, gwm

Protocols supported:
	IP/ICMP/ECHO (required)
	IP/UDP/SNMP (optional)
	CHAOS/STATUS (optional)

Hardcopy supported (all hardcopy support is individually selectable):
	PostScript (Black&White): QMS PS 800-II, QMS PS-2400
	Tektronix (Color): 4692

Details on the particular support available.
----------------------------------------------------------------

Presently IP and (optionally) CHAOS protocols.  It requires that your system
have IP (BSD sockets) available, but the Chaos protocol support is optional
(and defaults off).  It will parse any addresses whether support for the
protocol is defined, to allow reading each others Geometry files.  However, it
cannot test addresses in a protocol family that is not installed.

Can retrieve preset information with SNMP.  Presently some general system
wide info, interface statistics, address list, and routing table.  Mostly the
variables were the ones I thought it would be interesting to look at.  It is
fairly straightforward to change the info.  In the snmp.c file there is a
table where each set of variables is declared and a routine that formats the
information.

Can use IP/ICMP/Echo or Chaos/Status for checking response at all of a hosts
addresses.

Presently knows how to write black and white PostScript or color Tektronix
files for hardcopy.

Only display supported is X (either Version 10 or Version 11), both color and
black&white displays are supported.  Of course a lot more information can be
put on a color display.  It shouldn't be too hard to write additional display
modules to make other display systems (NeWs?) available as a link-time
configuration, all the display stuff is in one file.  The program will run on
a terminal that doesn't support X, you just don't get an interactive map (I
frequently run it from my home H19).  The X10 support is no longer used
regularly and some incompatibilities may have crept in.

Developed on MicroVAX running Berkeley 4.3BSD.  It also installs direct from
the distribution on many other machines (see list above).  I tried to write
the code to not have hardware/system dependancies so it should run on other
UNIX systems supporting Berkeley sockets (i.e.  SunOS).  But, since I don't
have lots of different systems readily available to test on, there may still
be some things I've missed (but with both VAX and RT working that covers a
lot of the things that can be wrong).
