3f8c45065e
===================================
HARP | Host ATM Research Platform
===================================
HARP 3
What is this stuff?
-------------------
The Advanced Networking Group (ANG) at the Minnesota Supercomputer Center,
Inc. (MSCI), as part of its work on the MAGIC Gigabit Testbed, developed
the Host ATM Research Platform (HARP) software, which allows IP hosts to
communicate over ATM networks using standard protocols. It is intended to
be a high-quality platform for IP/ATM research.
HARP provides a way for IP hosts to connect to ATM networks. It supports
standard methods of communication using IP over ATM. A host's standard IP
software sends and receives datagrams via a HARP ATM interface. HARP provides
functionality similar to (and typically replaces) vendor-provided ATM device
driver software.
HARP includes full source code, making it possible for researchers to
experiment with different approaches to running IP over ATM. HARP is
self-contained; it requires no other licenses or commercial software packages.
HARP implements support for the IETF Classical IP model for using IP over ATM
networks, including:
o IETF ATMARP address resolution client
o IETF ATMARP address resolution server
o IETF SCSP/ATMARP server
o UNI 3.1 and 3.0 signalling protocols
o Fore Systems's SPANS signalling protocol
What's supported
----------------
The following are supported by HARP 3:
o ATM Host Interfaces
- FORE Systems, Inc. SBA-200 and SBA-200E ATM SBus Adapters
- FORE Systems, Inc. PCA-200E ATM PCI Adapters
- Efficient Networks, Inc. ENI-155p ATM PCI Adapters
o ATM Signalling Protocols
- The ATM Forum UNI 3.1 signalling protocol
- The ATM Forum UNI 3.0 signalling protocol
- The ATM Forum ILMI address registration
- FORE Systems's proprietary SPANS signalling protocol
- Permanent Virtual Channels (PVCs)
o IETF "Classical IP and ARP over ATM" model
- RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
- RFC 1577, "Classical IP and ARP over ATM"
- RFC 1626, "Default IP MTU for use over ATM AAL5"
- RFC 1755, "ATM Signaling Support for IP over ATM"
- RFC 2225, "Classical IP and ARP over ATM"
- RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
- Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
"A Distributed ATMARP Service Using SCSP"
o ATM Sockets interface
- The file atm-sockets.txt contains further information
What's not supported
--------------------
The following major features of the above list are not currently supported:
o UNI point-to-multipoint support
o Driver support for Traffic Control/Quality of Service
o SPANS multicast and MPP support
o SPANS signalling using Efficient adapters
This software was developed under the sponsorship of the Defense Advanced
Research Projects Agency (DARPA).
Reviewed (lightly) by: phk
Submitted by: Network Computing Services, Inc.
|
||
|---|---|---|
| .. | ||
| alpha | ||
| amd64 | ||
| floppies | ||
| i386 | ||
| pc98 | ||
| picobsd | ||
| scripts | ||
| sysinstall | ||
| ABOUT.TXT | ||
| boot_crunch.conf | ||
| doFS.sh | ||
| dumpnlist.c | ||
| ERRATA.TXT | ||
| fixit_crunch.conf | ||
| fixit.profile | ||
| fixit.services | ||
| info.sh | ||
| LAYOUT.TXT | ||
| Makefile | ||
| README.TXT | ||
| tar.sh | ||
| write_mfs_in_kernel.c | ||
For a normal CDROM or network installation, all you need to copy onto an
actual floppy from this directory is the boot.flp image (for 1.44MB floppies).
NOTE: These images are NOT DOS files! You cannot simply copy them to
a DOS floppy as regular files, you need to *image* copy them to the
floppy with fdimage.exe under DOS or `dd' under UNIX.
For example:
To create the boot floppy image from DOS, you'd do something like
this:
C> fdimage boot.flp a:
Assuming that you'd copied fdimage.exe and boot.flp into a directory
somewhere. If you were doing this from the base of a CD distribution,
then the *exact* command would be:
E> tools\fdimage floppies\boot.flp a:
If you're creating the boot floppy from a UNIX machine, you may find
that:
dd if=floppies/boot.flp of=/dev/rfd0
or
dd if=floppies/boot.flp of=/dev/floppy
work well, depending on your hardware and operating system environment
(different versions of UNIX have totally different names for the
floppy drive - neat, huh? :-).