RFC 1147
FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
RFC 1147: FYI on a Network Management Tool Catalog 🎀
Title: FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices 🦋 Authors: R. Stine, Editor (SPARTA, Inc.) 💅 Category: FYI: 2, which means it's informational, not a standard 🌸 Date: April 1990 📅 Obsoletes/Updates: the header doesn't list any, so nothing is replaced or updated here ✨
Status of This Memo ✨
okay so this FYI memo's whole goal is to give site admins and network managers practical info they can actually use 💖 It's for the Internet community, and it does not specify any standard. It's also not an IAB policy or recommendation statement 🙈 Comments, critiques, and new or updated tool descriptions are super welcome! Send them to Robert Stine at stine@sparta.com, or to the NOCTools working group at noctools@merit.edu 💌
Distribution of this memo is unlimited 🌈
1. Introduction 🧚
this catalog is basically a cheat sheet of tools that help network managers debug and maintain TCP/IP internets and interconnected communications resources 💜 Every entry tells you what the tool does, how it works, and how to get it 🔥
The NOCTools Working Group of the Internet Engineering Task Force (IETF) put this catalog together in 1989 ⭐ Future editions will come out as IETF members find tools that should be added, or spot deficiencies and inaccuracies 🫶 They're also thinking about making an edition for the OSI protocol suite, so keep an eye out 👀
Quick disclaimer, bestie: the IETF does not endorse any of the tools in here 🚫 For the most part, nobody on the team has evaluated the tools or validated their descriptions, and most of the commercial tool descriptions came straight from vendors. Caveat Emptor! 💀
1.1 Purpose 🎀
ngl, re-inventing the wheel is a whole thing in data communications 🙄 The main goal of this document is to fight that habit in a small but useful way 💅 By listing what some network management tools can do, we hope to pool and share what we know 🍓 Another goal is to show newcomers what they can do to manage internet sites, and there's a network management tutorial at the end that helps with that 🧚 Finally, by leaving things out, the catalog also shows which network management tools are needed but don't exist yet 😭
There are other great sources for this info too! 🌸 The DDN Protocol Implementation and Vendors Guide and the DATAPRO series on data communications and LANs are super comprehensive and informative 🤩 The DDN guide covers a lot of internet management topics, including evaluations of protocol implementations and network analyzers* 🔍 DATAPRO volumes are pricey, so check your local university or technical library! They're solid surveys of commercial network management products, and they also have tutorials, market analyses, product evaluations, and predictions about technology trends 📚
1.2 Scope 🦋
The tools in this document are used to manage the network resources, LANs, and devices that TCP/IP internets usually connect together 🌐 This is not a "how to" manual for network management, though, so don't come here expecting that 🙈 It has a tutorial, but it's way too brief and general to be your only source. Aspiring network managers need to study a lot more 📖 This catalog also isn't an operations manual for particular tools. Each tool entry is short and focuses on what the tool can be used for 💖 If you need help installing or running a tool, check its documentation, which can be hundreds of pages in some cases 😭
1.3 Overview 🗺️
Section 1 covers the purpose, scope, and organization of the catalog 🧚
Section 2 lists and explains the standard keywords used in the tool descriptions. The keywords work as a subject index into the catalog 🔑
Section 3 is the main body of the catalog and has the entries for network management tools 💅 They're in alphabetical order by tool name, and every description follows a standard format that's explained in the intro to Section 3 🎀
After the catalog, there's an appendix with a tutorial on the goals and practice of network management 🌸
- Instructions for obtaining the DDN Protocol Guide are given in Section 7 of the appendix.
1.4 Acknowledgements 🫶
The compilation and editing of this catalog was sponsored by the Defense Communications Engineering Center (DCEC), under contract DCA100-89-C-0001 💼 It started as an initial task to survey current internet management tools 🔍 But honestly, most of the catalog is the result of volunteer labor from the NOCTools Working Group, the User Services Working Group, and lots of other people 🥹 Without those volunteers, this catalog wouldn't exist. The support from the Internet community has been extremely gratifying 💜
A few people did especially notable work. Mike Patton, Paul Holbrook, Mark Fedor and Gary Malkin were super helpful with composition and editorial review ✨ Dave Crocker gave essential guidance and encouragement 👑 Bob Enger was involved from the very start, doing the real grunt work of chairing the Working Group and building the catalog 💪 Phill Gross helped christen the NOCTools Working Group, define its scope and goals, and set up its role in the IETF 🌈 And Mike Little came up with the original idea of enhancing and publicizing the management tool survey through IETF participation 💡
Any deficiencies and errors are, of course, the editor's responsibility 🙈
2. Keywords 🏷️
This catalog uses "keywords" to give terse descriptions of the tools 🎀 Keywords are abbreviated attributes of a tool or its use. So tools can be compared fairly, the group came up with uniform keyword definitions, which are listed below 💖 After the definitions, there's an index of catalog entries by keyword 🔖
2.1 Keyword Definitions 📝
the keywords are always listed in a predefined order, sorted first by the general category they fall into, and then alphabetically 💅 The categories for management tool keywords are:
- the general management area a tool relates to, or the tool's functional role 🎯
- the network resources or components that are managed 🌐
- the mechanisms or methods a tool uses to do its job ⚙️
- the operating system and hardware environment of a tool 💻
- the characteristics of a tool as a hardware product or software release 📦
Keywords for the general management area or functional role of a tool are:
- Alarm: a reporting/logging tool that can trigger on specific events within a network 🚨
- Analyzer: a traffic monitor that reconstructs and interprets protocol messages spanning several packets 🔬
- Benchmark: a tool used to evaluate the performance of network components 🏃♀️
- Control: a tool that can change the state or status of a remote network resource 🕹️
- Debugger: a tool that, by generating arbitrary packets and monitoring traffic, can drive a remote network component into various states and record its responses 🐛
- Generator: a traffic generation tool 🌊
- Manager: a distributed network management system or system component 👑
- Map: a tool that can discover and report a system's topology or configuration 🗺️
- Reference: a tool for documenting MIB structure or system configuration 📚
- Routing: a packet route discovery tool 🛣️
- Security: a tool for analyzing or reducing threats to security 🔐
- Status: a tool that remotely tracks the status of network components 📡
- Traffic: a tool that monitors packet flow 🚦
Keywords that identify the network resources or components a tool manages are:
- Bridge: a tool for controlling or monitoring LAN bridges 🌉
- CHAOS: a tool for controlling or monitoring implementations of the CHAOS protocol suite, or network components that use it 🌀
- DECnet: a tool for controlling or monitoring implementations of the DECnet protocol suite, or network components that use it 🖥️
- DNS: a Domain Name System debugging tool 🔤
- Ethernet: a tool for controlling or monitoring network components on ethernet LANs 🔌
- FDDI: a tool for controlling or monitoring network components on FDDI LANs or WANs 🧵
- IP: a tool for controlling or monitoring implementations of the TCP/IP protocol suite, or network components that use it 🌍
- OSI: a tool for controlling or monitoring implementations of the OSI protocol suite, or network components that use it 🧩
- NFS: a Network File System debugging tool 📁
- Ring: a tool for controlling or monitoring network components on Token Ring LANs 💍
- SMTP: an SMTP debugging tool 📧
- Star: a tool for controlling or monitoring network components on StarLANs ⭐
Keywords that describe a tool's mechanism are:
- Curses: a tool that uses the "curses" tty interface package 🖥️
- Eavesdrop: a tool that silently monitors communications media (for example, by putting an ethernet interface into "promiscuous" mode) 👀
- NMS: the tool is a component of, or queries, a Network Management System 🛰️
- Ping: a tool that sends packet probes such as ICMP echo messages. To help tell tools apart, NMS queries and protocol spoofing (see below) are not considered probes 🏓
Okay bestie, the keyword list is giving me a whole catalog of vibes 💅 Each tag tells you what a tool is built on, where it runs, and how you get it 🦋
Proprietary🎀: a distributed tool that uses proprietary communications techniques to link its components.SNMP💜: a network management system or component based on SNMP, the Simple Network Management Protocol.Spoof🧚: a tool that tests operation of remote protocol modules by peer-level message exchange.X🌈: a tool that uses X-Windows.
Next up are the tags for where a tool runs, which is basically its operating environment 🌸
DOS💖: a tool that runs under MS-DOS.HP⭐: a tool that runs on Hewlett-Packard systems.Macintosh🍓: a tool that runs on Macintosh personal computers.Standalone🔥: an integrated hardware/software tool that requires only a network interface for operation.UNIX👑: a tool that runs under 4.xBSD UNIX or related OS.VMS✨: a tool that runs under DEC's VMS operating system.
Last, the tags for how you get your hands on a tool, meaning whether it's hardware or software and whether it costs anything 🫶
Free💅: a tool is available at no charge, though other restrictions may apply. Tools that come with an OS distribution but aren't otherwise available are not listed as "free", so don't even try 🙈Library📚: a tool packaged with either an Application Programming Interface (API) or object-level subroutines that may be loaded with programs.Sourcelib🧁: a collection of source code (subroutines) upon which developers may construct other tools.
2.2. Tools Indexed by Keywords ✨
Okay, this is the index, so you can look up any tool by its keyword 🔍 Each tool is listed under every keyword that describes it, and both the keywords and the tools under them are alphabetical 🫶
Quick heads-up: the names have been tidied up a bit, so capitalization follows what the developers or distributors use. Those roman numerals in parentheses are NOT part of the name, they're just there to tell apart tools that share a name, and Section 3 explains how that works 💀
alarm bridge
CMIP Library ConnectVIEW
EtherMeter decaddrs
LanProbe NMC
LANWatch proxyd
NETMON (III) Snmp Libraries
osilog snmpd
SERAG
sma
Snmp Libraries CHAOS
snmptrapd LANWatch
SpiderMonitor map
Unisys NCC
WIN/MGT Station
xnetmon (I) control
XNETMON (II) CMIP Library
ConnectVIEW
NETMON (III)
analyzer NMC
LANWatch proxyd
Sniffer Snmp Libraries
SpiderMonitor snmpset
TokenVIEW
Unisys NCC
benchmark WIN/MGT Station
hammer XNETMON (II)
nhfsstone
SPIMS
spray
TTCP
Unisys NCC
curses DOS
Internet Rover Comp. Security Checklist
net_monitor ConnectVIEW
nfswatch hammer
osimon hopcheck
snmpperfmon LAN Patrol
LANWatch
netmon (I)
debugger NETMON (III)
SPIMS netwatch
OverVIEW
ping
DECnet Snmp Libraries
decaddrs snmpd (II)
LANWatch TokenVIEW
NETMON (III) XNETMON (II)
net_monitor xnetperfmon
NMC
Sniffer
Snmp Libraries eavesdrop
SpiderMonitor ENTM
XNETMON (II) etherfind
xnetperfmon EtherView
LAN Patrol
LanProbe
DNS LANWatch
DiG NETMON (II)
LANWatch netwatch
netmon (I) nfswatch
nslookup NNStat
OSITRACE
Sniffer
SpiderMonitor
Tcplogger
TRPT
ethernet free
arp arp
ConnectVIEW CMIP Library
ENTM CMU SNMP
etherfind DiG
etherhostprobe ENTM
EtherMeter etherhostprobe
EtherView hammer
LAN Patrol hopcheck
LanProbe HyperMIB
LANWatch Internet Rover
map map
NETMON (III) netmon (I)
netwatch NETMON (II)
Network Integrator netstat
nfswatch netwatch
NMC net_monitor
NNStat nfswatch
proxyd nhfsstone
SERAG NNStat
Sniffer NPRV
Snmp Libraries nslookup
snmpd (II) osilog
SpiderMonitor osimic
tcpdump osimon
Unisys NCC OSITRACE
WIN/MGT Station ping
XNETMON (II) query
xnetperfmon sma
SNMP Kit
tcpdump
FDDI tcplogger
Unisys NCC traceroute
TRPT
TTCP
generator
hammer
nhfsstone
ping
Sniffer
SpiderMonitor
spray
TTCP
Unisys NCC
HP IP
xup arp
CMU SNMP
Dual Manager
ENTM
etherfind
etherhostprobe
EtherView
getone
hammer
hopcheck
Internet Rover
LANWatch
map
Netlabs CMOT Agent
Netlabs SNMP Agent
netmon (I)
NETMON (II)
NETMON (III)
netstat
netwatch
net_monitor
nfswatch
NMC
NNStat
NPRV
OverVIEW
ping
proxyd
query
SERAG
Sniffer
SNMP Kit
Snmp Libraries
snmpask
snmpd (I)
snmpd (II)
snmplookup
snmpperfmon
snmppoll
snmpquery
snmproute
snmpset
snmpsrc
snmpstat
snmptrapd
snmpwatchokay bestie, the big tool index is here, and it is SO many tools 💅✨ I've kept every single line exactly as it is in the original, because the columns are basically a map and we can't mess with the map 🗺️🫶
snmpxbar
snmpxconn manager
snmpxmon CMIP Library
snmpxperf CMU SNMP
snmpxperfmon ConnectVIEW
snmpxrtmetric decaddrs
SpiderMonitor Dual Manager
SPIMS getone
spray LanProbe
Tcpdump map
Tcplogger Netlabs CMOT Agent
Traceroute Netlabs SNMP Agent
TRPT NETMON (III)
TTCP NMC
Unisys NCC NNStat
WIN/MGT Station osilog
xnetmon (I) osimic
XNETMON (II) osimon
xnetperfmon OverVIEW
sma
SNMP Kit
library Snmp Libraries
CMIP Library snmpask
Dual Manager snmpd (I)
LANWatch snmpd (II)
proxyd snmplookup
WIN/MGT Station snmpperfmon
snmppoll
snmpquery
Macintosh snmproute
HyperMIB snmpsrc
snmpset
snmpstat
snmptrapd
snmpwatch
snmpxbar
snmpxconn
snmpxmon
snmpxperf
snmpxperfmon
snmpxrtmetric
TokenVIEW
Unisys NCC
WIN/MGT Station
xnetmon (I)
XNETMON (II)
xnetperfmon
map NMS
decaddrs CMU SNMP
etherhostprobe ConnectVIEW
EtherMeter decaddrs
LanProbe Dual Manager
map EtherMeter
NETMON (III) getone
Network Integrator LanProbe
NPRV map
Snmp Libraries Netlabs CMOT Agent
snmpxconn Netlabs SNMP Agent
snmpxmon NETMON (III)
Unisys NCC NMC
xnetmon (I) NNStat
XNETMON (II) OverVIEW
proxyd
SERAG
NFS SNMP Kit
etherfind Snmp Libraries
EtherView snmpask
nfswatch snmpd (I)
nhfsstone snmpd (II)
Sniffer snmplookup
tcpdump snmpperfmon
snmppoll
snmpquery
snmproute
snmpset
snmpsrc
snmpstat
snmptrapd
snmpwatch
snmpxbar
snmpxconn
snmpxmon
snmpxperf
snmpxperfmon
snmpxrtmetric
TokenVIEW
Unisys NCC
WIN/MGT Station
xnetmon (I)
XNETMON (II)
xnetperfmon
OSI ring
CMIP Library ConnectVIEW
Dual Manager LANWatch
LANWatch map
Netlabs CMOT Agent NETMON (III)
NETMON (III) netwatch
osilog proxyd
osimic Sniffer
osimon Snmp Libraries
OSITRACE snmpd (II)
sma TokenVIEW
Sniffer XNETMON (II)
Snmp Libraries xnetperfmon
SpiderMonitor
SPIMS
XNETMON (II) routing
xnetperfmon arp
ConnectVIEW
decaddrs
ping etherhostprobe
etherhostprobe getone
hopcheck hopcheck
Internet Rover NETMON (III)
map netstat
netmon (I) net_monitor
net_monitor NMC
NPRV NPRV
ping query
spray Snmp Libraries
traceroute snmproute
TTCP snmpsrc
Unisys NCC snmpxrtmetric
xup traceroute
WIN/MGT Station
XNETMON (II)
proprietary
ConnectVIEW
EtherMeter security
LanProbe Comp. Security Checklist
SERAG ConnectVIEW
TokenVIEW Dual Manager
LAN Patrol
SERAG
reference XNETMON (II)
HyperMIB
Unisys NCC
SMTP sourcelib
Internet Rover CMIP Library
LANWatch CMU SNMP
mconnect HyperMIB
Sniffer Internet Rover
LANWatch
map
SNMP NETMON (III)
CMU SNMP net_monitor
decaddrs proxyd
Dual Manager SNMP Kit
getone Snmp Libraries
map Snmpd (II)
Netlabs SNMP Agent SpiderMonitor
NETMON (III) XNETMON (II)
NMC xnetperfmon
OverVIEW
proxyd
SNMP Kit spoof
Snmp Libraries DiG
snmpask Internet Rover
snmpd (I) mconnect
snmpd (II) nhfsstone
snmplookup nslookup
snmpperfmon query
snmppoll SPIMS
snmpquery
snmproute
snmpset standalone
snmpsrc EtherMeter
snmpstat Sniffer
snmptrapd SpiderMonitor
snmpwatch
snmpxbar
snmpxconn star
snmpxmon LAN Patrol
snmpxperf LANWatch
snmpxperfmon map
snmpxrtmetric NETMON (III)
Unisys NCC proxyd
WIN/MGT Station Sniffer
xnetmon (I) Snmp Libraries
XNETMON (II) snmpd (II)
xnetperfmon XNETMON (II)
xnetperfmon
status traffic
CMIP Library ENTM
CMU SNMP etherfind
ConnectVIEW EtherMeter
DiG EtherView
Dual Manager LAN Patrol
getone LanProbe
Internet Rover LANWatch
LanProbe NETMON (II)
mconnect netwatch
Netlabs CMOT Agent Network Integrator
Netlabs SNMP Agent nfswatch
netmon (I) NMC
net_monitor NNStat
NMC osimon
NNStat OSITRACE
NPRV Sniffer
nslookup snmpxperfmon
osimic SpiderMonitor
osimon tcpdump
OverVIEW tcplogger
ping TRPT
proxyd Unisys NCC
sma WIN/MGT Station
SNMP Kit
Snmp Libraries
snmpask
snmpd (I)
snmpd (II)
snmplookup
snmpperfmon
snmppoll
snmpquery
snmpstat
snmpwatch
snmpxbar
snmpxconn
snmpxmon
snmpxperf
snmpxperfmon
TokenVIEW
Unisys NCC
WIN/MGT Station
xnetmon (I)
XNETMON (II)
xnetperfmon
xup snmpxbar
UNIX snmpxconn
arp snmpxmon
CMIP Library snmpxperf
CMU SNMP snmpxperfmon
decaddrs snmpxrtmetric
DiG SPIMS
Dual Manager spray
etherfind tcpdump
etherhostprobe tcplogger
EtherView traceroute
getone TRPT
Internet Rover TTCP
map Unisys NCC
mconnect WIN/MGT Station
NETMON (II) xnetmon (I)
netstat XNETMON (II)
Network Integrator xnetperfmon
net_monitor
nfswatch
nhfsstone VMS
NMC arp
NNStat ENTM
nslookup netstat
osilog net_monitor
osimic NPRV
osimon nslookup
OSITRACE ping
ping Snmp Libraries
proxyd tcpdump
query traceroute
SERAG TTCP
sma XNETMON (II)
SNMP Kit xnetperfmon
Snmp Libraries
snmpask
snmpd (I)
snmpd (II)
snmplookup
snmpperfmon
snmppoll
snmpquery
snmproute
snmpset
snmpsrc
snmpstat
snmptrapd
snmpwatch
X
Dual Manager
map
snmpxbar
snmpxconn
snmpxmon
snmpxperf
snmpxperfmon
snmpxrtmetric
WIN/MGT Station
XNETMON (II)
xnetperfmon
xup3. Tool Descriptions ✨
This section is a collection of quick little write-ups about tools for managing TCP/IP internets 🎀. The entries are in alphabetical order by tool name, so you can scroll right to the one you want 💅.
Every entry follows the same standard format. Right after the NAME of a tool come its KEYWORDS, which are terse descriptions of what the tool is for or what it's like 🧚. The ABSTRACT gives the more detailed version of its purpose and characteristics. The MECHANISM section explains how the tool works. CAVEATS has warnings about using it, and BUGS covers known bugs or how to report them 🙈. LIMITATIONS describes the boundaries of what it can do, HARDWARE REQUIRED and SOFTWARE REQUIRED describe the environment it needs, and finally AVAILABILITY points you to vendors, online repositories, or other sources where you can get it 🦋.
We handle tool name clashes, meaning different tools with the same name, by adding parenthetical roman numerals to the names 💜. For example, BYU, MITRE, and SNMP Research each submitted a description of a tool called "NETMON." These tools were developed independently, do different things, run in different environments, and are about as related as the 19th-century explorer Richard Burton and the 20th-century actor Richard Burton 🎭. BYU's tool is listed as NETMON (I), MITRE's as NETMON (II), and the SNMP Research tool as NETMON (III).
The roman numerals only reveal the order in which the catalog editor received the tool descriptions. They should not be read as any sort of preference, priority, or rights to a tool name 🌈.
Internet Tool Catalog ARP
arp 🌸
NAME arp
KEYWORDS routing; ethernet, IP; UNIX, VMS; free.
ABSTRACT Arp displays and can modify the internet-to-ethernet address translations tables used by ARP, the address resolution protocol 🧚.
MECHANISM The arp program accesses operating system memory to read the ARP data structures.
CAVEATS None.
BUGS None known.
LIMITATIONS Only the super user can modify ARP entries 👑.
HARDWARE REQUIRED No restrictions.
SOFTWARE REQUIRED BSD UNIX or related OS, or VMS.
AVAILABILITY Available via anonymous FTP from uunet.uu.net, in directory bsd-sources/src/etc. Available with 4.xBSD UNIX and related operating systems. For VMS, it's available as part of the TGV MultiNet IP software package, as well as Wollongong's WIN/TCP 💖.
Internet Tool Catalog CMIP LIBRARY
CMIP Library 🦋
NAME CMIP Library
KEYWORDS alarm, control, manager, status; OSI; UNIX; free, library, sourcelib.
ABSTRACT The CMIP Library implements the functionality of the Common Management Information Service/Protocol as in the documents ISO DP 9595-2/9596-2 of March 1988. It can act as a building block for constructing CMIP-based agent and manager applications ✨.
MECHANISM The CMIP library uses ISO ROS, ACSE and ASN.1 presentation, as implemented in ISODE, to provide its service.
CAVEATS None.
BUGS None known.
LIMITATIONS The M-CREATE, M-DELETE and M-ACTION protocol primitives are not implemented in this version 🥲.
HARDWARE REQUIRED Developed on Sun3, tested on Sun3 and VAXStation.
SOFTWARE REQUIRED The ISODE protocol suite, BSD UNIX.
AVAILABILITY The CMIP library and the related management tools built upon it, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To get info about a copy, send email to gknight@ac.ucl.cs.uk or call +44 1 380 7366 📬.
The CMU SNMP Distribution 🌈
NAME The CMU SNMP Distribution
KEYWORDS manager, status; IP; NMS, SNMP; UNIX; free, sourcelib.
ABSTRACT The CMU SNMP Distribution is giving full package energy 💅. It includes source code for an SNMP agent, several SNMP client applications, an ASN.1 library, and supporting documentation.
The agent compiles into about 10 KB of 68000 code. The distribution includes a full agent that runs on a Kinetics FastPath2/3/4, and it's built into the KIP appletalk/ethernet gateway. The machine independent portions of this agent also run on CMU's IBM PC/AT based router 🖥️.
The applications are designed to be useful in the real world 🌍. Information is collected and presented in a useful format and is suitable for everyday status monitoring. Input and output are interpreted symbolically. The tools can be used without referencing the RFCs, which is honestly iconic 👑.
MECHANISM SNMP.
CAVEATS None.
BUGS None reported. Send bug reports to sw0l+snmp@andrew.cmu.edu. ("sw0l" is "ess double-you zero ell.") 🙈
LIMITATIONS None reported.
HARDWARE REQUIRED The KIP gateway agent runs on a Kinetics FastPath2/3/4. Otherwise, no restrictions.
SOFTWARE REQUIRED The code was written with efficiency and portability in mind 🫶. The applications compile and run on the following systems: IBM PC/RT running ACIS Release 3, Sun3/50 running SUNOS 3.5, and the DEC microVax running Ultrix 2.2. They are expected to run on any system with a Berkeley socket interface.
AVAILABILITY This distribution is copyrighted by CMU, but it may be used and sold without permission. Consult the copyright notices for further information. The distribution is available by anonymous FTP from the host lancaster.andrew.cmu.edu (128.2.13.21) as the files pub/cmu-snmp.9.tar, and pub/kip-snmp.9.tar. The former includes the libraries and the applications, and the latter is the KIP SNMP agent.
Please direct questions, comments, and bug reports to sw0l+snmp@andrew.cmu.edu. ("sw0l" is "ess double-you zero ell.") If you pick up this package, please send a note to the above address, so that you may be notified of future enhancements/changes and additions to the set of applications (several are planned) 📝.
Computer Security Checklist 🔐
NAME Computer Security Checklist
KEYWORDS security; DOS.
ABSTRACT This program consists of 858 computer security questions divided up in thirteen sections. It presents the questions to the user and records their responses. After answering the questions in one of the thirteen sections, the user can generate a report from the questions and the user's answers 📋. The thirteen sections are: telecommunications security, physical access security, personnel security, systems development security, security awareness and training practices, organizational and management security, data and program security, processing and operations security, ergonomics and error prevention, environmental security, and backup and recovery security 💀.
The questions are weighted as to their importance, and the report generator can sort the questions by weight. This way the most important issues can be tackled first 🔥.
MECHANISM The questions are displayed on the screen and the user is prompted for a single keystroke reply. When the end of one of the thirteen sections is reached, the answers are written to a disk file. The question file and the answer file are merged to create the report file.
CAVEATS None.
BUGS None known.
LIMITATIONS None reported.
HARDWARE REQUIRED No restrictions.
SOFTWARE REQUIRED DOS operating system.
Okay bestie, the ConnectVIEW one comes first and it is giving a lot 💅✨
AVAILABILITY
Commercial product, available from:
C.D., Ltd.
P.O. Box 58363
Seattle, WA 98138
(206) 243-8700NAME: ConnectVIEW 🎀
KEYWORDS: control, manager, routing, security, status; bridge, ethernet, ring; NMS, proprietary; DOS.
ABSTRACT
The ConnectVIEW Network Management System is a bunch of software managers that control and manage Halley System's internets 🌸 Those internets are built out of ConnectLAN 100 ethernet and ConnectLAN 200 Token Ring Brouters. The management software gives you an icon-based graphical network display with real-time monitoring and reporting, plus configuration, fault, performance and security management for ConnectLAN brouters. There's also a Planning function that lets you draw your networks, which is literally my favourite kind of main character energy 🦋
MECHANISM: Proprietary. 🔒
CAVEATS
ConnectVIEW has to run under Microsoft Windows, ideally on a dedicated management station. The good news is there's no degradation of LAN throughput ✨
BUGS: None known. 🫶
LIMITATIONS: Currently works only with Halley System's products.
HARDWARE REQUIRED
Needs a PC/AT compatible with 640KB RAM, an EGA adapter and monitor, a keyboard, a mouse, and an ethernet adapter 💻
SOFTWARE REQUIRED
MSDOS 3.3 or higher, plus Microsoft Windows/286 version 2.1.
AVAILABILITY
Commercially available from:
Halley Systems, Inc.
2730 Orchard Parkway
San Jose, CA 95134NAME
decaddrs, decaroute, decnroute, xnsroutes, bridgetab 🧚
KEYWORDS: manager, map, routing; bridge, DECnet; NMS, SNMP; UNIX.
ABSTRACT
These commands display private MIB information from Wellfleet systems 👑 They retrieve and format values of one or several MIB variables from the Wellfleet Communications private enterprise MIB, using the SNMP (RFC1098). Basically they're used to peek at the non-IP modules (DECnet, XNS, and Bridging) of a Wellfleet system.
Decaddrs shows the DECnet configuration of a Wellfleet system acting as a DECnet router, including the static parameters for each DECnet interface. Decaroute and decnroute show the DECnet inter-area and intra-area routing tables (so area routes and node routes). Xnsroutes shows routes known to a Wellfleet system acting as an XNS router. Bridgetab shows the bridge forwarding table, with the disposition of traffic arriving from or directed to each station known to the Wellfleet bridge module. All of these commands take an IP address as the argument and can specify an SNMP community for the retrieval. One SNMP query is performed for each row of the table.
Heads up: the Wellfleet system has to be operating as an IP router, or the SNMP won't be accessible 🚨
MECHANISM: Management information is exchanged by use of SNMP.
CAVEATS: None. 🌈
BUGS: None known.
LIMITATIONS: None reported.
HARDWARE REQUIRED: Distributed and supported for Sun 3 systems.
SOFTWARE REQUIRED: Distributed and supported for SunOS 3.5 and 4.x.
Internet Tool Catalog DECADDRS, DECAROUTE, et al.
AVAILABILITY
Commercial product of:
Wellfleet Communications, Inc.
12 DeAngelo Drive
Bedford, MA 01730-2204
(617) 275-2400Internet Tool Catalog DIG
NAME: DiG 🦋
KEYWORDS: status; DNS; spoof; UNIX; free.
ABSTRACT
DiG (domain information groper), is a command line tool that queries DNS servers in either an interactive or a batch mode. It was built to be more convenient and flexible than nslookup for gathering performance data and testing DNS servers 💅
MECHANISM: Dig is built on a slightly modified version of the bind resolver (release 4.8).
CAVEATS: none.
BUGS: None known.
LIMITATIONS: None reported.
HARDWARE REQUIRED: No restrictions. 🙌
SOFTWARE REQUIRED: BSD UNIX.
AVAILABILITY: DiG is available via anonymous FTP from venera.isi.edu in pub/dig.1.0.tar.Z 🍓
NAME: Dual Manager 👑
KEYWORDS: alarm, control, manager, map, security, status; IP, OSI; NMS, SNMP, X; UNIX; library.
ABSTRACT
Netlabs' Dual Manager manages TCP/IP networks using both SNMP and CMOT protocols 🔥 You can start that management through the X-Windows user interface (both Motif and Openlook), or through OSI Network Management (CMIP) commands. It handles configuration, fault, security and performance management, and it has extensive map management features, including scanned maps in the background. It also has simple mechanisms to extend the MIB and to assign specific lists of objects to specific network elements, so it can manage all vendors' specific MIB extensions 🧚 There's an optional relational DBMS for storing and retrieving MIB and alarm information. Finally, Dual Manager is an open platform, because it provides several Application Programming Interfaces (APIs) so users can extend its functionality. Iconic 🌈
The Dual Manager is expected to work as a TCP/IP "branch manager" under DEC's EMA, AT&T's UNMA and other OSI-conformant enterprise management architectures.
MECHANISM: The Netlabs Dual Manager supports the control and monitoring of network resources by use of both CMOT and SNMP message exchanges.
CAVEATS: None.
BUGS: None known.
LIMITATIONS: None reported.
HARDWARE REQUIRED: Runs on Sun/3 and Sun/4s.
SOFTWARE REQUIRED: Available on System V or SCO Open Desktop environments. Uses X-Windows for the user interface.
AVAILABILITY
Commercially available from:
Netlabs Inc
11693 Chenault Street Ste 348
Los Angeles CA 90049
(213) 476-4070
lam@netlabs.com (Anne Lam)NAME: ENTM -- Ethernet Traffic Monitor 💜
KEYWORDS: traffic; ethernet, IP; eavesdrop; VMS; free.
ABSTRACT
ENTM is a screen-oriented utility that runs under VAX/VMS 🖥️ It monitors local ethernet traffic and displays either a real time or cumulative histogram showing a percent breakdown of traffic by ethernet protocol type. You can report that information based on packet count or byte count. The percent of broadcast, multicast and approximate lost packets is reported too. The screen updates every three seconds. You can also display a real-time, sliding history window showing ethernet traffic patterns for the last five minutes, which is very "watching my own feed" 🙈
ENTM can also report IP traffic statistics by packet count or byte count. The IP histograms reflect information collected at the TCP and UDP port level, including ICMP type/code combinations. Both the ethernet and IP histograms can be sorted by ASCII protocol/port name or by percent-value. All screen displays can be saved in a file for printing later.
MECHANISM
This utility simply places the ethernet controller in promiscuous mode and monitors the local area network traffic. It preallocates 10 receive buffers and attempts to keep 22 reads pending on the ethernet device.
CAVEATS
Placing the ethernet controller in promiscuous mode may severely slow down a VAX system 💀 Depending on the speed of the VAX and how much traffic is on the local ethernet, a large amount of CPU time may be spent on the Interrupt Stack. Running this code on any production system during operational hours is discouraged.
BUGS
Due to a bug in the VAX/VMS ethernet/802 device driver, IEEE 802 format packets may not always be detected. A simple test is performed to "guess" which packets are in IEEE 802 format (DSAP equal to SSAP). So some DSAP/SSAP pairs may be reported as an ethernet type, while valid ethernet types may be reported as IEEE 802 packets 😭
In some hardware configurations, placing an ethernet controller in promiscuous mode with automatic-restart enabled will hang the controller. Their VAX 8650 hangs running this code, while their uVAX IIs and uVAX IIIs do not.
Please report any additional bugs to the author at:
Allen Sturtevant
National Magnetic Fusion Energy Computer Center
Lawrence Livermore National Laboratory
P.O. Box 808; L-561
Livermore, CA 94550
Phone : (415) 422-8266
E-Mail: sturtevant@ccc.nmfecc.govLIMITATIONS
The user is required to have PHY_IO, TMPMBX and NETMBX privileges. When activated, the program first checks that the user process has enough quotas remaining (BYTLM, BIOLM, ASTLM and PAGFLQUO) to run successfully without entering an involuntary wait state. Some quotas need a fairly generous setting 🍯
The contents of IEEE 802 packets are not examined. Only the presence of IEEE 802 packets on the wire is reported.
The count of lost packets is approximated. If, after each read completes on the ethernet device, the utility detects that it has no reads pending on that device, the lost packet counter is incremented by one. 🫶
When the total number of bytes processed goes past 7fffffff hex, every counter gets automatically reset back to zero. 🙈💀
HARDWARE REQUIRED You'll need a DEC ethernet controller 🔌
SOFTWARE REQUIRED VAX/VMS version V5.1+ 💜
AVAILABILITY Okay, this is the part where you grab the executables. FTP to the ANONYMOUS account (password GUEST) on CCC.NMFECC.GOV, then GET these four files:
[ANONYMOUS.PROGRAMS.ENTM]ENTM.DOC (ASCII text)
[ANONYMOUS.PROGRAMS.ENTM]ENTM.EXE (binary)
[ANONYMOUS.PROGRAMS.ENTM]EN_TYPES.DAT (ASCII text)
[ANONYMOUS.PROGRAMS.ENTM]IP_TYPES.DAT (ASCII text)Internet Tool Catalog ETHERFINDetherfind 🦋
NAME etherfind ✨
KEYWORDS traffic; ethernet, IP, NFS; eavesdrop; UNIX.
ABSTRACT Etherfind is the tool that sits there and watches every packet that passes through a network interface, then writes a text file describing the traffic 👀. Each line in the file is one packet, and it holds stuff like protocol type, length, source, and destination. You can have etherfind print out all the packet traffic on the ethernet, or just the traffic meant for the local host. Want to get more specific? You can filter by protocol (IP, ARP, RARP, ICMP, UDP, ND, TCP) and by source and destination addresses, plus TCP and UDP port numbers. Main character energy 👑
MECHANISM By default, and in usual operations, etherfind puts the interface into promiscuous mode 🫣. On 4.3BSD UNIX and related OSs, it uses a Network Interface Tap (NIT) to get a copy of the traffic on an ethernet interface.
CAVEATS None. Iconic 💅
BUGS None known 🌸
LIMITATIONS Minimal protocol information gets printed, which is kinda sad 🥲. Only the super user can run it. And the syntax is painful. Ngl, a lot of us have been there 😭
HARDWARE REQUIRED Ethernet 🔌
SOFTWARE REQUIRED SunOS 🌈
AVAILABILITY It's included as an executable in the SunOS "Networking Tools and Programs" software installation option ✨
etherhostprobe 🧚
NAME etherhostprobe 🍓
KEYWORDS map, routing; ethernet, IP; ping; UNIX; free.
ABSTRACT Etherhostprobe gives you a list of the hosts on an ethernet that respond to IP ARP 🦋. The list looks like this:
08:00:20:01:96:62 128.18.4.114 apptek4
08:00:20:00:02:fe 128.18.4.115 apptek5
08:00:20:00:57:6a 128.18.4.116 apptek6
08:00:20:00:65:34 128.18.4.117 apptek7
08:00:20:06:58:6f 128.18.4.118 apptek8
08:00:20:00:03:4f 128.18.4.119 apptek9The first column is the ethernet address, the second is the IP address, and the third is the hostname. If the name couldn't be found through gethostbyaddr, the third column gets left off. You can also pass a starting and ending IP address on the command line to narrow down the search 🎀
MECHANISM Etherhostprobe sends a UDP packet to the ``echo'' port, then peeks in the kernel's ARP cache for the matching address entry 👀. It doesn't care whether the UDP packet gets a reply (or no reply at all). The cache gets checked up to four times, at quarter-second intervals. The best part? This lets the program run for any user, no special privileges needed 🫶
CAVEATS Etherhostprobe will fill the kernel's ARP cache with possibly useless entries, which could slow down programs that are trying to do real work 😬
Etherhostprobe causes -lots- of ARPs to be generated, so network monitoring software (or people) might think something is horribly broken 🙈
Etherhostprobe spends up to one second looking at each possible address. So exhaustively searching a class-C network takes about four minutes, and exhaustively searching a class-B network takes about 18 hours. Exhaustively searching a class-A network takes the better part of a year, so don't even think about it 💀
Etherhostprobe will be fooled by gateways that implement proxy ARP. Every possible address on the proxy-ARPed subnet gets listed with the gateway's ethernet address 🤡
BUGS None known 🌸
LIMITATIONS If a machine isn't running IP ARP at the moment it gets probed, it will be considered nonexistent. Like, if a given machine is down when it's probed . . . 😵
All hosts being probed must be on the same (possibly bridged) ethernet 🧵
HARDWARE REQUIRED No restrictions, but see below 🌈
SOFTWARE REQUIRED Runs on SunOS 3.5, and possibly elsewhere 💜. The major non-standard portion of the code is ``tx_arp.c'', which reads the kernel's ARP cache.
AVAILABILITY Copyrighted, but freely distributed ✨. You can get it via anonymous FTP from spam.itstd.sri.com (128.18.10.1). From the pub directory, grab file EHP.1 for etherhostprobe, and files IPF.1 and IPF.2 for ipForwarding.
EtherMeter (tm), model LANB/150 ⚡
NAME EtherMeter (tm), model LANB/150 🍓
KEYWORDS alarm, map, traffic; ethernet; NMS, proprietary; standalone.
ABSTRACT The Network Applications Technology (NAT) EtherMeter is a dedicated ethernet traffic monitor that gives you stats on the ethernet segment it's plugged into 📊. It reports three major kinds of statistics:
For good packets, it reports the total number of good packets seen on the segment, the number of multicast and broadcast packets, and the total number of bytes in all packets seen.
For packets with errors, it reports the number of CRC errors, short packets, oversize packets, and alignment errors.
It also reports how packets are distributed by type, and how many protocols it has seen on the segment. A count of transmit collisions is reported too. Peak and current ethernet utilization rates get reported, etc. 🦋 You can set alarms for utilization rate, packet rate, total error count, and delta error 🚨
The EtherMeter sends its stats to a Network Management Station (NMS), also from NAT, using IP/UDP datagrams, so the meters can be monitored through routers 🌐. The NMS shows graphical and/or textual info, and the EtherMeter icons change colors to show status 🌈. When you set alarms and the levels get exceeded, an audible alarm goes off on the NMS, and the EtherMeter icon on the network map changes from green to yellow 💛
MECHANISM The EtherMeter is a self-contained board. It can either plug into a PC/AT bus for power, or live in a small standalone enclosure 🧚. You can get the board with either a 10BASE5 thick ethernet transceiver cable connector, or a 10BASE2 thin ethernet BNC connector.
CAVEATS The EtherMeter is mostly a passive device 🤍. Its only impact on the network comes from the monitoring packets it sends to the NMS. The EtherMeter is also assigned an IP address so it can talk to the NMS.
BUGS None known 🌸
LIMITATIONS It uses a proprietary protocol right now 🙃. The company has said it plans to develop SNMP for the EtherMeter in the first half of 1990. For now, the NMS doesn't keep log files. This limitation is acknowledged, and there are plans to add ASCII log file capability to the NMS 📝
HARDWARE REQUIRED An EtherMeter board and a PC/AT bus to plug it into, or a standalone enclosure with power supply (available from NAT) 🔌. You'll also need a Network Management Station and its software to fully interact with the EtherMeter devices.
SOFTWARE REQUIRED The EtherMeter software is included in ROM on the device. The NMS software is bundled in with the NMS hardware 💾
AVAILABILITY The EtherMeter device, standalone enclosure, and Network Management Station are available commercially from:
Network Application Technology, Inc.
21040 Homestead Road
Cupertino, California 95014
Phone: (408) 733-4530
Fax: (408) 733-6478EtherView(tm) 🎀
NAME EtherView(tm) 🌸
KEYWORDS traffic; ethernet, IP, NFS; eavesdrop; UNIX.
ABSTRACT EtherView is a network monitoring tool that runs on Sun workstations and lets you monitor your heterogeneous internet network 🧁. It monitors all systems on the ethernet, and it has three primary functions:
Load Profile: This lets users keep an eye on the load on the ethernet over long stretches of time 📈. The network administrator can use it to characterize the load generated by a node on the network, figure out which systems and applications make up how much of that load, and see how the load fluctuates over long periods.
NFS Profile: This lets the network administrator check the load on NFS servers, their average response time, and the mix of NFS load on each server 🗂️. People use the data to benchmark different NFS servers, spot which servers are overloaded, work out how many clients each server can support, and evaluate how well NFS accelerators are working. Data nerd heaven 🤓
Protocol Analyzer: Users can capture packets based on source, destination, application, protocol, bit pattern, packet size, or a boolean filtering expression 🕵️♀️. It has all the standard features, like configurable buffer size, packet slicing, and bit pattern based triggering criteria. It does automatic disassembly of NFS, TCP, UDP, IP, ICMP, ARP, and RARP packets 🔍. Packets can be examined in any combination of summary, hex, or detail format 💖
MECHANISM okay so EtherView uses Sun's NIT interface to flip the ethernet interface into promiscuous mode, which is how it captures packets 👀 A high level process manages the interface, and a low level process does the actual capturing and filtering. The two processes talk to each other through shared memory 🧚
BUGS None known ✨
LIMITATIONS bestie, this one's a little sad 🥲 because of limitations in Sun's NIT interface, EtherView will not capture packets originating from the system where it is run.
EtherView requires super-user privileges on the system where it is run 🔐
HARDWARE REQUIRED EtherView runs on all models of Sun-3, Sun-4 and Sun-386i 💻🌸
SOFTWARE REQUIRED
- Sun-3 - SunOS 4.0.3. (SunOS 4.0 with NIT fixes).
- Sun-4 - SunOS 4.0.
- Sun-386i - SunOS 4.0.
It runs under SunView, and it will run under X Windows in the future 🦋
AVAILABILITY EtherView is a copyrighted, commercial product from:
Matrix Computer Systems, Inc.
7 1/2 Harris Road
Nashua, NH 03062
Tel: (603) 888-7790
email: ...uunet!matrix!eviewgetone, getmany, getroute, getarp, getaddr, getif, getid 🎀
NAME getone, getmany, getroute, getarp, getaddr, getif, getid.
KEYWORDS manager, routing, status; IP; NMS, SNMP; UNIX.
ABSTRACT these commands grab values from MIB variables (RFC1066) using SNMP (RFC1098) and format them so they're actually readable 💅 getone and getmany retrieve arbitrary MIB variables, while getroute, getarp, getaddr, and getif pull and display tabular info, like routing tables, the ARP table, and interface configuration. getid shows the system name, identification, and boot time.
Getone <target> <mibvariable> retrieves and displays the value of the designated MIB variable from the specified target system. You can also specify the SNMP community name used for the retrieval 🫶 Getmany does the same thing for groups of MIB variables instead of single values. Each variable's name, value and data type get displayed.
Getroute returns info from the ipRoutingTable MIB structure in an accessible format. Getarp behaves similarly for the address translation table, getaddr does it for the ipAddressTable, and getif shows the interfaces table, supplemented with info from the ipAddressTable. Getid displays the system name, identification, ipForwarding state, and the boot time and date ⏰
All of them take a system name or IP address as an argument and can specify an SNMP community for the retrieval. One SNMP query is performed for each row of the table, which is a lot of queries but very thorough 🔍
MECHANISM queries SNMP agent(s).
CAVEATS none.
BUGS none known.
LIMITATIONS none reported.
HARDWARE REQUIRED distributed and supported for Sun 3 systems.
SOFTWARE REQUIRED distributed and supported for SunOS 3.5 and 4.x.
AVAILABILITY this is a commercial product of:
Wellfleet Communications, Inc.
12 DeAngelo Drive
Bedford, MA 01730-2204
(617) 275-2400hammer & anvil 🔨
NAME hammer & anvil
KEYWORDS benchmark, generator; IP; DOS; free.
ABSTRACT hammer and anvil are the benchmarking programs for IP routers 💥 Using these tools, gateways have been tested for per-packet delay, router-generated traffic overhead, maximum sustained throughput, and more.
MECHANISM tests are performed on a gateway in an isolated testbed. Hammer generates packets at controlled rates, and it can set the length and interpacket interval of a packet stream. Anvil counts packet arrivals 🧮
CAVEATS hammer should not be run on a live network 🚨
BUGS none reported.
LIMITATIONS early versions of hammer could not produce inter-packet intervals shorter than 55 usec.
HARDWARE REQUIRED hammer runs on a PC/AT or compatible, and anvil requires a PC or clone. Both use a Micom Interlan NI5210 for the LAN interface.
SOFTWARE REQUIRED MS-DOS.
AVAILABILITY hammer and anvil are copyrighted, though free ✨ Copies are available from pub/eutil on husc6.harvard.edu.
hopcheck 🐣
NAME hopcheck
KEYWORDS routing; IP; ping; DOS; free.
ABSTRACT hopcheck is a tool that lists the gateways traversed by packets sent from the hopcheck-resident PC to a destination. It uses the same mechanism as traceroute, but it's for IBM PC compatibles that have ethernet connections 🖥️ hopcheck is part of a larger TCP/IP package called ka9q, which is for use with packet radio. Ka9q can coexist on a PC with other TCP/IP packages such as FTP Inc's PC/TCP, but it must be used independently of other packages. Ka9q was written by Phil Karn. hopcheck was added by Katie Stevens, dkstevens@ucdavis.edu. Unlike traceroute, which requires a UNIX kernel mod, hopcheck runs on the standard, unmodified ka9q release, which is a big win 🙌
MECHANISM see the description in traceroute.
CAVEATS see the description in traceroute.
BUGS none known.
LIMITATIONS host table required. It does not work with a domain name server, or with an IP address as the argument. This is mainly an inconvenience 🙃
HARDWARE REQUIRED IBM PC compatible with an ethernet network interface card, though it does not work with the 3Com 505 board.
SOFTWARE REQUIRED DOS.
AVAILABILITY free 🎁 It's on deposit at the National Center for Atmospheric Research. For access from UNIX, it's available via anonymous FTP from windom.ucar.edu, in directory "etc," as hopcheck.tar.Z. For access directly from a PC, fetch nethop.exe and readme.hop; nethop.exe is executable. It's also available via anonymous FTP at ucdavis.edu, in the nethopexe or nethopsrc suite of files in directory "dist."
HyperMIB 📖
NAME HyperMIB
KEYWORDS reference; Macintosh; free, sourcelib.
ABSTRACT HyperMIB is a hypertext presentation of the MIB (RFC1066) 🍓 The tree structure of the MIB is shown graphically, and you traverse the tree by selecting branches. When the MIB variables are displayed, selecting one opens a text window showing that variable's definition, using the actual text of the MIB document.
MECHANISM the Apple Macintosh HyperCard utility is used. The actual text of the MIB document is read into scrollable text windows, and a string search is done on the selected variable. A person familiar with HyperCard programming could modify the program to suit their needs, such as adding the definitions for their company's private space 🧠
CAVEATS none.
BUGS none known.
LIMITATIONS this program only gives the definition of the MIB variables. It cannot poll a node to find the value of the variables 🙅♀️
HARDWARE REQUIRED Apple Macintosh computer with at least 1MByte of RAM.
SOFTWARE REQUIRED Apple Macintosh operating system and HyperCard.
AVAILABILITY this software may be copied and given away without charge 💜 The files are available by anonymous FTP on CCC.NMFECC.GOV. The files are:
[Anonymous.programs.HyperMIB]Hyper_MIB.help (ASCII text)
[Anonymous.programs.HyperMIB]Hyper.MIB (binary)
[Anonymous.programs.HyperMIB]MIB.tree (binary)The software is also available for a nominal fee from:
National Energy Software Center
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(312) 972-7250Internet Rover 🛰️
NAME Internet Rover
KEYWORDS status; IP, SMTP; curses, ping, spoof; UNIX; free, sourcelib.
ABSTRACT Internet Rover is a prototype network monitor that uses multiple protocol "modules" to test network functionality ✨ It has two main pieces of code: the data collector and the problem display.
There's one data collector that runs a series of network tests and keeps a list of problems with the network. There can be many display processes, all showing the current list of problems, which is super useful in a multi-operator NOC 👑
The display task uses curses, so many terminal types can show the problem file, either locally or from a remote site. Full source is provided. The data collector is easily configured and extensible, and contributions such as additional protocol modules and shell script extensions are welcome 🫶
MECHANISM a configuration file contains a list of nodes, addresses, a NodeUp? protocol test (ping in most cases), and a list of further tests to be performed if the node is in fact up. Modules are included to test TELNET, FTP, and SMTP. If the configuration contains a test that isn't recognized, a generic test is assumed, and a filename is checked for existence. This way, users can create scripts that create a file if there's a problem, and the data collector simply checks whether that file exists to determine if there's a problem 🧚♀️
CAVEATS none.
BUGS none known.
The Limitations for the previous tool first, with its hardware, software, and availability details. Then three more tools and the map.
This tool doesn't do anything with the test results yet. It was meant for a multi-operator setup, and it just shows a list of what's broken on the net. 🔍
HARDWARE REQUIRED: Suns and IBM RTs are the machines it's known to run on. 🖥️
SOFTWARE REQUIRED: Curses, 4.xBSD UNIX socket programming libraries, and BSD ping. 🧰
AVAILABILITY: You can grab the full source over anonymous FTP from merit.edu (35.1.1.42) in the ~ftp/pub/inetrover directory. The source and executables are public domain and can be freely distributed for non-commercial use. It's unsupported, but bug reports and fixes can go to wbn@merit.edu. 🌸
🦋 LAN Patrol
NAME: LAN Patrol
KEYWORDS: security, traffic; ethernet, star; eavesdrop; DOS.
ABSTRACT: Okay, LAN Patrol is a full-featured network analyzer, and it's giving total fault and performance management energy 💅. Network managers can keep an eye on user activity, spot traffic overloads, plan for growth, test cable, catch intruders, balance network services, and more. It collects data with state-of-the-art techniques to watch all activity on a network, so you get an accurate picture of how things are running. ✨
LAN Patrol's reports can be saved to disk as ASCII files, then imported into spreadsheet or database programs for deeper analysis. 📊
MECHANISM: The LAN Patrol interface driver programs a standard interface card to capture all the traffic on a network segment. It runs in the background of a regular PC and keeps stats for every station on the network. You can look at the info on screen, or get a custom report printed or saved to a file. 🖨️
CAVEATS: None. Normal operation is totally passive, so it's transparent to the network. 🫶
BUGS: None known. 🌈
LIMITATIONS: LAN Patrol can monitor up to 10,000 packets/sec on an AT class PC. It's limited to a maximum of 1024 stations for intervals of up to 30 days. 🕰️
Since LAN Patrol works at the physical level, it only sees traffic on the segment where it's installed. It can't see traffic across bridges. 🌉
HARDWARE REQUIRED: Computer: IBM PC/XT/AT, PS/2 Model 30, or compatible. It needs 512K memory and either a hard drive or a double-sided disk drive.
Display: color or monochrome text. A color display lets you color-code traffic info. 🎨
Network: an Ethernet, StarLAN, LattisNet, or StarLAN 10 network interface card. 🔌
SOFTWARE REQUIRED: PC DOS, MS-DOS version 3.1 or greater. 💾
AVAILABILITY: You can buy LAN Patrol through network dealers, or directly from:
Legend Software, Inc.
Phone: (201) 227-8771
FAX: (201) 906-1151🧚 LanProbe
NAME: LanProbe -- the HP 4990S LanProbe Distributed Analysis System.
KEYWORDS: alarm, manager, map, status, traffic; ethernet; eavesdrop, NMS; proprietary.
ABSTRACT: The LanProbe distributed monitoring system does remote and local monitoring of ethernet LANs, and it's protocol and vendor independent. Iconic. 👑
LanProbe finds every active node on a segment and puts it on a map, with its adapter card vendor name, ethernet address, and IP address. You can add extra info about the nodes, like equipment type and physical location, into the database yourself. 🗺️
With the NodeLocator option, data on where nodes actually are gets entered automatically, so the map becomes an accurate picture of the segment's physical layout. After that, when a new node shows up, or one moves or goes inactive, the change gets detected and shown on the map in real time. The system also gives the network manager precise cable fault info, displayed right on the map. ⚡
Traffic stats get gathered and displayed, and you can export them in (comma delimited) CSV format for more analysis. You can set alerts on user-defined thresholds. 📈
Trace gives you remote protocol analyzer capability, with decodes for common protocols. 🔍
Significant events get logged, like power failure, cable breaks, a new node on the network, a broadcast IP source address seen, and so on. That log gets uploaded to ProbeView periodically. 🫧
ProbeView makes reports that you can work with in MSDOS based word processors, spreadsheets, and DBMS programs. 📝
MECHANISM: The system has one or more LanProbe segment monitors, plus ProbeView software that runs under Microsoft Windows. The LanProbe segment monitor attaches to the end of an ethernet segment and monitors all traffic. You can attach it directly to thin or thick coax cable, or through an external transceiver to fiber optic or twisted pair cabling. Network data for the segment gets sent to a workstation running ProbeView over RS-232, ethernet, or a modem connection. 🔗
ProbeView runs on a PC/AT class workstation and shows network info in graphical displays. 📊
The HP4992A NodeLocator option attaches to the opposite end of the cable from the HP4991A LanProbe segment monitor. On coaxial cabling schemes, it automatically finds where nodes are on the ethernet networks. 📍
CAVEATS: None. 🌸
BUGS: None known. 🐞
LIMITATIONS: None reported. ✅
HARDWARE REQUIRED:
HP 4991A LanProbe segment monitor
HP 4992A NodeLocator (for optional capabilities)
80386 based PC capable of running MS-WindowsSOFTWARE REQUIRED: HP 4990A ProbeView, plus MSDOS 3.0 or higher and Microsoft Windows/286 2.1. 💻
AVAILABILITY: It's a commercial product, available from:
Hewlett-Packard Company
P.O. Box 10301,
Palo Alto, CA 94303-0890🌈 LANWatch
NAME: LANWatch
KEYWORDS: alarm, analyzer, traffic; CHAOS, DECnet, DNS, ethernet, IP, OSI, ring, SMTP, star; eavesdrop; DOS; library, sourcelib.
ABSTRACT: LANWatch 2.0 is cheap, powerful, and flexible, and it's a network analyzer that runs under DOS on personal computers. It needs no hardware changes to the host or the network. 🙌 It's an invaluable tool for installing, troubleshooting, and monitoring LANs, and for developing and debugging new protocols. 🔥
Network managers can look at traffic patterns and packet errors to find performance problems and bottlenecks. Protocol developers can use it to inspect and check that protocols are handled properly. 🧐 Because it's software-only and installs easily on existing PCs, network technicians and field service engineers can carry it in their briefcase and analyze networks at remote sites. 💼
LANWatch has two operating modes: Display and Examine. In Display Mode, it traces traffic by showing captured packets in real time. Examine Mode lets you scroll back through stored packets and look at them in detail. 🔎
To pick a subset of packets for display, storage, or retrieval, there's a big set of built-in filters. They mean LANWatch only collects packets you care about, so you don't have to dig through all the traffic. The built-in filters are alarm, trigger, capture, load, save, and search. You can control each one separately to match on source or destination address, protocol, or packet contents at the hardware and transport layers. 🎯 LANWatch also comes with enough source code that you can change the existing filters and parsers or add new ones. 🛠️
The LANWatch distribution has executables and source for several post-processors: a TCP protocol analyzer, a node-by-node traffic analyzer, and a dump file listing tool. 📦
MECHANISM: It works with many common PC network interfaces by putting them in promiscuous mode and capturing traffic. 🪄
CAVEATS: Most PC network interfaces won't capture 100% of the traffic on a fully-loaded network. They mostly miss back-to-back packets. 🙈
BUGS: None known. 🌸
LIMITATIONS: LANWatch can't analyze what it doesn't see (see Caveats). 👀
HARDWARE REQUIRED: LANWatch needs a PC or PS/2 with a supported network interface card. 💜
SOFTWARE REQUIRED: LANWatch runs in DOS. Changing the supplied source code, or making new filters and parsers, needs Microsoft C 5.1. 💅
AVAILABILITY: LANWatch is commercially available from FTP Software, Incorporated, 26 Princess Street, Wakefield, MA, 01880, phone (617 246-0900). 📞
🍓 map
NAME: map -- Interactive Network Map
KEYWORDS: manager, map; CHAOS, ethernet, IP, ring, star; NMS, ping, SNMP, X; UNIX; free, sourcelib.
ABSTRACT: map draws a map of network connectivity, and it lets you interactively check information about the various components. That includes whether hosts can be reached over the network. It's giving visual network clarity 🗺️✨
The program comes with complete source, and it's written in a modular way 🧩, so adding different protocol stacks, displays, or hardcopy devices is relatively easy, bestie ✨. That's literally one of the reasons the first version supports at least two of each 💅. Contributions of extra drivers in any of those areas are welcome, and so is porting it to more platforms 🌈.
MECHANISM 🛰️
Net components are pinged by use of ICMP echo and, optionally, CHAOS status requests and SNMP "gets." 📡 The program initializes itself from static data stored in the file system, so it doesn't need to touch the network to get running (unless the static files are network mounted) 🙌.
CAVEATS ⚠️
As of publication, the tool is in beta release.
BUGS 🐛
Several minor nits, documented in distribution files. 🙈 Bug discoveries should be reported by email to Bug-Map@LCS.MIT.Edu.
LIMITATIONS 🚧
See distribution file for an indepth discussion of system capabilities and potential.
HARDWARE REQUIRED 🖥️
An X display is needed for interactive display of the map, and non-graphical interaction is available in non-display mode 🎀. For hardcopy output, a PostScript or Tektronix 4692 printer is required 🖨️.
SOFTWARE REQUIRED 💾
BSD UNIX or related OS. IP/ICMP is required, while CHAOS/STATUS and SNMP can be used but are optional ✨. X-Windows is required for interactive display of the map.
AVAILABILITY 📬
As of publication, map is in beta release. 🧁 To be added to the email forum that discusses the software, or to obtain individual files or instructions on getting the full current release, send a request to:
MAP-Request@LCS.MIT.EduThe program is Copyright MIT. It's available via anonymous FTP with a license that makes it free to use and distribute for non-commercial purposes 🦋.
Internet Tool Catalog · MCONNECT 🎀
mconnect 💌
KEYWORDS 🏷️
status; SMTP; spoof; UNIX.
ABSTRACT 📝
Mconnect allows an interactive session with a remote mailer 💌. Mail delivery problems can be diagnosed by connecting to the remote mailer and issuing SMTP commands directly 🔍.
MECHANISM 🔧
Opens a TCP connection to remote SMTP on port 25 🔌. Provides local line buffering and editing, which is the distinction between mconnect and a TELNET to port 25 ✨.
CAVEATS ⚠️
None.
BUGS 🐛
None known.
LIMITATIONS 🚧
Mconnect is not a large improvement over using a TELNET connection to port 25 😅.
HARDWARE REQUIRED 🖥️
No restrictions 💖.
SOFTWARE REQUIRED 💾
BSD UNIX or related OS.
AVAILABILITY 📬
Available with 4.xBSD UNIX and related operating systems 🌸.
Internet Tool Catalog · NETLABS CMOT AGENT 🧚
Netlabs CMOT Agent 🌟
KEYWORDS 🏷️
manager, status; IP, OSI; NMS.
ABSTRACT 📝
Netlabs' CMOT code debuted in Interop 89 🎉. The CMOT code comes with an Extensible MIB, which allows users to add new MIB variables 🧩. The code currently supports all the MIB variables in RFC 1095 via the data types in RFC 1065, as well as the emerging MIB-II, which is currently in experimental stage 🧪. The CMOT has been benchmarked at 100 Management Operations per Second (MOPS) for a 1-MIPS machine 🏎️.
MECHANISM 🔧
The Netlabs CMOT agent supports the control and monitoring of network resources by use of CMOT message exchanges 📡.
CAVEATS ⚠️
None.
BUGS 🐛
None known.
LIMITATIONS 🚧
None reported.
HARDWARE REQUIRED 🖥️
Portable to most hardware 💅.
SOFTWARE REQUIRED 💾
Portable to most operating systems 🌈.
AVAILABILITY 📬
Commercially available from:
Netlabs Inc
11693 Chenault Street Ste 348
Los Angeles CA 90049
(213) 476-4070
lam@netlabs.com (Anne Lam)Internet Tool Catalog · NETLABS SNMP AGENT 🌷
Netlabs SNMP Agent. 💜
KEYWORDS 🏷️
manager, status; IP; NMS, SNMP.
ABSTRACT 📝
Netlabs' SNMP code debuted in Interop 89, where it showed interoperation of the code with several implementations on the show floor 🤝. The SNMP code comes with an Extensible MIB, which allows users to add new MIB variables 🧩. The code currently supports all the MIB variables in RFC 1066 via the data types in RFC 1065, as well as the emerging MIB-II, which is currently in experimental stage 🧪. The SNMP has been benchmarked at 200 Management Operations per Second (MOPS) for a 1-MIPS machine 🚀.
MECHANISM 🔧
The Netlabs SNMP agent supports the control and monitoring of network resources by use of SNMP message exchanges 📡.
CAVEATS ⚠️
None.
BUGS 🐛
None known.
LIMITATIONS 🚧
None reported.
HARDWARE REQUIRED 🖥️
Portable to most hardware 💅.
SOFTWARE REQUIRED 💾
Portable to most operating systems 🌈.
AVAILABILITY 📬
Commercially available from:
Netlabs Inc
11693 Chenault Street Ste 348
Los Angeles CA 90049
(213) 476-4070
lam@netlabs.com (Anne Lam)Internet Tool Catalog · NETMON (I) 🦄
netmon 🛸
KEYWORDS 🏷️
status; DNS, IP; ping; DOS; free.
ABSTRACT 📝
Netmon is a DOS-based program that pings hosts on a monitored list at user-specified intervals ⏰. In addition, a user may optionally ping hosts not on the list 👀.
Netmon also performs domain lookups 🔎. Furthermore, a user may build and send a domain query to any desired DNS server 📮.
MECHANISM 🔧
The tool works by using the echo service feature of ICMP 🏓. It reports if it receives an incorrect response or no response 🚨.
CAVEATS ⚠️
Depending on the frequency of pinging and the number of hosts pinged, netmon could create a high volume of traffic 🌊.
BUGS 🐛
None known.
LIMITATIONS 🚧
None reported.
HARDWARE REQUIRED 🖥️
A PC, and a Western Digital WD8003 interface card (or any other card for which there is a packet driver for FTP Software Inc.'s PC/TCP kernel) 💻. Both monochrome and color displays are supported, though color is recommended 🌈.
SOFTWARE REQUIRED 💾
DOS operating system, and the PC/TCP Kernel by FTP Software, Inc. 📀
AVAILABILITY 📬
The BYU modified version is available for anonymous FTP from Dcsprod.byu.edu, in directory programs. It can be freely distributed for non-commercial use 💖.
NETMON and iptrace 🕵️♀️
KEYWORDS 🏷️
traffic; IP; eavesdrop; UNIX; free.
ABSTRACT 📝
NETMON is a facility that enables communication of networking events from the BSD UNIX operating system to a user-level network monitoring or management program 📡. Iptrace is a program interfacing to NETMON which logs TCP-IP traffic for performance measurement and gateway monitoring 🔍. It is easy to build other NETMON-based tools using iptrace as a model 🛠️.
NETMON resides in the 4.3BSD UNIX kernel 🏠. It is independent of hardware-specific code in UNIX 🧘. It is transparent to protocol and network type, having no internal assumptions about the network protocols being recorded 🫶. It is installed in BSD-like kernels by adding a standard function call (probe) to a few points in the input and output routines of the protocols to be logged 🧷.
NETMON is analogous to Sun Microsystems' NIT, but the interface tap function is extended by recording more context information 🧠. Aside from the timestamp, the choice of information recorded is up to the installer of the probes 🎯. The NETMON probes added to the BSD IP code supplied with the distribution include as context: input and output queue lengths, identification of the network interface, and event codes labeling packet discards 📋. (The NETMON distribution is geared towards measuring the performance of BSD networking protocols in an IP gateway 🌉.)
NETMON is designed so that it can reside within the monitored system with minimal interference to the network processing 🤏. The estimated and measured overhead is around five percent of packet processing 📊.
The user-level tool "iptrace" is provided with NETMON 🎁. This program logs IP traffic, either at IP-level only, or as it passes through the network interface drivers as well 🚦. As a separate function, iptrace produces a host traffic matrix output 🗺️. Its third type of output is abbreviated sampling, in which only a pre-set number of packets from each new host pair is logged 🎀. The three output types are configured dynamically, in any combination 🌈.
OSITRACE, another logging tool with a NETMON interface, is available separately (and documented in a separate entry in this catalog) 📚.
MECHANISM 🔧
Access to the information logged by NETMON is through a UNIX special file, /dev/netmon. User reads are blocked until the buffer reaches a configurable level of fullness 🪣.
Several other parameters of NETMON can be tuned at compile time 🎛️. A diagnostic program, netmonstat, is included in the distribution 🩺.
CAVEATS ⚠️
None.
Okay bestie, the NETMON bug stuff 🐛 BUGS: if something's broken or you've got a question, email the ie-tools crew. They're the official people for this, so no vibes-only DMs 💅
ie-tools@gateway.mitre.orgWant to join the list? Ask to join here:
ie-tools-request@gateway.mitre.orgYou can also just reach out to Allison Mankin directly, whether it's a question or a suggestion 🫶
Allison Mankin (703)883-7907
mankin@gateway.mitre.orgLIMITATIONS ⚠️ NETMON doesn't come with a NETMON interface for tcpdump or other UNIX protocol analyzers. Honestly it's simple to write one yourself, so don't panic 🌸 The NETMON probes for a promiscuous ethernet interface aren't included either.
HARDWARE REQUIRED 💻 No restrictions, bestie. Literally run it on whatever ✨
SOFTWARE REQUIRED 🧚 You need BSD UNIX-like network protocols, or you need to be able to install the BSD publicly available network protocols on the system you're monitoring 🎀
AVAILABILITY 🦋 You can grab the NETMON distribution by anonymous FTP from aelred-3.ie.org. The files are pub/netmon.tar or pub/netmon.tar.Z. There's also a short user's and installation guide called NETMON.doc in the same spot 📖 NETMON is provided "as is", and any code you derive from it has to keep a copyright text. It's copyrighted by the MITRE-Washington Networking Center, so keep that credit, periodt 💜
NAME 💖 NETMON -- an SNMP-based network management tool from SNMP Research
KEYWORDS 🏷️ alarm, control, manager, map, routing; DECnet, ethernet, IP, OSI, ring, star; NMS, SNMP; DOS; sourcelib.
ABSTRACT ✨ NETMON is a network management station that runs on a low-cost DOS-based platform. It works with lots of network types, including wide area networks and all sorts of LAN media 🌈 It's been used with multiprotocol devices that speak TCP/IP, DECnet, and OSI. The fault management tool shows a map of your network config, with each node and link state lit up in one of several colors 🎨 You can turn on alarms so the operator gets alerted when stuff happens on the network, and events get logged to disk. It also comes with complete source code, including a powerful set of portable libraries for building and parsing SNMP messages. Want to make reports? NETMON's output can go into flat files for a variety of statistical packages 📊
MECHANISM ⚙️ NETMON is built on the Simple Network Management Protocol (SNMP). It polls with the powerful SNMP get-next operator and the SNMP get operator. Trap-directed polling controls how much focus and intensity the polling gets 🔥
CAVEATS 🙈 None.
BUGS 🐛 None known. Iconic behavior 👑
LIMITATIONS ⚠️ The monitored and managed nodes must implement SNMP over UDP per RFC 1098, or they must be reachable through a proxy agent.
HARDWARE REQUIRED 🖥️ The minimum system is an IBM Personal Computer (4.77 MHz) with DOS 3.0 or later, an Enhanced Graphics Adapter, an Enhanced Graphics Monitor, a single 360 Kbyte floppy drive, and an ethernet adapter. BUT most users will want a hard disk for storing network history, and they'll be way less impatient with a faster CPU 🐢➡️🐇
SOFTWARE REQUIRED 💾 DOS 3.0 or later, plus TCP/IP software from one of several sources.
AVAILABILITY 💰 This one is a commercial product, available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff Case---
Internet Tool Catalog ✨ NETSTAT 🌸
NAME 💅 netstat
KEYWORDS 🏷️ routing; IP; UNIX, VMS; free.
ABSTRACT 🦋 Netstat is a program that reads network-related data structures inside the kernel, then shows you the output as ASCII right in your terminal. It can report on the routing table, TCP connections, TCP and UDP "listens", and protocol memory management 🧠
MECHANISM ⚙️ Netstat reads operating system memory to get the kernel routing tables. Lowkey magic 🪄
CAVEATS ⚠️ Kernel data structures can change while netstat is running, so your numbers might shift on you mid-read 😭
BUGS 🐛 None known.
LIMITATIONS 🙌 None reported.
HARDWARE REQUIRED 💻 No restrictions.
SOFTWARE REQUIRED 🖥️ BSD UNIX or a related OS, or VMS.
AVAILABILITY 🌈 You can get it by anonymous FTP from uunet.uu.net, in the directory bsd-sources/src/ucb. It comes with 4.xBSD UNIX and related operating systems. For VMS, it's included in the TGV MultiNet IP software package, and also in Wollongong's WIN/TCP 🎀
NAME 🧚 netwatch
KEYWORDS 🏷️ traffic; ethernet, IP, ring; eavesdrop; DOS; free.
ABSTRACT 👀 PC/netwatch listens to an attached local broadcast network and prints one line for every packet that goes by. Each line has the "to" and "from" local network addresses, the packet length, the value of the protocol type field, and 8 selected contiguous bytes of the packet contents. While netwatch is running, you can send it commands to show collected info, change its operating mode, or filter for specific types of packets 🔍
MECHANISM 🔌 It puts the controller in promiscuous mode. Main character energy 🎬
CAVEATS 🙈 None.
BUGS 🐛 None known.
LIMITATIONS 🚦 The monitor can handle a burst rate of about 200 packets per second. Anything faster than that gets missed, but it still shows up in the statistics of the network driver 📉 The display rate is about 25 packets per second, and there's a buffer that holds 512 undisplayed packets. Once that's full, the monitor discards overflow packets. Yikes 😭
HARDWARE REQUIRED 🖥️ An IBM PC compatible with CGA and a network interface: a 3com 3C501, an Interlan NI5010, or a proNet p1300.
SOFTWARE REQUIRED 💾 DOS 2.0 or higher, and MicroSoft C if you want to generate custom executables.
AVAILABILITY 🦋 It's available as a utility program in the pcip distribution from the host husc6.harvard.edu, in the directory pub/pcip. There's also a standalone package by anonymous FTP from windom.ucar.edu, in the file pc/network/netwatch.arc. A binary "dearc" program is available from windom.ucar.edu too 💖
NAME 📊 Network Integrator I
KEYWORDS 🏷️ map, traffic; ethernet; UNIX.
ABSTRACT 🌟 This tool monitors traffic on network segments. Everything gets dumped either into a log file or, for real-time viewing, into a command tool window. Data is time-stamped by date and time, and logging can keep going for up to 24 hours ⏰
The tool is super flexible about how it collects and presents data. You can set traffic filters by the header values of lots of protocols, including the ones used by Apple, DEC, Sun, HP, and Apollo 🍎 It can monitor bandwidth utilization, plus actual load and peak throughput. The Network Integrator can also analyze a network's topology and record where every operational node is 🗺️
Data can be displayed in six separate bar graph formats. There are also several routines for making statistical summaries of the collected data 📈
MECHANISM ⚙️ The tools work through RPC and XDR calls.
CAVEATS ⚠️ The tool adds only a little traffic to the network, BUT generating statistics from captured files can take a significant chunk of a workstation's CPU 🔥
BUGS 🐛 None known.
LIMITATIONS 🚫 You must be root to run the monitor. There doesn't seem to be a limit on the number of nodes, since it monitors by segments. The only major limit is how much disk space a user can commit to log files. The log file size, though, can be controlled through the tool's parameters 💜
HARDWARE REQUIRED 🖥️ Sun3 or Sun4.
SOFTWARE REQUIRED 💾 4.0BSD UNIX or greater, or a related OS.
AVAILABILITY 💰 It's copyrighted and commercially available from Network Integrators, at (408) 927-0412.
NAME 🧚 net_monitor
KEYWORDS 🏷️ routing, status; DECnet, IP; curses, ping; UNIX, VMS; free, sourcelib.
ABSTRACT 🦋 net_monitor uses ICMP echo (and DECnet reachability information on VAX/VMS) to keep an eye on a network. The monitoring is very simplistic, but it has proved useful 💅 It periodically tests whether hosts are reachable and reports the results on a full-screen display. It groups hosts together into common sets. If every host in a set becomes unreachable, it makes a lot of racket with bells, because it assumes some common piece of hardware supporting that set has failed 🔔 The test periodicity, the hosts to test, and the groupings are all controlled by a single configuration file.
The idea for this program came from the PC/IP monitor facility, but it's an entirely different program with different functionality 🌸
MECHANISM ⚙️ Reachability is tested with ICMP echo facilities for TCP/IP hosts (and DECnet reachability information on VAX/VMS). A DECnet node counts as reachable if it shows up in the list of hosts from a "show network" command run on a routing node 🛰️
CAVEATS 💅 okay so this one is giving "use it in a window on a workstation, not a dumb terminal" 🖥️ It could be useful if ported to a PC (looks easy using FTP Software's programming libraries), but this has not been done. Curses is very slow and cpu intensive on VMS, but the tool has been run in a window on a VAXstation 2000. Just don't try to run it on a terminal connected to a 11/750. 🙈
BUGS None known. ✨
LIMITATIONS This tool is not meant to be a replacement for a more comprehensive network management facility such as is provided with SNMP. 🧚
HARDWARE REQUIRED A host with a network connection. 🔌
SOFTWARE REQUIRED Curses, 4.xBSD UNIX socket programming libraries (limited set) and some flavor of TCP/IP that supports ICMP echo request (ping). It has been run on VAX/VMS running WIN/TCP and several flavors of 4BSD UNIX (including SunOS 3.2, 4.0, and 4.3BSD). It could be ported to any platform that provides a BSD-style programming library with an ICMP echo request facility and curses. 💜
AVAILABILITY Requests should be sent to the author:
Dale Smith
Asst Dir of Network Services
University of Oregon
Computing Center
Eugene, OR 97403-1211
Internet: dsmith@oregon.uoregon.edu.
BITNET: dsmith@oregon.bitnet
UUCP: ...hp-pcd!uoregon!dsmith
Voice: (503)686-4394With the source code, a makefile is provided for most any UNIX box and a VMS makefile compatible with the make distributed with PMDF. A VMS DCL command file is also provided, for use by those VMS sites without "make." 🛠️
The author will attempt to fix bugs, but no support is promised. The tool is copyrighted, but free (for now). 🎀
NAME nfswatch
KEYWORDS traffic; ethernet, IP, NFS; curses, eavesdrop; UNIX; free.
ABSTRACT Nfswatch is the tea 🍵 It monitors all incoming ethernet traffic to an NFS file server and divides it into several categories. The number and percentage of packets received in each category is displayed on the screen in a continuously updated display.
All exported file systems are monitored by default. Other files may optionally be monitored. Options also allow monitoring of traffic destined for a remote host instead of the local host, or monitoring traffic sent by a single host. Items such as the sample interval length can be adjusted either on the command line or interactively. Facilities for taking screen "snapshots," saving all data to a log file, and summarizing the log file are included. Nfslogsum, a program that summarizes the log file, is included in the distribution. 📊
MECHANISM Nfswatch uses the Network Interface Tap in promiscuous mode to monitor the ethernet. It filters out NFS packets destined for the local (or remote) host, and then decodes the file handles in order to determine which file or file system a request pertains to. 🕵️♀️
CAVEATS Because the NFS file handle is a non-standard (server private) piece of data, the file system monitoring part of the program will break whenever the format of a file handle is not what it expects to see. 😭 This is easily fixed in the code, however. The code presently understands SunOS 4.0 file handles.
BUGS None known. ✨
LIMITATIONS Up to 256 exported file systems and 256 individual files can be monitored, but only (2 * (DisplayLines - 16)) will be displayed on the screen (all data will be written to the log file).
Only NFS requests made by client machines are counted; the NFS traffic generated by the server in response to these requests is not counted. 🙅♀️
HARDWARE REQUIRED Has been tested on Sun-3 and Sun-4 systems. No hardware dependencies, but see below. 🖥️
SOFTWARE REQUIRED SunOS 4.0 or higher. The STREAMS NIT device is used. Fairly easy code modifications should be able to make it run under older SunOS releases, or other versions of BSD UNIX with a NIT-like device. 🧩
AVAILABILITY Copyrighted, but freely distributable. Available via anonymous FTP from hosts icarus.riacs.edu and spam.itstd.sri.com in pub/nfswatch.tar.Z. There should also be a copy on the 1989 Sun User's Group tape. 📼
NAME nhfsstone
KEYWORDS benchmark, generator; NFS; spoof; UNIX; free.
ABSTRACT Nhfsstone (pronounced n-f-s-stone, the "h" is silent) is an NFS benchmarking program. It is used on an NFS client to generate an artificial load with a particular mix of NFS operations. It reports the average response time of the server in milliseconds per call and the load in calls per second. The nhfsstone distribution includes a script, "nhfsnums" that converts test results into plot(5) format so that they can be graphed using graph(1) and other tools. 📈
MECHANISM Nhfsstone is an NFS traffic generator. It adjusts its calling patterns based on the client's kernel NFS statistics and the elapsed time. Load can be generated over a given time or number of NFS calls. ⏱️
CAVEATS Nhfsstone will compete for system resources with other applications. 🥲
BUGS None known. ✨
LIMITATIONS None reported. 💖
HARDWARE REQUIRED No restrictions. 🌈
SOFTWARE REQUIRED 4.xBSD-based UNIX 🦋
AVAILABILITY Available via anonymous FTP from bugs.cs.wisc.edu. Alternatively, Legato Systems will provide the program free of charge, if certain conditions are met. Send name and both email and U.S. mail addresses to:
Legato Systems, Inc.
Nhfsstone
260 Sheridan Avenue
Palo Alto, California 94306A mailing list is maintained for regular information and bug fixes: nhfsstone@legato.com or uunet!legato.com!nhfsstone. To join the list: nhfsstone-request@legato.com or uunet!legato.com!nhfsstone-request. 📬
NAME NMC -- the Hughes LAN Systems 9100 Network Management Center
KEYWORDS control, manager, routing, status, traffic; bridge, DECnet, ethernet, IP; NMS, SNMP; UNIX.
ABSTRACT The 9100 Network Management Center provides the capability to manage and control standards-based networking products from Hughes LAN Systems and other vendors. 🏢 This management extends to all network products that are equipped with the industry standard SNMP (Simple Network Management Protocol). A comprehensive relational database manages the data and ensures easy access and control of resources throughout the network. 👑
9100 NMC software provides the following functions:
- Database Management: Stores and retrieves the information required to administer and configure the network. It can be used to:
- Store and recall configuration data for all devices.
- Provide availability history for devices.
- Provides full-function SQL interface.
- Assign new internet addresses.
- Provide administrative information such as physical location of devices, person responsible, maintenance history, asset data, hardware/software versions, etc.
- Configuration Management: A comprehensive configuration model that enables you to:
- Retrieve configuration information from SNMP devices.
- Configure HLS devices using SNMP.
- Configures attributes relating to TCP/IP, DECnet and other protocols in HLS devices using SNMP.
- Poll devices to compare their current attribute values with those in the database and produce reports of the discrepancies.
- Collect data about the state of the network.
- Performance Management: Displays local network traffic graphically, by packet size, protocol, network utilization, sources and destinations of packets, etc. 📊
- Fault Management: Provides availability monitoring and indicates potential problems.
- Scheduled availability monitoring of devices.
- SNMP traps (alarms) are recorded in an alarm log.
- New alarms are indicated by a flashing icon and optional audio alert. 🚨
- Possible causes and suggested actions for the alarms are listed.
- Cumulative reports can be produced.
- Utilities Function: Allows you to view and/or stop existing NMC processes, and to define schedules for invoking NMC applications and database maintenance utilities. 🧰
MECHANISM SNMP. 🫶
CAVEATS None reported. ✨
BUGS None known. ✨
LIMITATIONS Maximum number of nodes that can be monitored is 18,000. This can include Hosts, Terminal Servers, PCs, and Bridges. 🔢
HARDWARE REQUIRED The host for the NMC software is a Sun 3 desktop workstation. Recommended minimum hardware is the Sun 3/80 Color with a 1/4" SCSI tape drive. 🖥️
SOFTWARE REQUIRED The NMC, which is provided on 1/4" tape format, runs on the Sun 4.0 Operating System. 💿
AVAILABILITY 🛍️ NNStat is a commercial product, and the company behind it is Hughes LAN Systems Inc. 🏢 Here's where to find them:
Hughes LAN Systems Inc.
1225 Charleston Road
Mountain View, CA 94043
Phone: (415) 966-7300
Fax: (415) 960-3738
RCA Telex: 276572NNStat 📊
NAME NNStat ✨
KEYWORDS manager, status, traffic; ethernet, IP; eavesdrop, NMS; UNIX; free. 🎀
ABSTRACT okay so NNStat is a bundle of programs that gives you internet statistic collecting, and the big idea is that it collects traffic stats with a promiscuous ethernet tap on the local networks instead of poking at the gateways 👀 If all the traffic going into or out of a network (or a group of networks) runs over one local ethernet, you just station a stats agent on each local network and boom, you get a profile of the traffic 🦋 The statistical data then gets pulled from those local agents by a global manager.
There's a program called "statspy" that does the gathering. It reads every packet on an ethernet interface and records all the info it cares about 💅 For each packet it checks whether the source or destination IP address is one being monitored, usually a gateway address. If it is, statspy looks inside the packet to see if it matches any further criteria.
There's also a program called "collect" that does the global collecting. It regularly polls the statspy processes in the domain you care about and grabs their locally logged stats 🌈
And the NNSTAT distribution comes with several sample awk programs that process the logged output from collect 🧚
MECHANISM the local agents (statspy processes) grab raw traffic data with a promiscuous ethernet tap 🔥 Then a global manager (the "collect" process) pulls back statistical, filtered, or otherwise reduced data from those agents.
CAVEATS None. 🙈
BUGS bug fixes, extensions, and other pointers get discussed on the electronic mail forum called bytecounters 📬 To join, send a request to bytecounters-request@venera.isi.edu. The forum exchanges are archived in the file bytecounters/bytecounters.mail, which you can grab with anonymous FTP from venera.isi.edu 💖
LIMITATIONS NNStat presumes a topology of one or more long haul networks gatewayed to local ethernets. ✨
A kernel mod is required to run with SunOS4. The mods are described in the bytecounters archive. 🛠️
HARDWARE REQUIRED you need an ethernet interface, plus a Sun 3, Sun 4 (SPARC), or PC RT workstation 🖥️
SOFTWARE REQUIRED the distribution is for BSD UNIX, but it could easily be adapted to any UNIX with promiscuous ethernet support 🌸
AVAILABILITY the distribution is available via anonymous FTP from venera.isi.edu, in the file pub/NNStat.tar.Z. The documentation is in pub/NNStat.userdoc.ms.Z 📂
Internet Tool Catalog NSLOOKUPNPRV 🗺️
NAME NPRV -- IP Node/Protocol Reachability Verifier 🦋
KEYWORDS map, routing, status; IP; ping; VMS; free. 💜
ABSTRACT NPRV is a full-screen, keypad-oriented utility that runs under VAX/VMS 🎀 It lets you quickly scroll through a list of IP addresses (or domain names) that you define, and check whether each node is reachable 👑 Reachability is figured out by doing an ICMP echo, a UDP echo, and a TCP echo, taking turns every three seconds ⏱️ It shows the total number of packets sent and received, plus the minimum, average, and maximum round-trip times (in milliseconds) for each type of echo. There's also a "trace route" function that finds the path from your local system to the remote host. Once the trace route info fills the screen, you can save a "snapshot" of the screen to a text file 📸 When you exit the utility, those text files can be used to generate a logical network map that shows how hosts and gateways are interconnected. Iconic 🌈
MECHANISM the ICMP echo works by sending ICMP ECHO REQUEST packets 🎯 The UDP and TCP echoes work by connecting to the UDP/TCP echo ports (port number 7). The trace route info is built by sending ICMP ECHO REQUEST packets and UDP packets with very large destination UDP port numbers, alternating between them, in two passes 🧚
Here's how the trace route goes. Each packet is first sent with a TTL (time to live) of 1. That should cause an ICMP TIME EXCEEDED error from the first routing gateway. Then each packet gets a TTL of 2, which should trigger an ICMP TIME EXCEEDED error from the second routing gateway. Then a TTL of 3, and so on 🌊 This keeps going until an ICMP ECHO REPLY or a UDP PORT UNREACHABLE comes back. That means the remote host has been reached and the trace route info is complete ✅
CAVEATS this utility sends one echo packet per second (ICMP, UDP, or TCP), and also sends out one trace route packet per second ⚡ If a transmitted trace route packet comes back in less than one second, another trace route packet is sent 100 milliseconds later. This could cause a lot of contention on the local network, so be careful 🙈
BUGS None known. Please report any bugs you find to the author:
Allen Sturtevant
National Magnetic Fusion Energy Computer Center
Lawrence Livermore National Laboratory
P.O. Box 808; L-561
Livermore, CA 94550
Phone : (415) 422-8266
E-Mail: sturtevant@ccc.nmfecc.govLIMITATIONS you need SYSPRV privilege to do the ICMP Echo and trace route functions. The utility will still run with this privilege disabled, but then only the UDP Echo and TCP Echo info gets displayed. It's written in C, but it can't be easily ported over to UNIX, since it uses a lot of VMS system calls and all the screen I/O is done with the VMS Screen Management Routines 🫶
HARDWARE REQUIRED any network interface supported by TGV Incorporated's MultiNet software 🔌
SOFTWARE REQUIRED VAX/VMS V5.1+ and TGV Incorporated's MultiNet version 2.0 💻
AVAILABILITY for executables only, FTP to the ANONYMOUS account (password GUEST) on CCC.NMFECC.GOV (128.55.128.30) and GET the following files:
[ANONYMOUS.PROGRAMS.NPRV]NPRV.DOC (ASCII text)
[ANONYMOUS.PROGRAMS.NPRV]NPRV.EXE (binary)
[ANONYMOUS.PROGRAMS.NPRV]SAMPLE.IPA (ASCII text)Internet Tool Catalog NSLOOKUPnslookup 🔍
NAME nslookup 💖
KEYWORDS status; DNS; spoof; UNIX, VMS; free. 🌸
ABSTRACT nslookup is a program for interactive queries of ARPA Internet domain servers 🧚 It's super useful for diagnosing routing or mail delivery problems, where a local domain server is often responding with an incorrect internet address 😭 It's basically a database front end that turns your queries into domain name queries. By default it queries the local domain name server, but you can specify additional servers too. You can also get extra info beyond just the mapping of domain names to internet addresses ✨
MECHANISM formats and sends domain name queries 📨
CAVEATS None. 🙈
BUGS None known. 🍓
LIMITATIONS None known. 🌈
HARDWARE REQUIRED no restrictions 🎉
SOFTWARE REQUIRED BSD UNIX or a related OS, or VMS 💅
AVAILABILITY nslookup is part of the "named" distribution, available via anonymous FTP from uunet.uu.net, in the directories bsd-sources/src/etc and bsd-sources/src/network. It's also part of the "bind" distribution, available via anonymous FTP from ucbarpa.berkeley.edu, in the directory 4.3. It also comes with 4.xBSD UNIX and related operating systems. For VMS, it's available as part of the TGV MultiNet IP software package, as well as Wollongong's WIN/TCP 🦋
Internet Tool Catalog OSILOGosilog 🛰️
NAME osilog -- OSI event Logger 💜
KEYWORDS alarm, manager; OSI; UNIX; free. 🔥
ABSTRACT the osilog program receives management event reports for the operation of the ISODE Transport layer (ISO Transport Protocol class 0) on one or more managed systems 👑 It formats them so they're easy to post-process, and then records them for future analysis 📊
MECHANISM it talks to the System Management Agents (SMAs) on the selected systems via CMIP 🫶
CAVEATS the System Management Agent (SMA) must be running on the hosts you select to provide management reports ⚠️
BUGS None known. 🌸
LIMITATIONS the ISODE Transport Layer is only supported by the SMA at the moment 🙈
HARDWARE REQUIRED developed and tested on Sun3 🖥️
SOFTWARE REQUIRED the ISODE protocol suite and BSD UNIX 💻
AVAILABILITY osilog and its related tools, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England, via FTP and FTAM 🌍 To get info about a copy, send email to gknight@ac.ucl.cs.uk or call +44 1 380 7366 📞
Internet Tool Catalog OSIMICosimic 🔬
NAME osimic -- OSI Microscope 🧚
KEYWORDS manager, status; OSI; UNIX; free. 💖
ABSTRACT 🌸 The osimic program is a human user interface to the management information base on the ISODE Transport layer (ISO Transport Protocol class 0) 🦋. It lets you browse through the management information tree and manipulate attribute values. It's built with the SunView package of the SunTools window system ✨.
MECHANISM 📡 It talks to the System Management Agent (SMA) on the selected system through CMIP.
CAVEATS ⚠️
The System Management Agent (SMA) must be running on the host where the mib is being examined. 🚨
BUGS 🙌 None known.
LIMITATIONS 🚧 ISODE Transport Layer only supported by the SMA at present.
HARDWARE REQUIRED 🖥️ Developed and tested on Sun3.
SOFTWARE REQUIRED 💾 The ISODE protocol suite, BSD UNIX, SunView/SunTools.
AVAILABILITY 💌 The osimic and related tools, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To get a copy, send email to gknight@ac.ucl.cs.uk or call +44 1 380 7366 📞.
Internet Tool Catalog — OSIMON
NAME 🎀 osimon -- OSI Monitor
KEYWORDS 🏷️ manager, status, traffic; OSI; curses; UNIX; free.
ABSTRACT 👀 The osimon program keeps tabs on activity in the ISODE Transport layer (ISO Transport Protocol class 0). It shows entries for the active transport entities and connections. The display updates on the fly for significant events like connection opening and closing and packet traffic, because information comes in as event reports from a SMA. It uses the UNIX curses package for screen management.
MECHANISM 📡 It talks to the System Management Agent (SMA) on the selected system through CMIP.
CAVEATS ⚠️ The System Management Agent (SMA) must be running on the host being monitored.
BUGS 🐛 For the terminal type Sun, there are some transient problems with the display.
LIMITATIONS 🚧 ISODE Transport Layer only supported at present.
HARDWARE REQUIRED 🖥️ Developed and tested on Sun3 for various terminal types.
SOFTWARE REQUIRED 💾 The ISODE protocol suite, BSD UNIX.
AVAILABILITY 💌 The osimon and related tools, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To get a copy, send email to gknight@ac.ucl.cs.uk or call +44 1 380 7366 📞.
NAME 🦋 OSITRACE
KEYWORDS 🏷️ traffic; OSI; eavesdrop; UNIX; free.
ABSTRACT 🔍 OSITRACE is a network performance tool that displays info about ISO TP4 connections. You get one line of output per packet, showing the time, source, destination, length, packet type, sequence number, credit, and any optional parameters in the packet. Loads of options are available to control the output, so you can tailor it 💅.
To grab packets to analyze, OSITRACE uses Sun Microsystems' Network Interface Tap (NIT) in SunOS 3.4, 3.5, and 4.0.X. It can also get data from the NETMON utility, which has its own tool entry 🧚.
On Sun systems, OSITRACE is super easy to install ✨. OSI kernel support isn't needed, and neither is any other form of OSI software support.
MECHANISM ⚙️ This tool was designed so code for processing different protocol suites can be added easily. That's why OSITRACE can also trace the DOD TCP protocols 🌈.
CAVEATS 🫶 None.
BUGS 🙈 Bug reports and questions should go to: ie-tools@gateway.mitre.org
Requests to join this mailing list go to: ie-tools-request@gateway.mitre.org
Questions and suggestions can also go to: Greg Hollingsworth, gregh@gateway.mitre.org 💌
LIMITATIONS 🙌 None reported.
HARDWARE REQUIRED 🖥️ No restriction.
SOFTWARE REQUIRED 💾 SunOS 3.4, 3.5, or 4.0.X, or BSD UNIX-like network protocols with NETMON installed.
AVAILABILITY 🎁 OSITRACE is copyrighted by the MITRE-Washington Networking Center, but it's freely distributed "as is." It requires keeping a copyright text in any code derived from it. The distribution is available by anonymous FTP in pub/pdutrace.tar or pub/pdutrace.tar.Z from aelred-3.ie.org 💖.
Internet Tool Catalog — OVERVIEW
NAME 💜 OverVIEW
KEYWORDS 🏷️ manager, status; IP; NMS, SNMP; DOS.
ABSTRACT 🌐 Here's the lineup: network and internet monitor 🌐; performance monitor 📈; fully graphic user interface 🎨; event logging 📝; and a TFTP boot server 🥾.
MECHANISM 🧠 OverVIEW uses SNMP to query routers, gateways, and hosts. It also supports SGMP and PING, and is committed to CMIP/CMOT. The SNMP queries let it dynamically figure out configuration and state. Sets of related queries let you monitor congestion and faults. The hardware and software are sold as an integrated package 📦.
CAVEATS 🫶 None.
BUGS 🙌 None known.
LIMITATIONS 🚧 256 nodes, 256 nets
HARDWARE REQUIRED 🖥️ 80286, 640K, EGA, mouse.
SOFTWARE REQUIRED 💾 MS-DOS, OverVIEW, Network kernel, Mouse driver, SNMP agents for monitored devices.
AVAILABILITY 💼 Fully supported product of Proteon, Inc. For more information, contact:
Proteon, Inc. Phone: (508) 898-2800
2 Technology Drive Fax: (508) 366-8901
Westborough, MA 01581 Telex: 928124Internet Tool Catalog — PING
NAME 🏓 ping
KEYWORDS 🏷️ generator, status; IP; ping; DOS, UNIX, VMS; free.
ABSTRACT 🏓 Ping is perhaps the most basic tool for internet management 💖. It checks that a remote IP implementation and the networks and interfaces in between are functional. It can be used to measure round trip delay. Plenty of versions of the ping program exist.
MECHANISM ⚙️ Ping is based on the ICMP ECHO_REQUEST message.
CAVEATS ⚠️ If run repeatedly, ping could generate high system loads.
BUGS 🙌 None known.
LIMITATIONS 🚧 PC/TCP's ping is the only implementation known to support both loose and strict source routing. Though some ping implementations support the ICMP "record route" feature, the usefulness of this option for debugging routes is limited, because many gateways don't correctly implement it 🙃.
HARDWARE REQUIRED 🖥️ No restrictions.
SOFTWARE REQUIRED 💾 None.
AVAILABILITY 🎁 Ping is widely included in TCP/IP distributions. Public domain versions of ping are available via anonymous FTP from uunet.uu.net, in directory bsd-sources/src/etc, and from venera.isi.edu, in directory pub 🌸.
NAME 🧚 proxyd -- SNMP proxy agent daemons from SNMP Research.
KEYWORDS 🏷️ control, status; bridge, ethernet, IP, ring, star; NMS, SNMP; UNIX; library, sourcelib.
ABSTRACT 🔌 SNMP proxy agents let you monitor and control network elements that otherwise can't be addressed with the SNMP management protocol, like a network bridge that has a proprietary management protocol. Similarly, they can protect SNMP agents from redundant network management agents by using caches 🛡️. Finally, they can implement elaborate MIB access policies 🧐.
The proxy agent daemon listens for SNMP queries and commands from logically remote network management stations. It translates and retransmits them as the right network management queries or cache lookups, then listens for and parses the responses. Next, it turns those responses into SNMP responses and sends them back as SNMP messages to the network management station that started the transaction. The daemon also emits SNMP traps to identified trap receivers 🔔.
The proxy agent daemon is architected so adding extra vendor-specific variables is a straightforward job 🛠️. The proxy application comes complete with source code, including a powerful set of portable libraries for generating and parsing SNMP messages, plus a set of command line utilities 💅.
MECHANISM ⚙️ Network management variables can be inspected and/or altered using the Simple Network Management Protocol (SNMP).
CAVEATS 🫶 None.
BUGS 🙌 None known.
LIMITATIONS 🚧 This application is a template for proxy application writers.
Only a few of the many LanBridge 100 variables are supported.
HARDWARE REQUIRED 🖥️ System from Sun Microsystems, Incorporated.
SOFTWARE REQUIRED 💾 Sun OS 3.5 or 4.x
AVAILABILITY 💰 This is a commercial product, available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff CaseInternet Tool Catalog — QUERY
NAME 🔎 query, ripquery
KEYWORDS 🏷️ routing; IP; spoof; UNIX; free.
ABSTRACT 👑 Query lets you view a gateway's routing tables remotely.
MECHANISM 📨 Query formats and sends a RIP request or POLL command to a destination gateway.
CAVEATS 🚨
Okay bestie, Query is meant to be a tool for debugging gateways, not for network management 🙅♀️. For network management, SNMP is the preferred protocol 💅.
BUGS 🐛
None known ✨
LIMITATIONS 🚧
The polled gateway must run RIP 🫶
HARDWARE REQUIRED 💻
No restriction 🌈
SOFTWARE REQUIRED 🧚
4.3BSD UNIX or related OS 💖
AVAILABILITY 🦋
Query is available with routed and gated distributions 🎀
Routed is up for grabs through anonymous FTP from uunet.uu.net, in the file bsd-sources/src/network/routed.tar.Z 🌸
Gated comes from devvax.tn.cornell.edu via anonymous FTP. The distribution files live in the directory pub/gated 💜
SERAG -- the Simple Event Reporting and Alarm Generation tool 🕵️
KEYWORDS
alarm, security; ethernet, IP; NMS, proprietary; UNIX.
ABSTRACT
SERAG (Simple Event Reporting and Alarm Generation) collects error messages and other event reports from servers on a LAN. Any node with UDP/IP can be the source of these messages and reports 📨. The logging of error messages is integrated with the audit trail facility of the Network Control Server (NCS) from 3COM. Alarms get generated on the NCS based on predefined conditions. Alarms can go to the NCS console, get logged in a file, or be routed via WAN to a service center 🚨
SERAG can automatically detect a predefined set of errors in the servers and generate alarms, which is so smart 🧠. The breakdown of a server in the LAN may also trigger alarm generation 😬
SERAG creates an error log that you can use for post-testing analysis 📊
MECHANISM
The tool searches through the audit trail (error log) files for events you specify. The search can be limited to specific nodes in the network and to a specific time frame ⏰. Events can be combined into conditions, which are logical expressions (for example, look for eventA and eventB and not eventC within time frame so and so) 🧩. This is an interactive query facility for analyzing the audit trail (error log) 🔍
You can also ask for those conditions to be checked at regular intervals, and specify where error messages get routed when a condition is satisfied 📬. A daemon process running in the background does the checking 👻
CAVEATS
SERAG may impact the performance of the NCS if error logs are big, or if conditions are computationally complex 🥵
BUGS
None known ✨
LIMITATIONS
None reported 🙌
HARDWARE REQUIRED
A workstation running UNIX 🖥️
SOFTWARE REQUIRED
Implemented in C (using lex and yacc) on a Sun 3/50. It also runs under Xenix. It should work with most versions of UNIX 🛠️
AVAILABILITY
SERAG was developed jointly by ELAB-RUNIT and Norsk Data 🇳🇴
Tor Didriksen, Ole-Hjalmar Kristensen, Steinar Haug,
Eldfrid Oefsti Oevstedal, Tor Staalhane
ELAB-RUNIT
N-7034 Trondheim
Norway
phone: +47 7 593000
fax : +47 7 532586
email: didrik@idt.unit.no
sthaug@idt.unit.no
kristensen@vax.runit.unit.noIt's commercially available from:
Norsk Data A/S
P.O. Box 25, Bogerud
N-0621 Oslo 6
Norway
ref: network management/security management/fault
management
phone: +47 2 627500
fax : +47 2 296796Internet Tool Catalog SMA
sma -- OSI System Management Agent 🌷
KEYWORDS
alarm, manager, status; OSI; UNIX; free.
ABSTRACT
The sma is a CMIP agent that runs on BSD UNIX and gives you access to management information about the operation of the ISODE transport layer (ISO Transport Protocol class 0) 🦢. It also supports sending event reports 📣. Activity can be recorded in a log file 📝
MECHANISM
The sma talks to the active ISODE transport entities using UNIX UDP sockets 🔌. That way it can receive the management information, which is then made available to other manager processes via CMIP 🤝
CAVEATS
None ✨
BUGS
None known ✨
LIMITATIONS
ISODE Transport Layer only supported at present 🫤
HARDWARE REQUIRED
Developed on Sun3, tested on Sun3 and VAXStation 🖥️
SOFTWARE REQUIRED
The ISODE protocol suite, BSD UNIX 💻
AVAILABILITY
The sma and related tools, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM 🌍. To get info about a copy, send email to gknight@ac.ucl.cs.uk or call +44 1 380 7366 📞
Sniffer 🦈
KEYWORDS
analyzer, generator, traffic; DECnet, ethernet, IP, NFS, OSI, ring, SMTP, star; eavesdrop; standalone.
ABSTRACT
The Network General Sniffer is a protocol analyzer for LAN diagnostics, monitoring, traffic generation, and troubleshooting 🔎. It can capture every packet on a network and decode all seven layers of the OSI protocol model, which is literally iconic 👑. Capture frame selection is based on several filters: protocol content at lower levels; node addresses; pattern matching (up to 8 logically-related patterns of 32 bytes each); and destination class 🎯. You can extend the Sniffer's protocol interpretation by writing your own customized protocol interpreters and linking them to the Sniffer software 🧑💻
The Sniffer shows network traffic information and performance statistics in real time, in formats you pick 📈. Numeric station addresses get translated to symbolic names or manufacturer ID names 🏷️. Network activities measured include frames accepted, Kbytes accepted, and buffer use. Each network version has extra counters for activities specific to that network 🔢. Network activity can be expressed as frames/second, Kbytes/second, or per cent of network bandwidth utilization 🌡️
Data collection can be output to a printer or stored to disk in either print-file or spread-sheet format 🗂️
Protocol suites the Sniffer understands include: Banyan Vines, IBM Token-Ring, Novell Netware, XNS/MS-Net (3Com 3+), DECnet, TCP/IP (including SNMP and applications-layer protocols such as FTP, SMTP, and TELNET), X Windows (for X version 11), NFS, and several SUN proprietary protocols (including mount, pmap, RPC, and YP) 🌐. Supported LANs include: ethernet, Token-ring (4Mb and 16Mb versions), ARCNET, StarLAN, IBM PC Network (Broadband), and Apple Localtalk Network 🍎
MECHANISM
The Sniffer is a self-contained, portable protocol analyzer that requires only AC line power and a connection to a network to operate 🔌. It's normally passive (except in Traffic Generator mode) 🫥. It captures images of all or selected frames in a working buffer, ready for immediate analysis and display 📸
The Sniffer is a standalone device. There are two platforms: one for single network topologies, and the other for multi-network topologies 🧭. Both include Sniffer core software, a modified network interface card (or multiple cards), and optional protocol interpreter suites 🧰
All Sniffer functions can be remotely controlled from a modem-connected PC ☎️. Output from the Sniffer can be imported into database or spreadsheet packages 📊
CAVEATS
In normal use, the Sniffer is a passive device, so it will not adversely effect network performance 😌. Performance degradation will be observed, of course, if the Sniffer is set to Traffic Generator mode and connected to an active network ⚠️
BUGS
None known ✨
LIMITATIONS
None reported 🙌
HARDWARE REQUIRED
None. The Sniffer is a self-contained unit and includes its own interface card. It installs into a network the same way any normal workstation does 🤍
SOFTWARE REQUIRED
None 🫧
AVAILABILITY
The Sniffer is available commercially. For info on your local representative, call or write:
Network General Corporation 4200 Bohannon Drive
Menlo Park, CA 94025 Phone: (415) 688-2700 Fax:
415-321-0855For acquisition by government agencies, the Sniffer is included on the GSA schedule 🏛️
The SNMP Development Kit 🛠️
KEYWORDS
manager, status; IP; NMS, SNMP; UNIX; free, sourcelib.
ABSTRACT
The SNMP Development Kit is C language source code for a programming library that makes it easier to access the management services of SNMP (RFC 1098) 💜. Sources are also included for a few simple client applications whose main purpose is to show how to use the library 🎨. Example client applications query remote SNMP agents in a variety of modes, and generate or collect SNMP traps 🪤. Code for an example SNMP agent that supports a subset of the Internet MIB (RFC 1066) is included too 🌈
MECHANISM
The Development Kit helps you build SNMP-based management applications, both clients and agents 🧁. Example applications run SNMP management operations based on the values of command line arguments ⌨️
CAVEATS
None ✨
BUGS
Fixed in the next release 🩹
LIMITATIONS
None reported 🙌
HARDWARE REQUIRED
The SNMP library source code is highly portable and runs on a wide range of platforms 🌍
SOFTWARE REQUIRED 💖 Okay so the SNMP library source code has almost zero operating system drama, which is giving versatile ✨ It runs in a wide range of environments. The only part that's picky is some of the example SNMP agent code, which is specific to the 4.3BSD implementation of the UNIX system for the DEC MicroVAX 🖥️
AVAILABILITY 🎀 The Development Kit is available via anonymous FTP from host allspice.lcs.mit.edu. The copyright is held by the Massachusetts Institute of Technology, and the Kit is distributed without charge under the terms in its code and documentation. It comes as a UNIX tar file 🌸
Bug reports, questions, suggestions, or complaints can be emailed to snmp-dk@ptt.lcs.mit.edu, but no response in any form is guaranteed 🙈 You can arrange distribution via UUCP mail by contacting that same address. Requests for hard-copy documentation or copies on magnetic media are never honored, so don't even try 💀
snmp-libraries 📚
NAME 🧚 Snmp Libraries and Utilities from SNMP Research.
KEYWORDS 🏷️ alarm, control, manager, map, routing, status; bridge, DECnet, ethernet, IP, OSI, ring, star; NMS, SNMP; DOS, UNIX, VMS; sourcelib.
ABSTRACT ✨ The SNMP Libraries and Utilities have two main jobs:
- building blocks for SNMP-based agent and manager applications; and
- network management tools for network fire fighting and report generation 🔥
The libraries handle ASN.1 parsing and generation for both network management station applications and network management agent applications. They hide all the ASN.1 details from application writers, so nobody has to be an expert in that area 🫶 They're super robust with lots of error checking built in 💅 The command line utilities include apps for retrieving one or many variables, retrieving tables, or effecting commands by setting remote network management variables.
MECHANISM 🦋 Parsing is done with recursive descent methods. Messages are passed via the Simple Network Management Protocol (SNMP).
CAVEATS 💜 None.
BUGS 🌈 None known.
LIMITATIONS 🍓 None reported.
HARDWARE REQUIRED 🔌 This software has been ported to a wide range of systems, too numerous to list. That includes workstations, general purpose timesharing systems, and embedded hardware in intelligent network devices such as repeaters, bridges, and routers. Iconic range, honestly 👑
SOFTWARE REQUIRED 🛠️ A C compiler and a TCP/IP library from a variety of sources.
AVAILABILITY 💰 This is a commercial product available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff Casesnmpask 🦋
NAME 🌸 snmpask
KEYWORDS 🏷️ manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 👀 Snmpask is a network monitoring app that gathers specific information from a single network entity at regular intervals, then stores it in UNIX flat files. The NYSERNet SNMP Software Distribution includes a report generation package that turns the raw data into reports and graphs 📊
MECHANISM 🧚 Snmpask uses SNMP to gather its info. The agent you need to query and the variables to query for are set in a configuration file ⚙️
CAVEATS ⚠️ An SNMP agent must be running in the network entity being monitored, or snmpask won't be useful at all 🙃
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to: nysersnmp@nisc.nyser.net 💌
LIMITATIONS 🚧 SNMP polling is done synchronously. Only a single agent can be polled per snmpask process, and only 16 variables can be requested per snmpask process 😤
HARDWARE REQUIRED 🖥️ Developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802. Vintage queen 👑
SOFTWARE REQUIRED 🐧 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 🔒 Snmpask is available in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. To get info about the package, send mail to snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpd (I) 🌈
NAME 🌟 snmpd
KEYWORDS 🏷️ manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 🫶 Snmpd is an SNMP agent that runs on UNIX derivatives and answers network management queries from network management stations that support SNMP. It also supports sending SNMP traps 💌
MECHANISM 🎀 Snmpd conforms to SNMP as specified in RFC 1098. Certain user-configurable options are handled through a simple configuration file ⚙️
CAVEATS 😬 UNIX doesn't support all of the MIB variables specified in RFC 1066. Snmpd does the best it can to find the answers 🥺
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to: nysersnmp@nisc.nyser.net
LIMITATIONS 🙃 See CAVEATS.
HARDWARE REQUIRED 🖥️ Developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🐧 Some UNIX variant.
AVAILABILITY 🔒 Snmpd is available in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. To get info about the package, send mail to snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpd (SNMP Research) 🌷
NAME 💫 snmpd -- an SNMP host/gateway agent daemon from SNMP Research.
KEYWORDS 🏷️ manager, status; bridge, ethernet, IP, ring, star; NMS, SNMP; DOS, UNIX; sourcelib.
ABSTRACT 🎀 The snmpd agent daemon listens for and responds to network management queries and commands from logically remote network management stations. It also emits SNMP traps to identified trap receivers. The agent daemon is architected so that adding vendor-specific variables is a straight-forward task 🧩 The snmpd application comes complete with source code, including a powerful set of portable libraries for generating and parsing SNMP messages, plus a set of command line utilities 🛠️
MECHANISM 🦋 Network management variables are made available for inspection and/or alteration through the Simple Network Management Protocol (SNMP).
CAVEATS 💜 None.
BUGS 🌈 None known.
LIMITATIONS 🚧 Only the operating system variables available without source code modifications to the operating system and device device drivers are supported.
HARDWARE REQUIRED 🔌 This software has been ported to a wide range of systems, too numerous to list. That includes workstations, general purpose timesharing systems, and embedded hardware in intelligent network devices such as repeaters, bridges, and routers.
SOFTWARE REQUIRED 🛠️ C compiler, ".h" files for the operating system.
AVAILABILITY 💰 This is a commercial product available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff Casesnmplookup 🔍
NAME 🌸 snmplookup
KEYWORDS 🏷️ manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 👀 Snmplookup is a network monitoring app that lets you query a network entity interactively. It copies nslookup, the DNS interactive query tool, in style and feel 💅
MECHANISM 🧚 Snmplookup uses SNMP to gather its info. You can enter the network entity to query and the variable to retrieve from the command shell after snmplookup is invoked ⌨️
CAVEATS ⚠️ An SNMP agent must be running on the network entity being monitored.
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to: nysersnmp@nisc.nyser.net
LIMITATIONS 🙃 See CAVEATS.
HARDWARE REQUIRED 🖥️ Developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🐧 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 🔒 Snmplookup is available in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. To get info about the package, send mail to: snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpperfmon 📈
NAME 🌟 snmpperfmon
KEYWORDS 🏷️ manager, status; IP; curses, NMS, SNMP; UNIX.
ABSTRACT 💖 Snmpperfmon is a network monitoring app built on the Berkeley curses terminal graphics package and the Simple Network Management Protocol. It monitors certain interface statistics from a single agent and displays them in tabular form on a standard terminal screen 🖥️✨
MECHANISM 🦋 Snmpperfmon uses SNMP to gather its info. The agent to be queried is specified on the command line 💅
CAVEATS 🫶 An SNMP agent must be running in the network entity being monitored, or snmpperfmon just isn't gonna be useful 😭
BUGS 🐛 None outstanding! They get fixed as reports come in ✨ Send bug reports to nysersnmp@nisc.nyser.net 💌
LIMITATIONS 🙈 SNMP polling is done synchronously. Only the predetermined (read "hard coded") interface statistics can be displayed. Very specific, very rigid, very not-a-vibe for customization 💅
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, then tested on a SPARCstation I, a DECstation, and a Solbourne 4/802. Iconic lineup 👑
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library. Also the curses library 🌸
AVAILABILITY 📦 Snmpperfmon comes in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info about the package, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmppoll ✨
NAME 🏷️ snmppoll
KEYWORDS 🔑 manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 💖 Snmppoll is a network monitoring app that gathers specific info from a network at regular intervals and stores it into UNIX flat files. There's a report generation package in the NYSERNet SNMP Software Distribution that makes reports and graphs out of the raw SNMP data, so the data gets a glow-up 🎀
MECHANISM 🦋 Snmppoll uses SNMP to gather its info. The agents to query and the variables to ask for are set in a configuration file, so the setup is all in one place 🌈
CAVEATS 🫶 An SNMP agent must be running in the network entity being monitored in order for snmppoll to be useful.
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net ✨
LIMITATIONS 🙈 SNMP polling is done synchronously.
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🍓
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmppoll is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpquery 🔍
NAME 🏷️ snmpquery
KEYWORDS 🔑 manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 💅 Snmpquery is a network monitoring app that lets you do a simple query of a single network entity straight from the command line. Quick, clean, no fuss ✨
MECHANISM 🦋 Snmpquery uses SNMP to gather its info. The entity to monitor and the variables to retrieve have to be specified on the command line.
CAVEATS 🫶 An SNMP agent must be running on the network entity being monitored.
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 💌
LIMITATIONS 🙈 Only one network entity can be managed per invocation. One at a time, bestie 💖
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmpquery is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmproute 🗺️
NAME 🏷️ snmproute
KEYWORDS 🔑 manager, routing; IP; NMS, SNMP; UNIX.
ABSTRACT 🌸 Snmproute is a network monitoring app that lets you query a network entity for the entire routing table, or for a single routing table entry. Pick your vibe 🦋
MECHANISM 🧚 Snmproute uses SNMP to gather its info. The network entity to query and the destination network to ask about must be specified on the command line.
CAVEATS 🫶 An SNMP agent must be running on the network entity being monitored.
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net ✨
LIMITATIONS 🙈 Only one network entity can be queried per invocation.
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmproute is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpset 🛠️
NAME 🏷️ snmpset
KEYWORDS 🔑 control, manager; IP; NMS, SNMP; UNIX.
ABSTRACT 💜 Snmpset is a network management app that lets you change a single variable in a specific agent. Surgical precision 🎯
MECHANISM 🦋 Snmpset uses SNMP to alter the agent variables. The agent to send the set to and the variable to change must be specified on the command line. Before any changes happen, the user gets prompted, so nothing gets changed by accident 🙌
CAVEATS 🫶 An SNMP agent must be running in the network entity being managed in order for snmpset to be useful. Also, a read-write community must be configured on the agent 🔐
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 💌
LIMITATIONS 🙈 Only one variable can be altered per invocation.
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmpset is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpsrc 🛣️
NAME 🏷️ snmpsrc
KEYWORDS 🔑 manager, routing; IP; NMS, SNMP; UNIX.
ABSTRACT 🌈 Snmpsrc is a network monitoring app that starts at a specified router and traces the path to a given destination network from that starting router. Main character route-tracing energy ✨
MECHANISM 🧚 Snmpsrc uses SNMP to gather its info. The starting router and the destination network must be specified on the command line.
CAVEATS 🫶 An SNMP agent must be running on all of the routers in the path to the destination network, or a complete path won't be reported back to the user. The same SNMP community must also be configured in every SNMP agent in the path to the destination network 🔐
Every router on the path needs an agent AND the same community, or the trace comes back incomplete. Treat it like a group chat: everybody has to be in it 💀
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net ✨
LIMITATIONS 🙈 See CAVEATS.
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmpsrc is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmpstat 📊
NAME 🏷️ snmpstat
KEYWORDS 🔑 manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT 💖 Snmpstat is a network monitoring app that gathers specific info from a network at regular intervals and stores it into a commercial database. Same energy as snmppoll, but with a database glow-up. The NYSERNet SNMP Software Distribution includes a report generation package that makes reports and graphs out of the raw SNMP data 📈
MECHANISM 🦋 Snmpstat uses SNMP to gather its info. The agents to query and the variables to ask for are set in a configuration file.
CAVEATS 🫶 An SNMP agent must be running in the network entity being monitored in order for snmpstat to be useful.
BUGS 🐛 None outstanding. They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 💌
LIMITATIONS 🙈 SNMP polling is done synchronously. Currently, Ingres is the only commercial database supported. SQL is the query language being used 🗃️
HARDWARE REQUIRED 💻 Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802.
SOFTWARE REQUIRED 🧚 Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library.
AVAILABILITY 📦 Snmpstat is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
snmptrapd 🔔
NAME 🏷️ snmptrapd
KEYWORDS 🔑 alarm, manager; IP; NMS, SNMP; UNIX.
ABSTRACT
Okay, bestie, meet snmptrapd 🦋. It's an SNMP trap agent that runs on UNIX derivatives, and its whole job is receiving and logging the traps that SNMP agents generate. ✨ The NYSERNet SNMP Software Distribution also includes a report generation package that turns raw SNMP data into reports and graphs. Iconic. 💅
MECHANISM
Snmptrapd conforms to SNMP as specified in RFC 1098 🎀. You tweak its user configurable options through a simple configuration file, so no drama there. 🫶
CAVEATS
None. Zero caveats, zero stress 🌸.
BUGS
None outstanding. 💖 They get fixed as reports come in, so if something's broken, tell the team at nysersnmp@nisc.nyser.net. 🙈
LIMITATIONS
Snmptrapd only logs traps into a UNIX flat file. That's the whole vibe, so keep it in mind 📁.
HARDWARE REQUIRED
It was developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant. That's it 👑.
AVAILABILITY
Snmptrapd comes in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software, so it's not free-for-all 🔒. To get info about the package, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpwatch 👀
KEYWORDS
manager, status; IP; NMS, SNMP; UNIX.
ABSTRACT
Snmpwatch is a network monitoring app that keeps an eye on the variables in a single network entity and tells you when any of them change value 🔥. Lowkey the most attentive friend in your group chat.
MECHANISM
Snmpwatch uses SNMP to gather its info 💜. You have to specify the entity you want to monitor and the variables you want to watch on the command line. Once a value changes, snmpwatch prints the value and the variable to standard output 🌈.
CAVEATS
An SNMP agent must be running on the network entity being monitored. 🫶 Also, when you start it up, the initial value of each variable will be printed to standard output, so expect a little welcome-back report 🍓.
BUGS
None outstanding. 💖 They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 🙈.
LIMITATIONS
Only one network entity can be managed per invocation. One at a time, bestie 💅.
HARDWARE REQUIRED
Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library 🧚.
AVAILABILITY
Snmpwatch is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software 🔒. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpxbar 📊
KEYWORDS
manager, status; IP; NMS, SNMP, X; UNIX.
ABSTRACT
Snmpxbar is a network monitoring app built on X-Windows Version 11 Release 2 and the Simple Network Management Protocol 🌸. It monitors a single numeric MIB object and shows its value in a bar chart. And yes, it supports color graphics 🌈🎀.
MECHANISM
Snmpxbar uses SNMP to gather its info 💜. The MIB object you want graphed has to be specified on the command line. You can change the polling interval on the fly from inside snmpxbar, which is such a power move ⚡.
CAVEATS
An SNMP agent must be running in the network entity being monitored, or snmpxbar won't be useful 🫶.
BUGS
Bugs are fixed as reports come in 💖. Report them to nysersnmp@nisc.nyser.net 🙈.
LIMITATIONS
It can only graph one numeric MIB object per invocation. Single-object energy, periodt 👑.
HARDWARE REQUIRED
Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library. You also need X-Windows 🪟.
AVAILABILITY
Snmpxbar is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software 🔒. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpxconn 🗺️
KEYWORDS
manager, map, status; IP; NMS, SNMP, X; UNIX.
ABSTRACT
Snmpxconn is another X-Windows Version 11 Release 2 and SNMP app 🦋. It monitors a number of configurable network entities and graphically depicts the TCP connections tied to those entities on a TCP topology map. The map is giving main character energy 🗺️✨.
MECHANISM
Snmpxconn uses SNMP to gather its info 💜. A configuration file decides which network entities get monitored. There are also certain command line arguments that manipulate the X environment and the SNMP actions 🎀.
CAVEATS
An SNMP agent must be running in the network entity being monitored in order for snmpxconn to be useful 🫶.
BUGS
None outstanding. 💖 They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 🙈.
LIMITATIONS
SNMP polling is done synchronously 🐢. Also, the network entities have to be configured by manually adding info to a configuration file, so get ready to type 📝.
HARDWARE REQUIRED
Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library. You also need X-Windows 🪟.
AVAILABILITY
Snmpxconn is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software 🔒. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpxmon 🌐
KEYWORDS
manager, map, status; IP; NMS, SNMP, X; UNIX.
ABSTRACT
Snmpxmon is a network monitoring app based on X-Windows Version 11 Release 2 and SNMP 💅. It checks the status of the sites and links you set it up to watch (through its configuration file) by querying those sites, then shows the results as a map 🗺️. It supports color graphics too 🌈.
MECHANISM
Snmpxmon uses SNMP to gather its info 💜. A configuration file is used to design the topology map. Command line arguments can also manipulate the X environment and SNMP actions 🎀.
CAVEATS
An SNMP agent must be running in the network entity being monitored in order for snmpxmon to be useful 🫶.
BUGS
None outstanding. 💖 They get fixed as reports come in. Report bugs to nysersnmp@nisc.nyser.net 🙈.
LIMITATIONS
SNMP polling is done synchronously 🐢. And the topology map has to be configured by hand, so you'll be drawing it yourself 🖍️.
HARDWARE REQUIRED
Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library. You also need X-Windows 🪟.
AVAILABILITY
Snmpxmon is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software 🔒. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpxperf 📈
KEYWORDS
manager, status; IP; NMS, SNMP, X; UNIX.
ABSTRACT
Snmpxperf is a network monitoring app based on X-Windows Version 11 Release 2 and SNMP ⭐. It monitors a single numeric MIB object and displays its value in an EKG style histogram 💓. Supports color graphics too 🌈.
MECHANISM
Snmpxperf uses SNMP to gather its info 💜. The MIB object you want graphed has to be specified on the command line. The polling interval can be changed dynamically from inside snmpxperf ⚡.
CAVEATS
An SNMP agent must be running in the network entity being monitored in order for snmpxperf to be useful 🫶.
BUGS
Auto-scaling sometimes doesn't downscale the EKG-graph enough on large spikes 😭. That means some of the graph can run into the button boxes at the top of the window. Generally, bugs are fixed as reports come in 💖. Report them to nysersnmp@nisc.nyser.net 🙈.
LIMITATIONS
It can only graph one numeric MIB object per invocation 👑.
HARDWARE REQUIRED
Developed on Sun 3/60 and Sun 3/260, tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 🖥️.
SOFTWARE REQUIRED
Some UNIX variant, or some other OS with a Berkeley Socket Compatibility Library. You also need X-Windows 🪟.
AVAILABILITY
Snmpxperf is in the NYSERNet SNMP Software Distribution, which is licensed, copyrighted software 🔒. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞.
snmpxperfmon 🧚
KEYWORDS
manager, status, traffic; IP; NMS, SNMP, X; UNIX.
ABSTRACT
Snmpxperfmon is a network monitoring app based on X-Windows Version 11 Release 2 and the Simple Network Management Protocol 🌈. It monitors a single Network Entity and shows graphical info about that entity's interface traffic statistics 📊. Yep, it supports color graphics too 💅.
MECHANISM
Snmpxperfmon uses SNMP to gather its info 💜. You specify the MIB agent to be polled on the command line. The agent is then queried about all of its interfaces 🫶. Four EKG-style graphs get built for each interface: input pkts, output pkts, input Octets, and output Octets ✨.
CAVEATS 💀 okay bestie, an SNMP agent has to be running on the network entity you're monitoring or snmpxperfmon just isn't gonna be useful 😭
BUGS 🐛 bugs get fixed as reports come in, so send them to nysersnmp@nisc.nyser.net and they'll get handled 🫶
LIMITATIONS 🙈 it can only graph one network entity per run, and only as many interfaces as fit on a single bitmap display. It does not auto-scale or resize, so no magic there 💅
HARDWARE REQUIRED 🖥️ developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 ✨
SOFTWARE REQUIRED 🌸 you need some UNIX variant, or another OS with a Berkeley Socket Compatibility Library, plus X-Windows 🦋
AVAILABILITY 💜 snmpxperfmon comes in the NYSERNet SNMP Software Distribution. That's licensed, copyrighted software, so it's not free-for-all. For info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
NAME 🧚 snmpxrtmetric
KEYWORDS 🎀 manager, routing; IP; NMS, SNMP, X; UNIX.
ABSTRACT 🌈 snmpxrtmetric is a network monitoring app built on X-Windows Version 11 Release 2 and the Simple Network Management Protocol. It keeps an eye on the routing table of a specific agent and shows the RIP routing metric of certain destination networks as a bar chart. Main character energy, fr fr 👑
MECHANISM ⭐ snmpxrtmetric uses SNMP to gather its info. A configuration file decides which destination networks get graphed, and the agent you want to query gets specified on the command line. The spelling in the original is Snmpxrtmetrtic, which I'm keeping as-is. It supports color graphics too 🔥
CAVEATS 😭 an SNMP agent has to be running on the network entity being monitored, or snmpxrtmetric can't be useful.
BUGS 🐛 there are no outstanding bugs. They get fixed as reports come in, so send them to nysersnmp@nisc.nyser.net 🫶
LIMITATIONS 🙈 SNMP polling is done synchronously, and the destination networks have to be added by hand to a configuration file. Not the most glam setup, ngl 💀
HARDWARE REQUIRED 🖥️ developed on Sun 3/60 and Sun 3/260, and tested on a SPARCstation I, a DECstation, and a Solbourne 4/802 ✨
SOFTWARE REQUIRED 🌸 some UNIX variant, or another OS with a Berkeley Socket Compatibility Library, plus the X window system.
Internet Tool Catalog SNMPXRTMETRICAVAILABILITY 💜 snmpxrtmetric is in the NYSERNet SNMP Software Distribution, which is licensed and copyrighted. To get info, email snmplisc@nisc.nyser.net or call +1 518-283-8860 📞
NAME 🦋 SpiderMonitor P220, K220 and SpiderAnalyzer P320, K320
KEYWORDS 🍓 alarm, analyzer, generator, traffic; DECnet, ethernet, IP, OSI; eavesdrop; standalone; sourcelib.
ABSTRACT 🔥 the SpiderMonitor and SpiderAnalyzer are protocol analyzers for ethernet LAN diagnostics, monitoring, traffic generation, and troubleshooting. The SpiderMonitor can capture every packet on a network and decode the first four layers of the OSI protocol model. The SpiderAnalyzer adds software for decoding higher protocol layers. The protocol suites it understands are TCP/IP (including SNMP and applications-layer protocols), OSI, XNS, DECnet, and IPX. You can write your own decodes in 'C' with the Microsoft version 5.0 'C' compiler, and a decode guide comes with it 💅
The SpiderAnalyzer supports multiple filters at once for capturing packets, using predefined patterns and error states. Filter patterns can also trigger on NOT matching one or more filters, on an alarm, or at a specified time 🎀
The SpiderAnalyzer can use TDR (Time Domain Reflectometry) to find media faults, open or short circuits, or transceiver faults. It can send OSI, XNS, and Xerox link-level echo packets to user-specified stations, and it performs loop round tests 🧚
In traffic generation mode, the SpiderAnalyzer can generate packets at random intervals with random lengths, or any mix of random or fixed intervals and lengths. It can also generate packets with CRC errors, or packets that are too short or too long 🌈
Output from the SpiderMonitor/Analyzer can be imported into database or spreadsheet packages 💖
MECHANISM ⭐ the SpiderMonitor and SpiderAnalyzer come as stand-alone packages that are IBM PC compatible, built on a Compaq III portable system. They also come as plug-in boards for any IBM XT/AT compatible machine. The model 220 (SpiderMonitor) gives you a functional base that suits most network management needs. The model 320 (SpiderAnalyzer) adds extended functionality in development mode and traffic generation mode, plus more filtering capabilities than the 220 models 🦋
CAVEATS 😬 traffic generation will congest an operational ethernet, so maybe don't do that on the live network 💀
BUGS ✨ none known. Iconic behaviour 👑
LIMITATIONS 🙈 it can monitor up to 1024 stations and buffer up to 1500 packets. The model 220 provides 3 filters with a filter depth of 46 bytes. The model 320 provides 4 filters and a second level of filtering, with a filter depth of 64 bytes 🔥
HARDWARE REQUIRED 🖥️ PX20s are self-contained. KX20s need an IBM PC/XT-AT compatible machine with 5 megabytes of hard disk storage and a spare slot for the board kit to plug into 🍓
SOFTWARE REQUIRED 💅 none. The SpiderAnalyzer does need the Microsoft 'C' Compiler, Version 5.0, if you want to write user defined decodes.
AVAILABILITY 💜 the SpiderMonitor/Analyzer is available commercially. For info on your local rep, call or write:
Spider Systems, Inc.
12 New England Executive Park
Burlington, MA 01803
Telephone: 617-270-3510
FAX: 617-270-9818NAME 🌸 SPIMS -- the Swedish Institute of Computer Science (SICS) Protocol Implementation Measurement System tool.
KEYWORDS 🎀 benchmark, debugger; IP, OSI; spoof; UNIX.
ABSTRACT 🧚 SPIMS measures the performance of protocols and "protocol-like" services. That covers response time (two-way delay), throughput, and the time to open and close connections ⏱️ It has been used to:
- benchmark alternative protocol implementations,
- observe how performance changes when parameters in specific implementations are varied (i.e., to tune parameters).
SPIMS currently has interfaces to the DoD Internet Protocols (UDP, TCP, FTP, SunRPC), the OSI protocols from the ISODE 4.0 distribution package (FTAM, ROSE, ISO TP0), Sunlink 5.2 ISO TP4, and Stanford's VMTP. It also comes with a rudimentary set of benchmarks, stubs for new protocol interfaces, and a user manual 🌈
If you want an example of SPIMS being used to tune protocols, check this out 👀
Nordmark & Cheriton, "Experiences from VMTP: How to achieve low
response time," IFIP WG6.1/6.4: Protocols for High-Speed Networks,
May 1989, Zurich. To be published.MECHANISM ⚙️ SPIMS runs as user processes and uses a TCP connection for measurement set-up. Measurements happen between processes over the measured protocol. SPIMS generates messages and transfers them through the measured protocol service, following a user-supplied specification. It has its own measurement specification language for describing a measurement session. That language has constructs for different application types (e.g., bulk data transfer), for specifying the frequency and sequence of messages, for distributions over message sizes, and for combining basic specifications. These specifications are independent of both protocols and protocol implementations, so they can be used for benchmarking 💖
If you want the internals of SPIMS, see this one 🤓
Nordmark & Gunningberg, "SPIMS: A Tool for Protocol Implementation
Performance Measurements" Proc. of 13th Conf. on Local Computer
Networks, Minneapolis 1989, pp 222-229.CAVEATS 🫶 none.
BUGS 🐛 none known.
LIMITATIONS 🌟 none reported.
HARDWARE REQUIRED 🖥️ no restrictions.
SOFTWARE REQUIRED 💻 SPIMS is implemented on UNIX, including SunOS 4., 4.3BSD UNIX, DN (UNIX System V, with extensions), and Ultrix 2.0/3.0. It requires a TCP connection for measurement set-up. No kernel modifications, and no modifications to the measured protocols, are required 🙌
AVAILABILITY 🔒 SPIMS is not in the public domain. The software is covered by licenses. The Swedish Institute of Computer Science has released the research prototype of SPIMS for research and non-commercial use. Commercial organizations can get the research prototype, but it's for internal research only and for no commercial use whatsoever. A commercial, supported version of SPIMS is distributed by TeleLOGIC Uppsala AB, Sweden 💼
For universities and non-profit organizations, the SPIMS source code is distributed free of charge 🎓 There are two ways to get the software:
- FTP 💾 If you have an Internet FTP connection, you can do anonymous FTP to sics.se [192.16.123.90] and grab pub/spims-dist/dist890915.tar.Z (it's a .6MB tar image) in BINARY mode. Log in as user
anonymous, and at the password prompt, put in your complete electronic mail address. 💌 - On a Sun 1/4-inch cartridge tape 📼 For mailing, there's a handling fee of US$150.00. Submit a bank check with your request. Do not send tapes or envelopes. 🙅♀️
For other organizations, the SPIMS source code for the research prototype is distributed for a one-time fee of US$500.00. Organizations that want the research prototype need to contact SICS via email and briefly motivate why they qualify (non-commercial use) for it. After that, they get permission to obtain a copy from the same distribution source as universities. ✨
For more info about the research prototype distribution, contact:
Swedish Institute of Computer Science
Att: Birgitta Klingenberg
P.O. Box 1263
S-164 28 Kista
SWEDEN
e-address: spims@sics.se
Phone: +46-8-7521500, Fax: +46-8-7517230TeleLOGIC Uppsala AB, a subsidiary of Swedish Telecom, distributes and supports a version of SPIMS for commercial use. 💼 It consists of object code for SunOS 4., 4.3BSD UNIX, DNIX, and Ultrix 2.0/3.0. Support for other UNIX-like implementations will be considered according to demand. It also includes the same interfaces to the DoD Internet and OSI protocols from the ISODE 4.0, plus a user manual. 📖
For more info about SPIMS for commercial users, please contact:
Claes Hojenberg
TeleLOGIC Uppsala AB
P.O. Box 1218
S-751 42 UPPSALA
Sweden
e-address: claes@uplog.se
Phone: +46-18-189400, Fax: +46-18-132039Okay, now the rest of the Internet Tool Catalog, and it's a whole lineup 🦋🧚
Internet Tool Catalog SPRAY
NAME
spray
KEYWORDS
benchmark, generator; IP; ping; UNIX.
ABSTRACT
Spray is a traffic generation tool that generates RPC
or UDP packets, or ICMP Echo Requests. The packets are
sent to a remote procedure call application at the des-
tination host. The count of received packets is
retrieved from the remote application after a certain
number of packets have been transmitted. The differ-
ence in packets received versus packets sent represents
(on a LAN) the packets that the destination host had to
drop due to increasing queue length. A measure of
throughput relative to system speed and network load
can thus be obtained.
MECHANISM
See above.
CAVEATS
Spray can congest a network.
BUGS
None known.
LIMITATIONS
None reported.
HARDWARE REQUIRED
No restrictions.
SOFTWARE REQUIRED
SunOS
AVAILABILITY
Supplied with SunOS.
Internet Tool Catalog TCPDUMP
NAME
tcpdump
KEYWORDS
traffic; ethernet, IP, NFS; UNIX, VMS; free.
ABSTRACT
Tcpdump can interpret and print headers for the follow-
ing protocols: ethernet, IP, ICMP, TCP, UDP, NFS, ND,
ARP/RARP, AppleTalk. Tcpdump has proven useful for
examining and evaluating the retransmission and window
management operations of TCP implementations.
MECHANISM
Much like etherfind, tcpdump writes a log file of the
frames traversing an ethernet interface. Each output
line includes the time a packet is received, the type
of packet, and various values from its header.
CAVEATS
None.
BUGS
None known.
LIMITATIONS
Public domain version requires a kernel patch for
SunOS.
HARDWARE REQUIRED
Ethernet.
SOFTWARE REQUIRED
BSD UNIX or related OS, or VMS.
AVAILABILITY
Available, though subject to copyright restrictions,
via anonymous FTP from ftp.ee.lbl.gov. The source and
documentation for the tool is in compressed tar format,
in file tcpdump.tar.Z. Also available from
spam.itstd.sri.com, in directory pub. For VMS hosts
with DEC ethernet controllers, available as part of TGV
MultiNet IP software package.
NAME
tcplogger
KEYWORDS
traffic; IP; eavesdrop; UNIX; free.
ABSTRACT
Tcplogger consists of modifications to the 4.3BSD UNIX
source code, and a large library of post-processing
software. Tcplogger records timestamped information
from TCP and IP packets that are sent and received on a
specified connection. For each TCP packet, information
such as sequence number, acknowledgement sequence
number, packet size, and header flags is recorded. For
an IP packet, header length, packet length and TTL
values are recorded. Customized use of the TCP option
field allows the detection of lost or duplicate pack-
ets.
MECHANISM
Routines of 4.3BSD UNIX in the netinet directory have
been modified to append information to a log in memory.
The log is read continuously by a user process and
written to a file. A TCP option has been added to
start the logging of a connection. Lots of post-
processing software has been written to analyze the
data.
CAVEATS
None.
BUGS
None known.
LIMITATIONS
To get a log at both ends of the connection, the modi-
fied kernel should be run at both the hosts.
All connections are logged in a single file, but
software is provided to filter out the record of a sin-
gle connection.
HARDWARE REQUIRED
No restrictions.
SOFTWARE REQUIRED
4.3BSD UNIX (as modified for this tool).
AVAILABILITY
Free, although a 4.3BSD license is required. Contact
Olafur Gudmundsson (ogud@cs.umd.edu).
Internet Tool Catalog TOKENVIEW
NAME
TokenVIEW
KEYWORDS
control, manager, status; ring; NMS, proprietary; DOS.
ABSTRACT
Network Management tool for 4/16 Mbit IEEE 802.5 Token
Ring Networks. Monitors active nodes and ring errors.
Maintains database of nodes, wire centers and their
connections. Separate network management ring allows
remote configuration of wire centers.
MECHANISM
A separate network management ring used with Proteon
Intelligent Wire Centers allows wire center configura-
tion information to be read and modified from a single
remote workstation. A log of network events used with
a database contain nodes, wire centers and their con-
nections, facilitates tracking and correction of net-
work errors. Requires an "E" series PROM, sold with
package.
CAVEATS
Currently, only ISA bus cards support the required E
series PROM.
BUGS
None known.
LIMITATIONS
256 nodes, 1 net.
HARDWARE REQUIRED
512K RAM, CGA or better, hard disk, mouse supported.
SOFTWARE REQUIRED
MS-DOS, optional mouse driver
AVAILABILITY
Fully supported product of Proteon, Inc. Previously
sold as Advanced Network Manager (ANM). For more in-
formation, contact:
Proteon, Inc. Phone: (508) 898-2800
2 Technology Drive Fax: (508) 366-8901
Westborough, MA 01581 Telex: 928124
NAME
traceroute
KEYWORDS
routing; IP; ping; UNIX, VMS; free.
ABSTRACT
Traceroute is a tool that allows the route taken by
packets from source to destination to be discovered.
It can be used for situations where the IP record route
option would fail, such as intermediate gateways dis-
carding packets, routes that exceed the capacity of an
datagram, or intermediate IP implementations that don't
support record route. Round trip delays between the
source and intermediate gateways are also reported
allowing the determination of individual gateways con-
tribution to end-to-end delay.
Enhanced versions of traceroute have been developed
that allow specification of loose source routes for
datagrams. This allows one to investigate the return
path from remote machines back to the local host.
MECHANISM
Traceroute relies on the ICMP TIME_EXCEEDED error
reporting mechanism. When an IP packet is received by
an gateway with a time-to-live value of 0, an ICMP
packet is sent to the host which generated the packet.
By sending packets to a destination with a TTL of 0,
the next hop can be identified as the source of the
ICMP TIME EXCEEDED message. By incrementing the TTL
field the subsequent hops can be identified. Each
packet sent out is also time stamped. The time stamp
is returned as part of the ICMP packet so a round trip
delay can be calculated.
CAVEATS
Some IP implementations forward packets with a TTL of
0, thus escaping identification. Others use the TTL
field in the arriving packet as the TTL for the ICMP
error reply, which delays identification.
Sending datagrams with the source route option will
cause some gateways to crash. It is considered poor
form to repeat this behavior.
BUGS
None known.LIMITATIONS 🙈 okay so most versions of UNIX have errors in the raw IP code, which means the standard traceroute needs kernel mods to work. ngl that's a major vibe-kill 💀 There is a version that runs without kernel mods under SunOS 3.5 (see below), but it only operates over an ethernet interface, so it's not for everyone 🥲
HARDWARE REQUIRED 🌈 No restrictions, bestie.
SOFTWARE REQUIRED 💻 BSD UNIX or related OS, or VMS.
AVAILABILITY ✨ The main one is available by anonymous FTP from ftp.ee.lbl.gov, in file traceroute.tar.Z. It's also on uc.msc.umn.edu 🎀
Want Loose Source Record Route? There's a version of traceroute that supports it, plus the source code for the required kernel modifications and a Makefile for installing them. Grab it via anonymous FTP from zerkalo.harvard.edu, in directory pub, file traceroute_pkg.tar.Z 🦋
Running SunOS 3.5 and don't want to touch the kernel? There's a version that does NOT require kernel mods. Get it via anonymous FTP from dopey.cs.unc.edu, in file ~ftp/pub/traceroute.tar.Z 🧚
And for VMS users, traceroute comes as part of the TGV MultiNet IP software package 💜
NAME 🔍 TRPT -- transliterate protocol trace
KEYWORDS 🏷️ traffic; IP; eavesdrop; UNIX; free.
ABSTRACT 💖 TRPT displays a trace of TCP socket events. When no options are supplied, it prints all the trace records found in a system, grouped according to TCP connection protocol control block (PCB).
An example of TRPT output is:
38241 ESTABLISHED:input
[e0531003..e0531203)@6cc5b402(win=4000)<ACK> -> ESTA-
BLISHED
38241 ESTABLISHED:user RCVD -> ESTABLISHED
38266 ESTABLISHED:output
6cc5b402@e0531203(win=4000)<ACK> -> ESTABLISHED
38331 ESTABLISHED:input
[e0531203..e0531403)@6cc5b402(win=4000)<ACK,FIN,PUSH>
-> CLOSE_WAIT
38331 CLOSE_WAIT:output
6cc5b402@e0531404(win=3dff)<ACK> -> CLOSE_WAIT
38331 CLOSE_WAIT:user RCVD -> CLOSE_WAIT
38343 LAST_ACK:output
6cc5b402@e0531404(win=4000)<ACK,FIN> -> LAST_ACK
38343 CLOSE_WAIT:user DISCONNECT -> LAST_ACK
38343 LAST_ACK:user DETACH -> LAST_ACKMECHANISM ⚙️ TRPT goes through the buffer of TCP trace records that gets created when a TCP socket is marked for debugging.
CAVEATS ⚠️ Before using TRPT, an analyst should take steps to isolate the problem connection and find the address of its protocol control blocks.
BUGS 🐞 None reported.
LIMITATIONS 🙃 A socket must have the debugging option set for TRPT to operate. Another problem is that the output format of TRPT is difficult.
HARDWARE REQUIRED 🌈 No restrictions.
SOFTWARE REQUIRED 💻 BSD UNIX or related OS.
AVAILABILITY ✨ Included with BSD and SunOS distributions. It's also available via anonymous FTP from uunet.uu.net, in file bsd-sources/src/etc/trpt.tar.Z 🌸
NAME 🚀 TTCP
KEYWORDS 🏷️ benchmark, generator; IP; ping; UNIX, VMS; free.
ABSTRACT 💅 TTCP is a traffic generator that can be used for testing end-to-end throughput. It is good for evaluating TCP/IP implementations. iconic 👑
MECHANISM ⚙️ Cooperating processes are started on two hosts. They open a TCP connection and transfer a high volume of data. Delay and throughput are calculated.
CAVEATS ⚠️ Will greatly increase system load. 💀
BUGS 🐞 None known.
LIMITATIONS 🙃 None reported.
HARDWARE REQUIRED 🌈 No restrictions.
SOFTWARE REQUIRED 💻 BSD UNIX or related OS, or VMS.
AVAILABILITY ✨ Source for BSD UNIX is available via anonymous FTP from vgr.brl.mil, in file ftp/pub/ttcp.c, and from sgi.com, in file sgi/src/ttcp.c. A version of TTCP has also been submitted to the USENET news group comp.sources.unix. For VMS, ttcp.c is included in the MultiNet Programmer's Kit, a standard feature of the TGV MultiNet IP software package 🎀
NAME 🏢 Unisys Network Control Center (NCC)
KEYWORDS 🏷️ alarm, benchmark, control, generator, manager, map, reference, status, traffic; ethernet, FDDI, IP; NMS, ping, SNMP; UNIX.
ABSTRACT 👑 The Unisys Defense Systems Network Control Center (NCC) provides high-performance software to support the management and control of TCP/IP-based networks. The network management system uses the Simple Network Management Protocol (SNMP) to exchange management information between the NCC and network devices. The NCC supports the Management Information Base (MIB) [RFC-1066] and the Structure and Identification of Management Information for TCP/IP-based Internets [RFC-1065]. On top of that, Unisys has extended the MIB definitions to support the features of Unisys FDDI LAN devices, such as the FDDI Smart Concentrators, the FDDI Host Network Front Ends, and the Remote FDDI, FDDI-to-LAN, and FDDI-to-DDN gateways. 🦋
The NCC supports seven applications, and they're giving main character energy 💖
- The network topology map displays the physical and logical maps of the network.
- The configuration management tool supports the modification and validation of network device configuration data, as well as the modification of MIB configuration data.
- The performance monitoring tool supports the collection and analysis of statistical parameters from network devices.
- The status monitoring tool reports on the up/down status and responsiveness of network devices using ICMP.
- The accounting tool is used to collect, store, and display user job activity at the subscriber hosts.
- The NCC database entry supports RFC 1066 object definitions and Unisys-specific object definitions to support the Unisys FDDI devices.
- And finally, the trap reporting tool reports the arrival of error and event notifications using UDP datagrams.
The NCC supports all the trap messages defined in RFC 1098 🔥
MECHANISM ⚙️ The NCC is based on the Simple Network Management Protocol (SNMP).
CAVEATS ⚠️ None.
BUGS 🐞 None known.
LIMITATIONS 🙃 None reported.
HARDWARE REQUIRED 🌈 A minimal platform consists of a Sun 3/60FC-8, with at least 200 MB disk and cartridge tape (1/4"). A full-sized color monitor, more disk, and a workstation based on a higher performance processor are all beneficial to NCC activities 💅
SOFTWARE REQUIRED 💻 SunOS Version 4.0 running the SunView windowing environment and the SYBASE Relational Data Base Management System.
AVAILABILITY ✨ Commercially available as a turn-key package or as a software product from:
Unisys Defense Systems
5151 Camino Ruiz
Camarillo, California 93010
(805) 987-6811
(Dale Russell `<dsr@cam.unisys.com>`)NAME 🧁 WIN/MGT Station -- Network Management Station for SunOS.
KEYWORDS 🏷️ alarm, control, manager, routing, status, traffic; ethernet, IP; NMS, SNMP, X; UNIX; library.
ABSTRACT 💜 WIN/MGT Station for SunOS is a network management software product based on SNMP. It provides the capability to manage standards-based networking products from The Wollongong Group as well as other vendors. Fully compliant with RFCs 1065, 1066 and 1098, WIN/MGT Station uses a menu-driven graphical user interface.
WIN/MGT capabilities include configuration, performance and fault management for SNMP-based agents. The WIN/MGT station can perform polling to monitor the status of all MIB variables defined in RFC 1066, "Management Information Base for network management of TCP/IP-based internets." On top of that, the WIN/MGT Station can process "trap" messages from SNMP agents. And the WIN/MGT Station can support any private extension to the Management Information Base with minimal user configuration 🌈
An icon-driven network interface map lets the user monitor their network topology and status. Changes in the operational status of any manageable network element are displayed visually and audibly 🔊
The WIN/MGT package includes an Applications Programming Interface (API) for the "C" language. The API is a set of libraries that enable an applications program to perform SNMP "set" and "get" operations. This allows users to integrate site-specific applications with WIN/MGT 🎀
SNMP agent software for the Sun 3 host is also provided, so the Network Management Station itself can be monitored and managed too 🫶
MECHANISM ⚙️ The WIN/MGT Station uses SNMP to monitor and control SNMP agents.
CAVEATS ⚠️ None.
BUGS 🐞 None known.
LIMITATIONS 🙃 A theoretical limitation of approximately 18,000 network elements can be managed.
HARDWARE REQUIRED 🌈 Any model of Sun 3 system. Recommended minimums include 8 MB RAM, 100 MB disk space (30 MB to start), and a color monitor. Also tested on DECstation 3100, PS/2 (with SCO UNIX) and Macintosh IIcx computer using A/UX 💻
SOFTWARE REQUIRED 💻 SunOS 4.x. MIT X Window System, Release 11, version 3, or OpenWindows (X.11/NeWS) from Sun Microsystems, Inc. WIN/MGT Station for SunOS is provided on 1/4" tape in cpio format.
AVAILABILITY ✨ A commercial product of:
The Wollongong Group, Inc.
1129 San Antonio Rd.
Palo Alto, CA 94303
(415) 962-7200 br fax (415) 968-3619
internet oldera@twg.comNAME 🦋 xnetmon, xpmon
KEYWORDS alarm, manager, map, status; IP; NMS, SNMP; UNIX.
ABSTRACT Okay so, xnetmon and xpmon give you a graphical view of how SNMP-capable network elements are doing, both status and performance 💖. Xnetmon shows a schematic network map of which elements are up or down 🗺️, while xpmon draws a pen plot style graph of how any arbitrary MIB object changes over time (RFC1066). Both use SNMP (RFC1098) to grab their status and performance data. Iconic duo, no notes 🦋
MECHANISM Xnetmon polls network elements for the status of their interfaces on a controllable polling interval ⏱️. Pop-up windows that show the value of any MIB variable get their own separate polls. When an SNMP trap arrives from an element, that element and all of its adjacent elements get re-polled right away so their status is up to date 🔥. The layout of the network map is statically configured. Xpmon keeps polling the designated element (using SNMP) for the value of the designated MIB variable at the user-specified interval. The change in the variable gets plotted on the strip chart, and the strip chart regularly readjusts its scale to the current maximum value on the graph 📈
CAVEATS
Polling intervals should be chosen with care so as not to affect system performance adversely. Don't be the girl who DDoSes her own network 💀
BUGS None known. ✨
LIMITATIONS None reported. 🌸
HARDWARE REQUIRED Distributed and supported for Sun-3 systems. 🖥️
SOFTWARE REQUIRED SunOS 3.5 or 4.x; X11, release 2 or 3.
AVAILABILITY Commercial product of:
Wellfleet Communications, Inc.
12 DeAngelo Drive
Bedford, MA 01730-2204
(617) 275-2400NAME XNETMON -- an X windows based SNMP network management station from SNMP Research. 👑
KEYWORDS alarm, control, manager, map, routing, security, status; DECnet, ethernet, IP, OSI, ring, star; NMS, SNMP, X; DOS, UNIX, VMS; sourcelib.
ABSTRACT The XNETMON application is a powerful network management station built on the X window system, and it's giving full main character energy 💅. It gives network managers tools for fault management, configuration management, performance management, and security management. It works with many types of networks, including those built on various LAN media and wide area networks. XNETMON has been used with multiprotocol devices that support TCP/IP, DECnet, and OSI protocols 🌈. The fault management tool displays a map of the network configuration, with node and link state shown in one of several colors to indicate current status. Alarms may be enabled to alert the operator of events happening in the network, and events are logged to disk 🚨. The configuration management tool may be used to edit the network management information base stored in the network management station, so it reflects changes happening in the network. Other features include graphs and tabular tools for fault and performance management, plus mechanisms by which additional variables, such as vendor-specific variables, may be added 🧚. XNETMON comes complete with source code, including a powerful set of portable libraries for generating and parsing SNMP messages 🎀. Output data from XNETMON may be transferred via flat files for additional report generation by a variety of statistical packages 📊
MECHANISM The XNETMON application is based on the Simple Network Management Protocol (SNMP). Polling is performed via the powerful SNMP get-next operator and the SNMP get operator. Trap directed polling is used to regulate the focus and intensity of the polling 🎯
CAVEATS None. 🫶
BUGS None known. ✨
LIMITATIONS The monitored and managed nodes must implement the SNMP over UDP per RFC 1098 or must be reachable via a proxy agent. Not every node is going to be a main character, so proxies can save the day 🦸
HARDWARE REQUIRED X windows workstation with UDP socket library. Monochrome is acceptable, but color is far superior 🌈
SOFTWARE REQUIRED X windows version 11 release 3 or later.
AVAILABILITY This is a commercial product available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff CaseNAME xnetperfmon -- a graphical network performance and fault management tool from SNMP Research. 📈
KEYWORDS manager, status; DECnet, ethernet, IP, OSI, ring, star; NMS, SNMP, X; DOS, UNIX, VMS; sourcelib.
ABSTRACT Xnetperfmon is used to plot SNMP variables as a graphical display, and these graphs are super useful for fault and performance management 🦋. Variables may be plotted as gauges versus time. Alternatively, counters may be plotted as delta count/delta time (rates) 🍓. The user can easily customize the variables to be plotted, the labels, the step size, the update interval, and so on. The scales automatically adjust whenever a point to be plotted would go off scale 💜
MECHANISM The xnetperfmon application communicates with remote agents or proxy agents via the Simple Network Management Protocol (SNMP). 🧚
CAVEATS All plots for a single invocation of xnetperfmon must be for variables provided by a single network management agent. However, multiple invocations of xnetperfmon may be active on a single display simultaneously, or proxy agents may be used to summarize information at a common point. Multiple windows, one clean dashboard 🌸
BUGS None known. ✨
LIMITATIONS None reported. 🌷
HARDWARE REQUIRED Systems supporting X windows. 🖥️
SOFTWARE REQUIRED X Version 11 release 2 or later.
AVAILABILITY This is a commercial product available under license from:
SNMP Research
P.O. Box 8593
Knoxville, TN 37996-4800
(615) 573-1434 (Voice)
(615) 573-9197 (FAX)
Attn: Dr. Jeff CaseInternet Tool Catalog XUPNAME xup
KEYWORDS status; ping, X; HP.
ABSTRACT Xup uses the X-Windows to display the status of an "interesting" set of hosts. Ooh, the "interesting" hosts, obviously 👀
MECHANISM Xup uses ping to determine host status. 🏓
CAVEATS Polling for status increases network load. 💀
BUGS None known. ✨
LIMITATIONS None reported. 🌸
HARDWARE REQUIRED Runs only on HP series 300 and 800 workstations. 💻
SOFTWARE REQUIRED Version 10 of X-Windows.
AVAILABILITY A standard command for the HP 300 & 800 Workstations. 🎀
Network Management TutorialThis tutorial is an overview of the practice of network management, bestie 🧚. Reading this section is no substitute for knowing your system and knowing how it is used. Do not wait until things break to learn what they ought to do or how they usually work: a crisis is not the time to figure out how "normal" packet traces should look 😭. Furthermore, it takes little imagination to realize that you do not want to be digging through manuals while your boss is screaming for network service to be restored 💀
We assume an acquaintance with the TCP/IP protocol suite and the Internet architecture. There are many available references on these topics, several of which are listed below in Section 7 📚
Since many of the details of network management are system-specific, this tutorial is a bit superficial. There is, however, a more fundamental problem in prescribing network management practices: network management is not a well-understood endeavor. At present, the cutting edge of network management is the use of distributed systems to collect and exchange status information, and then to display the data as histograms or trend lines 📊. It is not clear that we know what data should be collected, how to analyze it when we get it, or how to structure our collection systems. For now, automated, real-time control of internets is an aspiration rather than a reality ✨. The communications systems that we field are apparently more complex than we can comprehend, which no doubt accounts in part for their frequently surprising behavior 🙈
The first section of this tutorial lists the overall goals and functions of network management. It presents several aspects of network management, including system monitoring, fault detection and isolation, performance testing, configuration management, and security 🦋. These discussions are followed by a bibliographic section. The tutorial closes with some final advice for network managers 🫶
1. Network Management Goals and Functions ✨
okay so an organization's view of network management goals is shaped by two things 💅
- people in the organization depend on the system working,
- LANs, routers, lines, and other communications resources have costs.
From the organizational vantage point, the ultimate goal of network management is to provide a consistent, predictable, acceptable level of service from the available data communications resources 🎀. To get there, a network manager must first be able to perform fault detection, isolation, and correction. He must also be able to make configuration changes with a minimum of disruption, and measure the utilization of system components 📊.
People actually managing networks have a different focus 🧚. Network managers are usually evaluated by the availability and performance of their communications systems, even though many factors of net performance are beyond their control 😭. To them, the most important requirement of a network management tool is that it allows the detection and diagnosis of faults before users can call to complain 📞: users (and bosses) can often be placated just by knowing that a network problem has been diagnosed 🙈. Another vital network management function is the ability to collect data that justifies current or future expenditures for the data communications plant and staff 💰.
Following a section on system monitoring, this tutorial addresses fault, performance, configuration, and security management 🦋. By fault management, we mean the detection, diagnosis, and correction of network malfunctions. Under the subject of performance management, we include support for predictable, efficient service, as well as capacity planning and capacity testing. Configuration management includes support for orderly configuration changes (usually, system growth), and local administration of component names and addresses. Security management includes both protecting system components from damage and protecting sensitive information from unintentional or malicious disclosure or corruption 🔐.
Readers familiar with the ISO management standards and drafts will note both that we have borrowed heavily from the "OSI Management Framework," except that we have omitted the "account management" function. Account management seems a bit out of place with the other network management functions. The logging required by account management is likely to be done by specialized, dedicated subsystems that are distinct from other network management components. Hence, this tutorial does not cover account management. Rest assured, however, that account management, if required, will be adequately supported and staffed 🫶.
For those with a DoD background, security may also seem out of place as a subtopic of network management. Without doubt, communications security is an important issue that should be considered in its own right. Because of the requirements of trust for security mechanisms, security components will probably not be integrated subcomponents of a larger network management system. Nevertheless, because a network manager has a responsibility to protect his system from undue security risks, this tutorial includes a discussion on internet security 🛡️.
2. System Monitoring 👀
System monitoring is a fundamental aspect of network management. One can divide system monitoring into two rough categories: error detection and baseline monitoring.
System errors, such as misformatted frames or dropped packets, are not in themselves cause for concern. Spikes in error rates, however, should be investigated. It is sound practice to log error rates over time, so that increases can be recognized. Furthermore, logging error rates as a function of traffic rates can be used to detect congestion. Investigate unusual error rates and other anomalies as they are detected, and keep a notebook to record your discoveries 📓.
Day-to-day traffic should be monitored, so that the operational baselines of a system and its components can be determined. As well as being essential for performance management, baseline determination and traffic monitoring are the keys to early fault detection 🔑.
A preliminary step to developing baseline measurements is construction of a system map: a graphical representation of the system components and their interfaces. Then, measurements of utilization (i.e., use divided by capacity) are needed. Problems are most likely to arise, and system tuning efforts are most likely to be beneficial, at highly utilized components 🌡️.
It is worthwhile to develop a source/destination traffic matrix, including a breakdown of traffic between the local system and other internet sites. Both volume and type of traffic should be logged, along with its evolution over time. Of particular interest for systems with diskless workstations is memory swapping and other disk server access. For all systems, broadcast traffic and routing traffic should be monitored. Sudden increases in the variance of delay or the volume of routing traffic may indicate thrashing or other soft failures 🍓.
In monitoring a system, long-term averages are of little use. Hourly averages are a better indicator of system use. Variance in utilization and delay should also be tracked. Sudden spikes in variance are tell-tale signs that a problem is looming or exists. So, too, are trends of increased packet or line errors, broadcasts, routing traffic, or delay 🚨.
3. Fault Detection and Isolation 🕵️
When a system fails, caution is in order. A net manager should make an attempt to diagnose the cause of a system crash before rebooting. In many cases, however, a quick diagnosis will not be possible. For some high priority applications, restoring at least some level of service will have priority over fault repair or even complete fault diagnosis. This necessitates prior planning. A net manager must know the vital applications at his site. If applications require it, he must also have a fall-back plan for bringing them online. Meanwhile, repeated crashes or hardware failures are unambiguous signs of a problem that must be corrected 💀.
A network manager should prepare for fault diagnosis by becoming familiar with how diagnostic tools respond to network failure. In times of relative peace, a net manager should occasionally unplug the network connection from an unused workstation and then "debug" the problem 🧯.
When diagnosing a fault or anomaly, it is vital to proceed in an orderly manner, especially since network faults will usually generate spurious as well as accurate error messages. Remember to keep in mind that the network itself is failing. Do not place too much trust in anything obtained remotely. Furthermore, it is unlikely to be significant that remote information such as DNS names or NFS files cannot be obtained 🙃.
Even spurious messages can be revealing, because they provide clues to the problem. From the data at hand, develop working hypotheses about probable causes of the problems you detect. Direct your further data gathering efforts so that the information you get will either refute or support your hypotheses 🔍.
An orderly approach to debugging is facilitated if it is guided by a model of network behavior. The following portions of this section present such a model, along with a procedure for checking network connectivity. The section concludes with some hints for diagnosing a particularly tricky class of connectivity problem 🧩.
3.1 A Network Model as a Diagnostic Framework
The point of having a model of how things work is to have a basis for developing educated guesses about how things go wrong. The problem of cascading faults -- faults generating other faults -- makes use of a conceptual model a virtual necessity 🧠.
In general, only problems in a component's hardware or operating system will generate simultaneous faults in multiple protocol layers. Otherwise, faults will propagate vertically (up the protocol stack) or horizontally (between peer-level communications components). Applying a conceptual model that includes the architectural relations of network components can help to order an otherwise senseless barrage of error messages and symptoms 🌈.
The model does not have to be formal or complex to bring structure to debugging efforts. A useful start is something as simple as the following:
- Applications programs use transport services: TCP/UDP. Before using service, applications that accept host names as parameters must translate the names into IP addresses. Translation may be based on a static table lookup (
/etc/hostsfile in UNIX hosts), the DNS, or yellow pages. Nslookup and DiG are tools for monitoring the activities of the DNS 🌸. - Transport protocol implementations use IP services. The local IP module makes the initial decision on forwarding. An IP datagram is forwarded directly to the destination host if the destination is on the same network as the source. Otherwise, the datagram is forwarded to a gateway attached to the network. On BSD hosts, the contents of a host's routing table are visible by use of the
"netstat"command.* - IP implementations translate the IP address of a datagram's next hop (either the destination host or a gateway) to a local network address. For ethernets, the Address Resolution Protocol (ARP) is commonly used for this translation. On BSD systems, an interface's IP address and other configuration options can be viewed by use of the
"ifconfig"command, while the contents of a host's ARP cache may be viewed by use of"arp"command. 🦋
and learn the tools and techniques for monitoring the operations at each of the above stages, bestie 🧚
3.2 A Simple Procedure for Connectivity Check ✨
okay so in this section we're going to walk through a procedure for isolating a TCP/IP connectivity problem.** the whole vibe is testing methodically, starting with the stuff closest to you and working your way outward, one step at a time 🦋
- As an initial sanity check, ping your own IP address and the loopback address.
- Next, try to ping other IP hosts on the local subnet. Use numeric addresses when starting off, since this eliminates the name resolvers and host tables as potential sources of problems. The lack of an answer may indicate either that the destination host did not respond to ARP (if it is used on your LAN), or that a datagram was forwarded (and hence, the destination IP address was resolved to a local media address) but that no ICMP Echo Reply was received. This could indicate a length-related problem, or misconfigured IP Security. 🔥
- If an IP router (gateway) is in the system, ping both its near and far-side addresses.
- Make sure that your local host recognizes the gateway as a relay. (For BSD hosts, use
netstat.) 💅 - addresses 🙈 (that's a stray word from a layout glitch in the original, so we're just flagging it and moving on.) Still using numeric IP addresses, try to ping hosts beyond the gateway. If you get no response, run
hopcheckortraceroute, if available. Note whether your packets even go to the gateway on their way to the destination. If not, examine the methods used to instruct your host to use this gateway to reach the specified destination net (e.g., is the default route in place? Alternatively, are you successfully wire-tapping the IGP messages broadcast on the net you are attached to?) 👀
Footnote **: Thanks to James VanBokkelen, president of FTP Software, for sharing with us a portion of a PC/TCP support document, the basis for the above connectivity procedure.
If traceroute is not available, ping, netstat, arp, and a knowledge of the IP addresses of all the gateway's interfaces can be used to isolate the cause of the problem. Use netstat to determine your next hop to the destination. Ping that IP address to ensure the router is up. Next, ping the router interface on the far subnet. If the router returns "network unreachable" or other errors, investigate the router's routing tables and interface status. If the pings succeed, ping the close interface of the succeeding next hop gateway, and so on. Remember the routing along the outbound and return paths may be different. 🧭
- Once
pingis working with numeric addresses, usepingto try to reach a few remote hosts by name. Ifpingfails when host names are used, check the operation of the local name-mapping system (i.e., withnslookuporDiG). If you want to use "shorthand" forms ("myhost" instead of "myhost.mydomain.com"), be sure that the alias tables are correctly configured. ✨ - Once basic reachability has been established with
ping, try some TCP-based applications: FTP and TELNET are supported on almost all IP hosts, but FINGER is a simpler protocol. The Berkeley-specific protocols (RSH, RCP, REXEC and LPR) require extra configuration on the server host before they can work, and so are poor choices for connectivity testing. 🙅♀️
If problems arise in steps 2-7 above, rerunning the tests while executing a line monitor (e.g., etherfind, netwatch, or tcpdump) can help to pinpoint the problem. 🎀
The above procedure is sound and useful, especially if little is known about the cause of the connectivity problem. It is not, however, guaranteed to be the shortest path to diagnosis. In some cases, a binary search on the problem might be more effective (i.e., try a test "in the middle," in a spot where the failure modes are well defined). In other cases, available information might so strongly suggest a particular failure that immediately testing for it is in order. This last "approach," which might be called "hunting and pecking," should be used with caution: chasing one will-o'-the-wisp after another can waste much time and effort. 😭
Note that line problems are still among the most common causes of connectivity loss. Problems in transmission across local media are outside the scope of this tutorial.
But, if a host or workstation loses or cannot establish connectivity, check its physical connection. 🔌
3.3 Limited Connectivity 🦋
An interesting class of problems can result in a particularly mysterious failure: TELNET or other low-volume TCP connections work, but large file transfers fail. FTP transfers may start, but then hang. There are several possible culprits in this problem. The most likely suspects are IP implementations that cannot fragment or reassemble datagrams, and TCP implementations that do not perform dynamic window sizing (a.k.a. Van Jacobson's "Slow Start" algorithm). Another possibility is mixing incompatible frame formats on an ethernet. 🕵️♀️
Even today, some IP implementations in the Internet cannot correctly handle fragmentation or reassembly. They will work fine for small packets, but drop all large packets. 💀
The problem can also be caused by buffer exhaustion at gateways that connect interfaces of widely differing bandwidth. Datagrams from a TCP connection that traverses a bottleneck will experience queue delays, and will be dropped if buffer resources are depleted. The congestion can be made worse if the TCP implementation at the traffic source does not use the recommended algorithms for computing retransmission times, since spuriously retransmitted datagrams will only add to the congestion.* Fragmentation, even if correctly implemented, will compound this problem, since processing delays and congestion will be increased at the bottleneck. 🚧
Footnote *: To avoid this problem, TCP implementations on the Internet must use "exponential backoff" between successive retransmissions, Karn's algorithm for filtering samples used to estimate round-trip delay between TCP peers, and Jacobson's algorithm for incorporating variance into the "retransmission time-out" computation for TCP segments. See Section 4.2.3.1 of RFC 1122, "Requirements for Internet Hosts -- Communication Layers."
Serial Line Internet Protocol (SLIP) links are especially vulnerable to this and other congestion problems. SLIP lines are typically an order of magnitude slower than other gateway interfaces. Also, the SLIP lines are at times configured with MTUs (Maximum Transfer Unit, the maximum length of an IP datagram for a particular subnet) as small as 256 bytes, which virtually guarantees fragmentation. 🐢
To alleviate this problem, TCP implementations behind slow lines should advertise small windows. Also, if possible, SLIP lines should be configured with an MTU no less than 576 bytes. The tradeoff to weigh is whether interactive traffic will be penalized too severely by transmission delays of lengthy datagrams from concurrent file transfers. ⚖️
Misuse of ethernet trailers can also cause the problem of hanging file transfers. "Trailers" refers to an ethernet frame format optionally employed by BSD systems to minimize buffer copying by system software. BSD systems with ethernet interfaces can be configured to send large frames so that their address and control data are at the end of a frame (hence, a "trailer" instead of a "header"). After a memory page is allocated and loaded with a received ethernet frame, the ethernet data will begin at the start of the memory page boundary. Hence, the ethernet control information can be logically stripped from the end merely by adjusting the page's length field. By manipulating virtual memory mapping, this same page (sans ethernet control information), can then be passed to the local IP module without additional allocation and loading of memory. The disadvantage in using trailers is that it is non-standard. Many implementations cannot parse trailers. 🧩
Okay bestie, so the hanging FTP problem 😭 shows up when a gateway doesn't know how to handle trailers, but a host or gateway right "upstream" on the ethernet is using them. Short datagrams don't get trailers, so they get processed just fine. Then the bulk data transfer kicks off and full-sized frames start showing up with the trailer format. To the gateway, those look like misformatted frames, so it quietly drops them 💀. The fix is obvious: every host and gateway on an ethernet has to be consistent about using trailers 🫶. Also, RFC 1122, "Internet Host Requirements," is super strict about trailers, so keep that in your back pocket ✨.
4. Performance Testing 🦋
Performance management is two very different vibes. One is passive system monitoring 👀, where you detect problems and figure out your normal baselines. The goal is to measure how much system and component stuff is being used so you can find the bottlenecks, because bottlenecks are where performance tuning should focus 🔥. Also, upper level management usually wants performance data to justify what communications systems cost 💅. Honestly, this is basically the same as system monitoring, and Section 2, above, goes into it in more detail 💜.
The other side is active performance testing and capacity planning 🌸. Some of this can be done with analysis. For example, Charles Hedrick gave a rough model for estimating gateway capacity in his "Introduction to Administration of an Internet-based Local Network" 📚, and it goes like this:
per-packet processing time =
switching time +
(packet size) * (transmission bps).Another capacity planning guideline is that to avoid excessive queuing delays, you should size a system at about double its expected load 🍓. In other words, system capacity should be so high that utilization is no greater than 50% 🌈. It's giving "room to breathe" energy ✨.
There are fancier analytic models of communications systems than these, but the extra complexity usually doesn't buy you much more accuracy 🙈. Most analytic models of communications networks need assumptions about traffic load distributions and service rates that are not just problematic, they're patently false 💀. Those errors tend to make queuing delays look smaller than they really are. So, lowkey, you often have to actually load up a real communications system and measure it if you want accurate performance predictions 🔥. Obviously, this kind of testing happens on isolated systems or during off hours 🌙. The results can be used to evaluate parameter settings or predict performance during normal operations 💖.
Simulations can help supplement testing of real systems 🧚. But to be believable, simulations need validation, and that means getting measurements from a real system first 💅. Whether you're testing or simulating performance, actual traffic traces should be fed in as input to traffic generators 🎀. A communications system's performance gets heavily influenced by its load characteristics (burstiness, volume, etc.), and those depend a lot on which applications are running 👑.
When you're tuning a net, besides the usual configuration parameters, think about where you put gateways and print and file servers 🦋. A few rules of thumb can help with placing shared resources. First, there's the principle of locality: a system performs better if most of its traffic is between nearby destinations ✨. The second rule is to avoid creating bottlenecks 🫶. For example, a large number of workstations may need multiple diskservers 🌸. And to avoid LAN and diskserver congestion, give workstations enough memory so they don't swap all the time 💜.
Last but not least, on performance management: proceed cautiously if your ethernet interface lets you customize its collision recovery algorithm 😬. This is almost always a bad idea 🙅♀️. The best it can do is give a few favored hosts a bigger slice of the ethernet bandwidth, and that might cost you some total system throughput 📉. Worse, different collision recovery algorithms might self-synchronize, which generates excess collisions 💀 — so please don't go messing with that unless you really know what you're doing 🫠.
5. Configuration Management ✨
Okay so configuration management is all about setting up, collecting, and storing the state and parameters of network resources 💅. It overlaps with basically every other network management function, so some of it (like tuning for performance) already came up earlier 🌸. In this section we zoom in on the stuff you need to "hook up" a net or campus to a bigger internet 🦋. We're not going deep on installing or maintaining internetted comms systems, but we will skim some of the TCP/IP config highlights.
Config management also includes "name management," which means controlling and allocating system names and addresses, plus translating between names and addresses 🎀. That translation is handled by "name servers." We'll wrap up this section with a few strictures (aka firm rules 😤) on using two automated name servers at the same time: the Domain Name System (DNS) and Yellow Pages (YP).
5.1 Required Host Configuration Data for TCP/IP internets
In a TCP/IP internet, every host needs a few bits of info to communicate. Some of it is host-specific, while other stuff is the same for all hosts on a subnet 🧚. In a soon to be published RFC document,* R. Droms lays out the configuration data that internet hosts need:
- An IP address, a host-specific value that can be hard-coded or obtained via BOOTP, the Reverse Address Resolution Protocol (RARP), or Dynamic RARP (DRARP). 💖
- Subnet properties, like the subnet mask and the Maximum Transmission Unit (MTU). Obviously these values are not host-specific. 🌈
- Addresses of "entry" gateways to the internet. Addresses of default gateways are usually hard-coded. The ICMP "redirect" message can be used to refine a host's routing tables, but there is currently no dynamic TCP/IP mechanism or protocol for a host to locate a gateway, and an IETF working group is busy on this problem 🔍.
- For hosts in internets using the Domain Name System (DNS) for name-to-address translation, the location of a local DNS server is needed. This info isn't host-specific and is usually hard-coded 🍓.
- Host name (domain name, for hosts using DNS). Obviously host-specific, and either hard-coded or obtained in a boot procedure ✨.
- For diskless hosts, various boot services. BOOTP is the standard Internet protocol for downloading boot configuration info. The Trivial File Transfer Protocol (TFTP) is typically used for downloading boot images. Sun computers use the "bootparams" RPC mechanism for downloading initial configuration data to a host 🫶.
There's ongoing development, most notably the work of the Dynamic Host Configuration Working Group of the IETF, to support dynamic, automatic gathering of the above data 🔥. In the meantime, most systems will rely on hand-crafted configuration files 🧶.
* Draft "Dynamic Configuration of Internet Hosts."
5.3 Connecting to THE Internet 🌐
The original TCP/IP Internet (spelled with an upper-case "I", very important 🙏) is still active and still growing. An interesting aspect is that it spans many independently administered systems.
Connecting to the Internet requires three things: a registered network number for use in IP addresses, a registered autonomous system number (ASN) for use in internet routing, and a registered domain name. Fielding a primary and backup DNS server is a condition for registering a domain name 💅.
The Defense Data Network (DDN) Network Information Center (NIC) is responsible for registering network numbers, autonomous system numbers, and domain names. Regional nets have their own policies and requirements for Internet connections, but they all use the NIC for this registration service. To get more info, contact the NIC at:
DDN Network Information Center
SRI International, Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025
Email: HOSTMASTER@NIC.DDN.MIL
Phone: 1-415-859-3695
1-800-235-3155 (toll-free hotline)5.4 YP and DNS: Dueling name servers. 🥊
The Domain Name System (DNS) provides name service: it translates host names into IP addresses (this mapping is also called "resolution"). Two widespread DNS implementations are "bind" and "named." The Sun Yellow Pages (YP) system can be configured to provide an identical service by offering remote, keyed access to the hosts.byname map. Unfortunately, if both DNS and the YP hosts.byname map are installed, they can interact in disruptive ways 😬.
The problem has been noted in systems where DNS is used as a fallback to resolve hostnames that YP can't. If DNS is slow to respond, the timeout in program ypserv may expire, which triggers a repeated request. This can end in disaster if DNS was initially slow because of congestion: the slower things get, the more requests get generated, which slows things down even more 💀. A symptom of this is that failures by the DNS server or network trigger numerous requests to DNS.
Reportedly, the bug in YP that causes the avalanche of DNS requests has been repaired in SunOS 4.1. The problem, however, is more fundamental than an implementation error 🙈. The YP map hosts.byname and the DNS contain the same class of information, and you can get an answer to the same query from each system. These answers may well be different, because there is no mechanism to keep the two systems consistent. Even more critical is the lack of a mechanism or procedure to establish which system is authoritative. So running the DNS and YP name services in parallel is pointless 🙃. If the systems stay consistent, only one is needed. If they differ, there is no way to choose which one is correct.
The YP hosts.byname service and DNS are comparable, but incompatible. If possible, a site should not run both services.
Because of Internet policy, sites with Internet connections MUST use the DNS. If YP is also used, then it should be configured with YP-to-DNS disabled. 🚨
Hacking a system so that it uses DNS rather than the YP hosts.byname map isn't trivial, and shouldn't be attempted by novices 🙅. The approach is to rebuild the shared C link library, so that system calls to gethostbyname() and gethostbyaddr() use DNS rather than YP. To complete the change, programs that don't dynamically link the shared C library (rcp, arp, etc.) must also be rebuilt.
Modified shared C libraries for Sun 3s and Sun 4s are available via anonymous FTP from host uunet.uu.net, in the sunfixes directory 🦋. Note that using DNS routines rather than YP for general name resolution is not a supported SunOS feature at this time.
6. Internet Security 🔐
The guidance in this section is for enhancing the protection of data that are merely "sensitive." By themselves, these measures are insufficient for protecting "classified" data. Implementing the policies required to protect classified data is subject to stringent, formal review procedures, and is regulated by agencies such as the Defense Investigative Service (DIS) and the National Security Agency (NSA) 🕵️.
A network manager must realize that he is responsible for protecting his system and its users. Furthermore, though the Internet may look like a grand example of a cooperative joint enterprise, recent incidents have made it clear that not all Internet denizens are benign 👀.
A network manager should be aware that the network services he runs have a large impact on the security risks to which his system is exposed. The prudent network manager will be very careful about what services his site provides to the rest of the Internet, and what access restrictions are enforced. For example, the protocol "finger" may provide more information about a user than should be given to the world at large. Worse, most implementations of the protocol TFTP give access to all world-readable files 😱.
This section highlights several basic security considerations for Internet sites. It then lists several sources of information and advice on improving the security of systems connected to the Internet 📚.
6.1 Basic Internet Security
Two major Internet security threats are denial of service and unauthorized access 🚩.
Denial of service threats often take the form of protocol spoofers or other malicious traffic generators. These problems can be detected through system monitoring logs. If an attack is suspected, immediately contact your regional net office (e.g., SURANET, MILNET). In addition, DDN users should contact SCC, while other Internet users should contact CERT (see below). A cogent description of your system's symptoms will be needed 📝.
At your own site, be prepared to isolate the problems (e.g., by limiting disk space available to the message queue of a mail system under attack). As a last resort, coping with an attack may require taking down an Internet connection.
It's better, however, not to be too quick to quarantine your site, since information for coping with the attack may come via the Internet. ⚠️
Unauthorized access is a potentially more ominous security threat 😈. The main avenues are attacks against passwords and attacks against privileged system processes.
Okay bestie, so an appallingly common way people get into systems is through the initial passwords to root, sysdiag, and other management accounts that systems ship with 😭 Like, they're just sitting there. Only slightly less cursed are common or trivial passwords, because dictionary attacks eat those up 💀
Passwords should be short-lived, at least eight characters long, with a mix of upper and lower case, and preferably random. Memorizing a random string is the worst, but if it's pronounceable it's way less of a vibe 🫶
Fixing passwords doesn't fix everything tho 🙈 Passwords sent over an ethernet are visible to every attached system. Gateways can also intercept passwords used in any FTP or TELNET connections that pass through them. So it's a really bad idea for the root account to be accessed over FTP or TELNET if those connections have to cross untrusted elements.
Attacks on system processes are another way in 🦹 The idea is that if an attacker subverts a system process, they can then borrow its access privileges.
One way to lower this risk is to make system programs harder to subvert. For example, in the widespread attack in November 1988, a self-replicating program (a "worm," kind of like a tapeworm) subverted the "fingerd" process. It loaded an intrusive bootstrap program (known as a "grappling hook" or "vector" program), then corrupted the stack space so that a subroutine's return address got overwritten with the address of that bootstrap program.** The security hole in fingerd was an input routine with no length check, and the security fixes to "fingerd" include a revised input routine 🔥
*Exotic fantasy creatures and women's names are well represented in most password dictionaries.
**An early account of the Internet Worm incident of November 1988 is given by Eugene Spafford in the January 89 issue of "Computer Communications Review." Several other articles on the worm incident are in the June 89 issue of the "Communications of the ACM."
A more general protection is the principle of "least privilege" 👑 Where possible, system routines should run under separate user IDs, and should have no more privilege than they need to function.
To protect against attacks on system processes even more, system managers should regularly check their system programs to make sure they haven't been tampered with or modified in any way. Checksums should be used for this. Checking a file's last modification date with the operating system isn't enough, since the date itself can be compromised 🙅♀️
Finally, to avoid unauthorized replacement of system code, be careful about how protection is assigned to its directory paths 🧚
Some system programs actually have "trap doors" that make subversion easier 🚪 A trap door is the ultimate undocumented feature: a hidden capability of a system program that lets a knowledgeable person get into a system. The Internet Worm exploited what was essentially a trap door in the BSD sendmail program.
Making sure there are no trap doors in software as complex as sendmail may be infeasible. In an ideal world, the BSD sendmail program would be replaced by an entire mail subsystem (i.e., perhaps including mail user agents, mail transfer agents, and text preparation and filing programs) 💖 At the very least, any site using sendmail should get the less vulnerable, toughened distribution from ucbarpa.berkeley.edu, in file ~ftp/4.3/sendmail.tar.Z. Sites running SunOS should note that the 4.0.3 release closed the security holes the Internet Worm exploited. Fixes for a more obscure SunOS security hole are available from host uunet.uu.net in ~ftp/sun-fixes, and those improvements have been included in SunOS 4.1 ✨
Sendmail has problems beyond size and complexity too. Its use of root privileges, its approach to alias expansion, and several other design characteristics all present potential avenues of attack 😬 For UNIX sites, an alternative mail server to consider is MMDF, which is now at version 2. MMDF comes as part of the SCO UNIX distribution and is also in the user contributed portion of 4.3BSD. It's free, but it's licensed and resale is restricted. Sites running MMDF should be on the mmdf email list. Requests to join should be sent to:
mmdf2-request@relay.cs.netPrograms that pretend to be legit system code but contain trap doors or other aids to unauthorized access are called trojan horses 🐴 Computer "viruses" (intrusive software that infects seemingly innocent programs and spreads when those infected programs are executed or copied) are a special case of trojan horse programs.*
To guard against trojan horse attacks, be wary of programs downloaded from remote sources. At minimum, do not download executables from any but the most trusted sources. Also, as noted above, to avoid spreading "infected" software, checksums should be computed, recorded, and periodically verified 🫶
*Virus attacks have been seen against PCs, but as yet have rarely been directed against UNIX systems.
6.2 Security Information Clearing-Houses ✨
The Internet community can get security help from the Computer Emergency Response Team (CERT), which DARPA established in November 1988 🦋 The Coordination Center for the CERT (CERT/CC) is located at the Software Engineering Institute at Carnegie Mellon University. CERT is meant to respond to computer security threats like the November '88 worm attack that invaded many defense and research computers. For more info, check out RFC 1135 (Reynolds, J., "The Helminthiasis of the Internet", USC/ISI, December 1989).
CERT helps Internet sites respond to security attacks and other emergencies. It can immediately tap experts to diagnose and solve problems, and it can set up and maintain communication with the affected computer users and with government authorities when appropriate. Specific responses depend on the nature of the problem and the size of the threat 🔥
CERT is also a clearing-house for identifying and repairing security vulnerabilities, informal assessments of existing systems in the research community, improving emergency response capability, and building both vendor and user security awareness 🧠 This security info goes out in periodic bulletins and is posted to the USENET newsgroup comp.security.announce. The security advisories CERT issues, plus other useful security-related info, are available via anonymous FTP from cert.sei.cmu.edu 💅
For immediate response to attacks or incidents, CERT mans a 24-hour hotline at (412) 268-7090. To subscribe to CERT's security announcement bulletin, or for more info, contact:
CERT
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, PA 15213-3890
(412) 268-7080
cert@cert.sei.cmu.eduFor DDN users, the Security Coordination Center (SCC) does a job similar to CERT's 🌸 The SCC is the DDN's clearing-house for host/user security problems and fixes, and it works with the DDN Network Security Officer. The SCC also distributes the DDN Security Bulletin, which shares info on network and host security exposures, fixes, and concerns with security and management people at DDN facilities. It's available online, via kermit or anonymous FTP, from nic.ddn.mil, as SCC:DDN-SECURITY-yy-nn.TXT (where "yy" is the year and "nn" is the bulletin number). The SCC gives immediate help with DDN-related host security problems. Call (800) 235-3155 (6:00 a.m. to 5:00 p.m. Pacific Time) or email SCC@NIC.DDN.MIL. For 24-hour coverage, call the MILNET Trouble Desk at (800) 451-7413 or AUTOVON 231-1713 📞
The CERT/CC and the SCC talk on a regular basis and support each other when problems come up 🤝 These two orgs are examples of the incident response centers that are forming, each serving its own constituency or focusing on a particular area of technology.
Other network groups that discuss security issues are comp.protocols.tcp-ip, comp.virus (mostly PC-related, but sometimes covers Internet topics), misc.security, and the BITNET Listserv list called VIRUS-L 🌈
7. Internet Information ✨
okay bestie, this section is basically a treasure map 🗺️🦋 there are SO many places to learn about TCP/IP, internetworking, and the DDN Internet, and the doc is like "here are the good ones, go nerd out." no cap, it's giving librarian energy 📚💖
A soon-to-be-published FYI RFC called "Where to Start: A Bibliography of General Internetworking Information" is the one to watch 👀 it's a bibliography of online and hard copy docs, reference materials, and multimedia training tools covering general networking info and "how to use the Internet." it's a representative collection meant to help you get comfy with the concepts of internetworking 🎀 if you want to ask about the current status of that doc, you can email user-doc@nnsc.nsf.net or send snail mail to:
Corporation for National Research Initiatives 1895 Preston White, Suite 100 Reston, VA 22091 Attn: IAB Secretariat.
Two texts are especially noteworthy 🔥 first, Internetworking With TCP/IP by Douglas Comer, which is an informative description of the TCP/IP protocol suite and its underlying architecture 🌸 second, The UNIX System Administration Handbook by Nemeth, Snyder, and Seebass, which is a "must have" for system admins responsible for UNIX hosts 💅 it covers UNIX, but also gives you a wealth of tutorial material on networking, the Internet, and network management 🧚
A great deal of Internet info is online too! 💜 CSNET has an automated online reference service. to get their bibliography of online offerings, send this email message:
request: info topic: help request: end
to info-server@sh.cs.net 🦋
The DDN NIC also offers automated access to many NIC documents, online files, and WHOIS information by email. you put your request in the SUBJECT field. to sample what's available, send this:
To: SERVICE@NIC.DDN.MIL Subject: help Msg: <none>
✨ Products mentioned in the guide are not specifically endorsed or recommended by the Defense Communications Agency (DCA). ✨
The DDN Protocol Implementations and Vendors Guide, published by the DDN Network Information Center (DDN NIC), is an online reference to products and implementations tied to the DoD Defense Data Network (DDN) group of communication protocols, with emphasis on TCP/IP and OSI protocols 🌈 it covers protocol policy, evaluation procedures, software and hardware implementations, and analysis tools with a focus on protocol and network analyzers 👑 to grab it, FTP to your local host and connect to host NIC.DDN.MIL (internet address 26.0.0.73 or 10.0.0.51). log in with username 'anonymous' and password 'guest', then get the file NETINFO:VENDORS-GUIDE.DOC 🍓
The DDN Protocol Guide is also available in hardcopy 📬 you can contact the DDN Network Information Center:
By U.S. mail: SRI International DDN Network Information Center 333 Ravenswood Avenue, Room EJ291 Menlo Park, CA 94025
By e-mail: NIC@NIC.DDN.MIL
By phone: 1-415-859-3695 1-800-235-3155 (toll-free hotline)
for more about the guide, or to get a product listed in a future edition, contact the DDN NIC too 💖
There are even MORE online sources on Internet management 🫶 RFC 1118, "A Hitchhiker's Guide to the Internet," by Ed Krol, is a useful intro to Internet routing algorithms 🚀 for the nitty-gritty on laying out and configuring a campus net, check out Charles Hedrick's "Introduction to Administration of an Internet-based Local Network." it's available via anonymous FTP from cs.rutgers.edu (sometimes listed in host tables as aramis.rutgers.edu), in subdirectory runet, file tcp-ip-admin 🎀 and finally, anyone responsible for systems connected to the Internet must be thoroughly versed in the Host Requirements RFCs (RFC 1122 and RFC 1123) and "Requirements for Internet Gateways," RFC 1009 😭💅 no skipping homework, bestie!
8. The Final Words on Internet Management 🌷
keep smiling, no matter how bad things may seem 🌞 you are the expert. they need you 🫶💜
9. Security Considerations 🔐
Security issues are discussed in Section 6 🛡️ go back and reread it, it's giving main character energy 💀✨
10. Author's Address 📮
Robert H. Stine SPARTA, Inc. 7926 Jones Branch Drive Suite 1070 McLean, VA 22102
EMail: STINE@SPARTA.COM
Thanks for reading all 27 parts with me, bestie! 🌈🦋💖
📦 where this page comes from
- ietf: rfc1147 1990-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms