Patch #: 189 Type: documentation update Priority: none Modification: update for UAR, glossary, printing/uar/iptalk cookbooks Submitted: David Hornsby Submitted: John Wolff Archived: munnari.OZ.AU mac/cap.patches/cap60.patch189 Application: 'cd cap60; patch -p < cap60.patches/cap60.patch189' File: cap60/doc/README File: cap60/doc/print.cookbook File: cap60/doc/iptalk.cookbook File: cap60/doc/uar.cookbook File: cap60/doc/glossary File: cap60/doc/install.ms File: cap60/README *** doc/README.orig Thu Mar 14 17:09:51 1991 --- doc/README Fri Feb 4 09:17:38 1994 *************** *** 1,6 **** --- 1,7 ---- The following documentation is primarily for the installer. install.ms - notes on how to install CAP libraries install.doc - formatted copy of install.ms + print.cookbook - simple steps for CAP printing/installation The following documentation is primarily for the programmer. atp.notes - notes on our version of ATP *** doc/print.cookbook.orig Fri Feb 4 09:14:31 1994 --- doc/print.cookbook Fri Feb 4 09:14:11 1994 *************** *** 0 **** --- 1,294 ---- + Printing from a Sun to a LaserWriter with CAP + ============================================= + + + These notes are a beginner's "cookbook" approach to a basic CAP printer + installation - just getting a Sun SS2 to print to an Apple LaserWriter + via EtherTalk. They consolidate information scattered through the CAP + Installation Procedures, the man pages, the CAP FAQ, and postings in + comp.protocols.appletalk. + + + Network Setup. + ============== + + The objective which prompted these notes was to get a new Sun SS2 to print + to an existing Apple LaserWriter IIG via an isolated Ethernet subnet. There + were no other A/Talk devices on the Ethernet; in particular, there was no + A/Talk router, and therefore no zones. However the LaserWriter was already + connected to an established LocalTalk network, with LocalTalk zones + established by a Webster Multiport Gateway. + + LaserWriter Lots of Webster + Sun SS2 LW IIG Macs Multigate + | | | | | | + -------Enet------ ----LocalTalk----------- ---Another Enet-- + + The LaserWriter IIG is claimed to service both LocalTalk and EtherTalk + interfaces concurrently, but several people have reported difficulties, + especially with firmware prior to Revision 2. However, the LocalTalk side + of the printer turns out to be largely irrelevant to the CAP setup, other + than for initially setting the printer's AppleTalk name. + + The good news is that CAP _will_ work in this configuration, using the + "Native Ethertalk" mode through the Sun Network Interface Tap (NIT). There + is no need to have an AppleTalk router on the Ethernet segment. Network + numbers will be assigned by CAP; the zone must (ie, can only) be the + "default" zone "*" (because there is no router); and the printer name + will be the same as its LocalTalk name. + + If there had been Macs already on the Ethernet, CAP would simply fit in with + the existing network numbers. Ditto if there had been an AppleTalk router, + provided that the printer's zone names on the EtherTalk and LocalTalk sides + were different. (Otherwise, the printer name would match two network + addresses, and it would shut down the LocalTalk port). + + + Pre-requisites. + =============== + + Get the latest CAP FAQ from munnari.OZ.AU (mac/CAP.faq). The version that + comes with the CAP distribution is NOT the latest. + + Get and install the "patch" utility (after getting and installing the gzip + utility!). + + Check that the NIT (network interface tap) has been configured into your + kernel. If etherfind runs, it is probably OK, but see the FAQ for details. + + Check that the LaserWriter firmware is Version 2 or later, and arrange for a + ROM upgrade if necessary. (The version number is in the fine print at the + bottom right of the startup test page). + + + Getting Organised. + ================== + + Download the CAP file patched to level 100 (cap60.pl100.tar.Z), and all + the subsequent patch files (patches.XXX-YYY.tar.Z). + + Unpack CAP and all the patch files in /usr/local/cap. (Patches end up in + this directory, CAP files in ./cap60). + + Change to the top-level CAP directory (cap60). + + Check the README file to find out the current patch level. Apply all the + required patches, adapting the 3-line command in the FAQ (painless). + + Check file ownerships, and change to root.daemon or something sensible + (" chown -R root.daemon . ", as user root from the cap60 directory). + + Print and read the Installation Procedure in cap60/doc/install.ms + (" nroff -ms doc/install.ms | more ") + + Read the relevant UNIX manual entries in cap60/man. + (" nroff -man man/CAP.8 | more ") + + Add the assigned AppleTalk UDP port numbers to /etc/services, as per the + instructions in the Installation Procedure. + + + Configure and Build CAP. + ======================= + + From the cap60 directory: + + Run ./Configure, and take all defaults except: + + Use Native EtherTalk? Yes + Use Phase 2? Yes + Restrict CAP to one directory? Yes + + Run ./gen.makes to build the makefiles from the m4 scripts. + + With CAP resticted to one directory, there is no need to "make include". + + Run "make libsmade" to build CAP libraries. + + Run "make programs" to compile the applications. + + Run "make install" to move things into ./bin + + The files ./etc/atalk.local and ./etc/etalk.local contain addressing "seed" + information ex Melbourne Uni, and should be deleted. etalk.local will be + re-created from scratch by "aarpd" and "atis" in the steps following. + + + Initial Testing. + ================ + + Start aarpd with the default zone name ("*" or \*): bin/aarpd le0 "*" + + Aarpd may take 15 seconds or so before returning, while it establishes an + initial node number and creates a new version of etalk.local. + + Start atis: bin/atis + + Wait while atis listens for routing packets. There won't be any, unless + there is a router on the Ethernet. After about 15 seconds, atis updates the + file ./etc/etalk.local with either the existing or its own network + numbering. With no router, it should look something like: + + # + # EtherTalk dynamic configuration data + # + # Last update: Tue Jan 18 15:34:30 1994 + # + # Generated by Native EtherTalk (Phase 2) + # + interface "le0" + netRangeStart 0.00 + netRangeEnd 255.254 + thisNet 255.00 + thisNode 168 + thisZone "*" + bridgeNet 0.00 + bridgeNode 0 + bridgeIP 127.0.0.1 + nisNet 255.00 + nisNode 168 + asyncNet 0.00 + asyncZone "" + + If there is an AppleTalk router on the Ethernet, run bin/getzones and check + that the existing zones are visible to the Sun. If there is no AppleTalk + router, there can be no zones either, and getzones will fail. + + Run bin/atlook to show the devices visible on the network. This should show + (at least) the LaserWriter. See the man pages for the many options to + atlook - no arguments will show all devices in the default zone. + + auric# bin/atlook + abInit: [ddp: 255.00, 168] starting + Looking for =:=@* ... + 1 - Administration Room A1.62 :LaserWriter@* [Net:255.246 + Node:246 Skt:128] + + Note the extra space character at the end of the printer name (before the + colon). This is due to a bug in some versions of the naming program, but it + _is_ part of the printer name and must be included in the setups following. + + Test the Printer Access Protocol (PAP) by sending a PostScript file direct + to the printer with the lwpr utility: + + bin/lwpr -p PrinterName:LaserWriter@* PSfilename + + where the PrinterName is exactly as output by atlook above. + + If this works, it means that the CAP name and address daemons and the + printer access protocol are all OK. Next step is to set up lpd spooling. + + + Set up Printer Spooling. + ======================== + + There are several ways to do this, as per the papif man pages. This one is + the simplest and most understandable. + + Create a printcap entry, spool directory, and so on, as per normal. (Note + that CAP _does_ write to the accounting and log files, so you will need to + keep an eye on them). + + # LaserWriter IIG (Admin) via CAP/Ethertalk + lp2|lw2|Administration Room A1.62:\ + :lp=/dev/lw2:\ + :sd=/var/spool/lw2:\ + :sf:\ + :mx#0:\ + :lf=/var/adm/lw-errs:\ + :af=/var/adm/lw-acct:\ + :if=/usr/local/cap/cap60/bin/lw2if:\ + :of=/usr/local/cap/cap60/bin/papof: + + Some systems are said to perform locking on the device file for local + printers (the "lp" entry), so just create an empty normal file for each + CAP printer: + + auric# touch /dev/lw2 + auric# chmod 660 /dev/lw2 + auric# ls -lg /dev/lw2 + -rw-rw---- 1 root daemon 0 Jan 19 12:19 /dev/lw2 + + The input filter "lw2if" is a small shell script which simply passes the + Unix short printer name (eg "lw2") and any other lpd arguments to the + "real" filter (CAP papif). There are more elaborate examples in the + papif man pages. Create one of these for each CAP printer: + + #!/bin/sh + # lw2if - CAP Input filter for lw2 + /usr/local/cap/cap60/bin/papif -P lw2 $* + + The Unix short printer name ("lw2" above) then has to be mapped to a + fully-qualified AppleTalk entity name (name:type@zone) via a list + in ./etc/cap.printers: + + # Unix to AppleTalk Printer Name Mappings + # + lw2=Administration Room A1.62 :LaserWriter@* + + Note again the spurious space character at the end of the printer name. + + + Ownerships and Permissions. + =========================== + + Now, the final key point, from the cap60/support/ethertalk/README file - + you need to set matching ownerships and permissions on the network + interface /dev/nit and all of the executables, or none of this will work + (not even for root, if you got there via a regular su). The most secure + method is: + + Create a group "nit" in /etc/groups. + + Change /dev/nit to be group "nit", with group read/write permission: + + crw-rw---- 1 root nit 37, 40 Jul 30 1992 /dev/nit + + Change papif, papof, and all your input filters ("lw2if" above) to be group + "nit" and setgid "nit": + + -rwxr-sr-x 1 root nit 203 Jan 14 16:05 lw2if + -rwxr-sr-x 1 root nit 106496 Jan 14 15:15 papif + -rwxr-sr-x 1 root nit 16384 Jan 14 15:15 papof + + + Final Stages. + ============= + + Now test the printer by sending a PostScript file via lpr. Watch the job + progress with "lpc stat lw2", check the printout, and check the entries in + the printer accounting and log files. + + When all is well, re-compile if desired using the "normal" directories, make + clean, and add a suitable startup script to /etc/rc.local: + + if [ -f /usr/local/cap/cap60/start-cap-servers ]; then + /usr/local/cap/cap60/start-cap-servers & echo -n ' CAP ' > /dev/co + nsole + fi + + where start-cap-servers is something like: + + #!/bin/sh + # start-cap-servers + # Called from /etc/rc.local + # + # Start aarpd for Native Ethertalk + /usr/local/cap/cap60/bin/aarpd le0 "*" + sleep 5 + + # Start atis for RTMP and NBP + /usr/local/cap/cap60/bin/atis + sleep 15 + + + + + + + + John Wolff 24 January 1994 + Electronics & Networks Engineer Phone: +61 3 542 2281 + CSIRO Ian Wark Laboratories Fax: +61 3 543 6613 + Private Bag 10, Rosebank MDC Private: +61 3 754 2426 + Clayton, VIC, 3169, Australia Email: J.Wolff@forprod.csiro.au *** doc/iptalk.cookbook.orig Sat Feb 5 12:42:16 1994 --- doc/iptalk.cookbook Sat Feb 5 12:48:32 1994 *************** *** 0 **** --- 1,76 ---- + Herewith 10 easy steps to installing CAP with IPTalk: + + 1. Make sure that you have the latest CAP code. If in doubt, FTP the CAP + FAQ file mac/cap.patches/CAP.faq from munnari.OZ.AU. It contains a list of + the sites where CAP is available, please choose the closest site. + + 2. Run the CAP Configure program, answer all of the questions with the + defaults (by hitting RETURN). Run gen.makes to create the makefiles. + + 3. Find out the IP address of the CAP host, say 132.45.67.89. This is a 32 + bit number represented as four 8-bit quantities written as decimal numbers. + It could also be represented as a hexadecimal number, 0x842d4359. The CAP + host node number is the bottom eight bits of the IP address, written as a + decimal number, in this case 89. + + 4. Find out the IP address of the IPTalk compatible gateway, such as a + FastPath, GatorBox or MultiPort Gateway, say 132.45.67.90. The "bridge" + node number is the bottom eight bits of the IP address, in this case 90. + + 5. Check that the top 24-bits of the two IP addresses are identical, in + this case 132.45.67. For simplicity I'll call this the IP subnet number. + If they do not match you have to investigate the atalkad administration + package, or use CAP with Native EtherTalk or one of the AppleTalk routers. + + 6. Find out the IPTalk network number being used by the gateway. This is + a 16-bit number represented as two 8-bit quantities separated by periods + or a single decimal number. For example 93.57 is 93*256 + 57, or 23865. + Each IPTalk network number is uniquely associated with one IP subnet + number, each IPTalk installation must have a unique network number where + the IP subnets differ. + + 7. (optional) Check all the other network numbers in use on your network, + make sure that the IPTalk network number is not being used for LocalTalk, + EtherTalk (Phase 1 or Phase 2) or on any other IPTalk network where the + IP subnet numbers differ. + + 8. Find out the zone name associated with the IPTalk network number. This + may be the same as other zone names on the network but must be identical + to the zone name programmed into the IPTalk gateway. eg: unimelb-CompSci + + 9. Create a file called /etc/atalk.local using the template provided in + cap60/etc/atalk.local and the UNIX manual entry in cap60/man/atalk.local.5 + As a minimum, the file would look like the following, using the numbers + from the examples used above, comment lines start with a '#' + + # mynet mynode myzone + 93.57 89 unimelb-CompSci + # bridgenet bridgenode bridgeIP + 93.57 90 132.45.67.90 + + 10. Find out what UDP ports are being used on the IP network. These are + also called the "NIC Assigned" ports. These ports map to AppleTalk socket + numbers and are used to deliver packets to the correct UNIX processes. By + default, CAP will use the ports starting at 768 so that the RTMP socket + number 1 maps to UDP port 769 and the ECHO socket 4 maps to 772. The + official port range starts at 200, so RTMP becomes 201 and ECHO becomes + 204. To ensure that CAP uses the official ports, add the following entries + to the file /etc/services or the NIS database + + at-rtmp 201/udp + at-nbp 202/udp + at-echo 204/udp + at-zis 206/udp + + The port numbers should already be defined in the gateway configuration. + + Continue testing from the [10] Verification step in cap60/doc/install.ms + + Note: if you are using CAP with Native EtherTalk then ignore all but step 1. + The Native EtherTalk code is able to learn the network configuration. If + you have an /etc/atalk.local file, you should remove it. If there are no + other routers on the network, start aarpd with "*" as the zone name. The + UDP ports are also used in Native EtherTalk, as markers for sockets in use. + If a CAP process has trouble starting the ZIS listener or ECHO or NBP + sockets are unavailable, consider installing the official UDP port entries. + *** doc/uar.cookbook.orig Sat Feb 5 12:42:16 1994 --- doc/uar.cookbook Sat Feb 5 12:48:33 1994 *************** *** 0 **** --- 1,86 ---- + Herewith 10 easy steps to installing CAP with UAR: + + 1. Get the UAR package (mac/uar.tar.Z) via anonymous FTP from munnari.OZ.AU + and place it in a local directory 'uar'. 'cd uar', un-compress and un-tar + the package with 'compress -d uar.tar.Z' and 'tar -xvf uar.tar' + + 2. Check the README to ensure that your host is supported, currently UAR + supports Phase 1 and Phase 2 EtherTalk networks connected to SUN, DEC ULTRIX, + SGI IRIX, Sony NEWS 4.2, HP-UX and IBM RS6000 AIX workstations, and Phase 1 + only on Sony NEWS pre-4.2 workstations. + + 3. Edit the 'Makefile' to add the necessary info to CFLAGS= and LIBS= + The requirements are listed per machine type (only NEWS, AIX & Solaris 2.N). + + 4. Compile the program by typing 'make'. If compilation procedes without + error, type 'make install'. This step copies the binary to /usr/local/cap/uar + + 5. Decide on whether or not you are going to run UAR as a "seed router". + That is, if UAR is to be configured with details of your local AppleTalk + network or is to determine information empirically from the network. For + UAR to function as a "seed router", you must create a uar.conf file that + contains network number(s) and zone name(s) for each of the participating + ethernet interfaces on your UAR host (see the sample uar.conf provided). + The information in uar.conf *must* be identical to the configuration in + any other AppleTalk routers on the local networks, this is not optional! + Normally your campus/institution network manager is the best source of + such information. + + 6. If you are absolutely certain that there are no other local AppleTalk + routers then you may choose numbers for the "network", "networklo" and + "networkhi" entries. A "node" entry is optional. Network numbers are + 16-bit quantities and can range from 1 to 65534 (the values 65280 to + 65534 are reserved as the "startup range" on Phase 2 networks, don't + assign a network number in this range). These 16-bit numbers can also + be represented as two decimal numbers separated by a dot. In this + notation, 56284 is represented as 219.220 (ie: 219 x 256 + 220). The + node number is an 8-bit number, the valid range is 1 - 254 on Phase 1 + AppleTalk networks and 1 - 253 on Phase 2 AppleTalk networks (assume + Phase 2 for recent Macintoshes unless you know otherwise). Node numbers + specified for UAR should be towards the high end of the range, ie: 253. + You must also choose a zone name or list of zone names for your network, + in the latter case specify one of them as the "default" zone name. The + interface names are the device names for your ethernet interfaces and + can be listed using the command 'netstat -i'. Under AIX, use "ent0", + "ent1" rather than the listed "en0", "en1". + + 7. Ensure that your CAP distribution is at least at patch level 144. + Run the Configure script and answer 'y' or 'yes' to the question + "Do you wish to use UAR (Unix AppleTalk Router) (default no) ?" and 'y' + or 'n' as necessary to "Do you want Phase 2 compatibility (no) ? " + Run 'gen.makes', 'make include' and 'make programs'. See the CAP + documentation for more details. + + 8. To use UAR with CAP you must specify an interface for CAP to be + "attached" to. With a uar.conf file, this is achieved with a "cap on" + entry, all other interfaces should have "cap off". If no uar.conf file + exists then run UAR with a -C option. This attaches CAP to the first + interface name listed in the UAR arguments. + + 9. Run UAR. For example, on a single interface machine where UAR is used + only to support CAP (and not in it's usual function as an AppleTalk Router) + you would use + + uar -C le0 + + or, on a multiple interface machine + + uar -C ie1 ie0 + + where CAP is attached to "ie1", or with a uar.conf file + + uar et0 enp0 + + where "et0" and "enp0" are listed in the uar.conf file with "interface" + entries containing network and node numbers, zones and one "cap on" entry. + + 10. Check for "/etc/etalk.local" created by UAR. Normally this takes up + to 15 seconds to appear (so in a start-cap-servers file insert a "sleep 20" + after starting UAR before starting the rest of the CAP programs). With CAP + compiled for use with UAR it should now be possible to run test programs such + as 'cap60/samples/getzones' and 'cap60/samples/atlook' and see meaningful + results. If not, consult your local network administrator or send email to + uar@munnari.OZ.AU. Please note that UAR vers 1.0 is FreeWare. A ShareWare + or site-license fee is payable for UAR version 1.1. + + *** doc/glossary.orig Sat Feb 5 12:42:16 1994 --- doc/glossary Sat Feb 5 12:48:31 1994 *************** *** 0 **** --- 1,75 ---- + CAP GLOSSARY + + CAP Columbia AppleTalk Package + A freeware suite of programs that partially implement the AppleTalk + protocol stack on a variety of UNIX machines. Includes an AFP 2.0 + AppleShare Server, LaserWriter Spooler and lpr/lpd "input" filter. + + ETHERTALK + AppleTalk protocols transmitted in specific type Ethernet packets. + May be Phase 1 (Ethernet packets type 0x809B) or Phase 2 (IEEE 802.3 + Ethernet packets with 0xAAAA03 802.2 header and 0x080007809B SNAP + headers). CAP in "Native EtherTalk" mode uses AppleTalk in Ethernet. + + LOCALTALK + AppleTalk protocols transmitted over twisted pair cable at + 230.4Kbits/second. + + IPTALK IP encapsulated AppleTalk + AppleTalk protocols transmitted within IP packets. Usually used with + CAP on UNIX hosts that are unable to speak EtherTalk. Requires an + external AppleTalk gateway to translate IPTalk to/from EtherTalk. + + UAB UNIX AppleTalk Bridge + Phase 1 EtherTalk Router. Used to connect two EtherTalk networks + together via Ethernet interfaces on a UNIX host. Also supports + CAP processes via local UDP/IP loopback using modified IPTalk. + Bundled with CAP. + + UAR UNIX AppleTalk Router + Phase 1/Phase 2 EtherTalk Router for UNIX boxes. Also supports CAP + and simple AppleTalk tunneling over IP networks. Not bundled with + CAP. Available in two versions: freeware with basic features and + shareware with extra features (supports ARNS clients, NBP registry). + + AUFS AppleTalk UNIX File Server + UNIX based AppleShare server. Supports Apple Filing Protocol v 2.0. + Nominated UNIX directories can be mounted as a AppleShare Volumes + for storage of Mac files. + + LWSRV LaserWriter Server/Spooler + UNIX based LaserWriter Spooler. Macintosh print jobs are spooled to + the UNIX printer queue for subsequent printing via PAPIF or serially + connected printer. + + PAPIF PAP Input Filter + BSD lpd filter for sending print-jobs to AppleTalk connected + printers. Can be used in a script for non-BSD printing systems. + + AARPD AARP Daemon + UNIX process for handling AppleTalk Address Resolution Protocol (AARP) + lookups. Stores ethernet hardware address/AppleTalk address mappings + which are available to other CAP processes via RPC. Also handles + updating of /etc/etalk.local. Used only with "Native EtherTalk". + + ATIS AppleTalk Information Server + UNIX process for handling AppleTalk Name Binding Protocol (NBP) + lookups and registrations, AppleTalk Echo Protocol (AEP) traffic + and Routing Table Maintenance Protocol (RTMP) data. Sends RTMP + router updates to AARPD via RPC. Other CAP processes register + Chooser visible names with ATIS. + + GETZONES + List AppleTalk zones for the local Internet. + + ATLOOK AppleTalk Lookup + Lists AppleTalk NBP entities visible on the network. Also ATPINGER + for sending Echo Protocol packets and ATLOOKLWS for LaserWriters. + + SNITCH UNIX InterPoll client + Equivalent to Macintosh "Responder" program. Provides limited + information about the CAP host to Mac InterPoll lookups. + + AppleTalk Reference + "Inside AppleTalk, Second Edition", Sidhu, Andrews, Oppenheimer. + Addison-Wesley, ISBN 0-201-55021-0 *** doc/install.ms.orig Sun Mar 8 22:54:52 1992 --- doc/install.ms Fri Feb 4 15:35:13 1994 *************** *** 4,40 **** .AB This document gives a step by step approach to installation of the Columbia AppleTalk Package for UNIX. .AE .SH ! NOTES ON CAP WITH ETHERTALK .LP .nh ! This file describes how to install CAP in both its "traditional" ! configuration (IPTalk, based on Appletalk protocols encapsulated in ! UDP/IP packets) and ! a version of CAP that supports Native EtherTalk (Phase 1 or 2), Kernel ! AppleTalk (Phase 1) or UAB \- the UNIX AppleTalk Bridge (Phase 1 only). .sp ! Native EtherTalk works on a limited range ! of hosts - those that support the Stanford ENET Packet Filter model, ! currently SUN workstations or DEC ULTRIX hosts only. ! UAB will run on SGI IRIX, Sony NEWS, DEC ULTRIX or SUN workstations. .LP ! The setup for Native EtherTalk, Kernel AppleTalk or UAB is performed ! from within ! Configure (but only if the Configure script determines that the host is suitable) by modifying the CAP libraries as necessary. Refer to the README files in the support/uab or support/ethertalk directories for more information. .sp The choice of whether to use IPTalk, ! Native EtherTalk/Kernel AppleTalk or UAB depends on your network setup. If you have a majority of Macintoshes on LocalTalk connected to ! an IPTalk gateway (see below) then use CAP in the IPTalk mode (default). If ! your Macintoshes are mostly connected via EtherNet and you have other EtherTalk gateways (Ciscos for example) then use CAP with Native EtherTalk or Kernel AppleTalk. If you have no other gateways, or need to bridge two ! Phase 1 EtherTalk networks then use UAB. On a SUN you may choose to use the native NIT interface or install kernel modifications to run the 'ENET' driver. .SH --- 4,58 ---- .AB This document gives a step by step approach to installation of the Columbia AppleTalk Package for UNIX. + .sp .AE .SH ! SEE ALSO .LP + Notes and cookbooks in cap60/doc and UNIX manual entries in cap60/man. + .SH + Notes on CAP with EtherTalk + .LP .nh ! This file describes how to install CAP in its "traditional" default ! configuration IPTalk - which is based on Appletalk protocols encapsulated in ! UDP/IP packets - and ! configurations that support communications via EtherTalk Phase 1 or Phase ! 2 - Native EtherTalk, Kernel AppleTalk or the UNIX AppleTalk ! Bridge, UAB (both Phase 1 only, obsolete) or via the UNIX AppleTalk Router, ! UAR. .sp ! Native EtherTalk mode is available on a limited range ! of hosts - those that support the Stanford ENET Packet Filter ! model - currently SUN workstations and DEC OSF/1 or ULTRIX hosts only. ! UAR will run on SGI IRIX, Sony NEWS, DEC OSF/1 or ULTRIX, SUN SunOS ! and Solaris, IBM AIX and HP-UX workstations. IPTalk mode is supported ! on all of the above and more and is easily ported to other platforms. ! .sp ! .IP ! Note: UAR is not bundled with CAP, see the CAP FAQ for more information, ! the most recent copy of the FAQ ! can always be obtained via FTP from munnari.OZ.AU in mac/CAP.faq. ! .sp .LP ! The setup for Native EtherTalk, Kernel AppleTalk, UAB/UAR is performed ! from within the ! Configure script (but only if Configure determines that the host is suitable) by modifying the CAP libraries as necessary. Refer to the README files in the support/uab or support/ethertalk directories for more information. .sp The choice of whether to use IPTalk, ! Native EtherTalk/Kernel AppleTalk or UAB/UAR depends on your network setup. If you have a majority of Macintoshes on LocalTalk connected to ! an IPTalk gateway (see "Prerequisites" below) then use CAP in IPTalk mode. ! If your Macintoshes are mostly connected via EtherNet and you ! have other EtherTalk gateways (Ciscos for example) then use CAP with Native EtherTalk or Kernel AppleTalk. If you have no other gateways, or need to bridge two ! EtherTalk networks, or want to run CAP with EtherTalk on hosts that don't ! have Native EtherTalk support then use UAR. On a SUN running SunOS you may ! choose to use the native NIT interface or install kernel modifications to run the 'ENET' driver. .SH *************** *** 43,49 **** To use CAP with IPTalk you must have a hardware bridge that has the ability to gateway IPTalk packets to and from EtherTalk and/or LocalTalk. Suitable candidates are the Webster MultiPort GateWay, ! Shiva FastPath and Cayman GatorBox. The code originally written to handle the IPTalk gateway function on the FastPath is often known as KIP (Kinetics IP). .sp --- 61,68 ---- To use CAP with IPTalk you must have a hardware bridge that has the ability to gateway IPTalk packets to and from EtherTalk and/or LocalTalk. Suitable candidates are the Webster MultiPort GateWay, ! Cisco Router, Shiva FastPath and Cayman GatorBox. The code originally ! written to handle the IPTalk gateway function on the FastPath is often known as KIP (Kinetics IP). .sp *************** *** 50,65 **** The file /etc/atalk.local (see atalk.local.5 in the cap60/man directory) contains routing information for the static IPTalk network and node numbers. It is not necessary to create this file ! if you are using Native EtherTalk or UAB drivers and its presence may cause problems if you are using Native EtherTalk without a gateway box. .sp Before you start here, you should have read the "README" and "NOTES" ! files. The README file gives a very basic overview of CAP necessary ! to understand the following. .sp The installation NOTES file tries to point out places where you might want to redefine things a little, explains configurations, and points out machine dependencies. .SH Review .LP --- 69,87 ---- The file /etc/atalk.local (see atalk.local.5 in the cap60/man directory) contains routing information for the static IPTalk network and node numbers. It is not necessary to create this file ! if you are using Native EtherTalk or UAR drivers and its presence may cause problems if you are using Native EtherTalk without a gateway box. .sp Before you start here, you should have read the "README" and "NOTES" ! files in the cap60 directory. The README file gives a very basic overview ! of CAP necessary to understand the following. .sp The installation NOTES file tries to point out places where you might want to redefine things a little, explains configurations, and points out machine dependencies. + .sp + A simple cookbook approach to CAP installation and printing is available in + cap60/doc/print.cookbook. .SH Review .LP *************** *** 78,84 **** Versions of IPTalk/UDP gateway code prior to April, 1988 had "well known" AppleTalk DDP sockets mapped to priviledged UDP/IP ports starting at ! 768 (so the NBP socket was UDP port 770, ECHO was 772 etc). .sp In April, 1988, the NIC assigned a range of UDP ports starting at 200 for the defined DDP services and assigned --- 100,106 ---- Versions of IPTalk/UDP gateway code prior to April, 1988 had "well known" AppleTalk DDP sockets mapped to priviledged UDP/IP ports starting at ! 768 (so the NBP socket 2 was UDP port 770, ECHO socket 4 was 772 etc). .sp In April, 1988, the NIC assigned a range of UDP ports starting at 200 for the defined DDP services and assigned *************** *** 85,95 **** the names "at-rtmp", "at-nbp", "at-echo", "at-zis" (not "at-zip" as documented in some versions of KIP). In addition, ports were allocated where there were holes or unused sockets between ! at-rtmp and at-zis. CAP Release 6 and above dynamically decides which mappings to use by doing "getservbyname()" calls based upon those names and using the UDP port number returned. getservbyname() normally searches the file ! /etc/services but the information may also be cached by a Yellow Pages ! server. If the requested service name does not exist, then the old mappings (based on 768) are used. .sp --- 107,118 ---- the names "at-rtmp", "at-nbp", "at-echo", "at-zis" (not "at-zip" as documented in some versions of KIP). In addition, ports were allocated where there were holes or unused sockets between ! at-rtmp and at-zis. CAP Release 6.0 ! and above dynamically decides which mappings to use by doing "getservbyname()" calls based upon those names and using the UDP port number returned. getservbyname() normally searches the file ! /etc/services but the information may also be cached by a NIS (aka Yellow ! Pages) server. If the requested service name does not exist, then the old mappings (based on 768) are used. .sp *************** *** 131,144 **** however, the commands to unpack the distribution are .sp .nf ! % compress \-d cap60.tar.Z ! % tar xf cap60.tar .fi .sp ! This creates a 'cap60' directory at the current level. CAP updates and bug fixes are normally distributed as 'patch' files. These are simply context diffs ! of the original and the new files (see diff(1)). To apply the patches with a minimum of effort, it is recommended that you use the 'patch' program written by Larry Wall. This can be obtained from sites that archive postings from the newsgroup comp.sources.unix in the directory --- 154,169 ---- however, the commands to unpack the distribution are .sp .nf ! % compress \-d cap60.pl100.tar.Z ! % tar xf cap60.pl100.tar .fi .sp ! This creates a 'cap60' directory containing the ! patch level 100 CAP distribution. CAP updates and bug fixes are normally distributed as 'patch' files. These are simply context diffs ! of the original and the new files (see the UNIX command diff(1)). ! To apply the patches with a minimum of effort, it is recommended that you use the 'patch' program written by Larry Wall. This can be obtained from sites that archive postings from the newsgroup comp.sources.unix in the directory *************** *** 154,163 **** New patches are applied from the top level directory with the command .sp .nf ! % patch \-p < cap60.patches/cap60.patch0NN .fi .sp ! where NN is the patch number. The \-p option tells patch to obtain information about which file to alter from the patch header. If you attempt to apply a patch more than once, patch will enquire about "a reversed or previously applied patch", answering yes to this will remove the patch, --- 179,188 ---- New patches are applied from the top level directory with the command .sp .nf ! % patch \-p < cap60.patches/cap60.patchNNN .fi .sp ! where NNN is the patch number. The \-p option tells patch to obtain information about which file to alter from the patch header. If you attempt to apply a patch more than once, patch will enquire about "a reversed or previously applied patch", answering yes to this will remove the patch, *************** *** 184,190 **** normally enough to build an IPTalk version of CAP with a basic feature set, it is also possible to include an extra set of features for the various CAP components, see the ! file CAP60.README for more details. .sp One Configure option allows the CAP files to be built and used within a single directory hierarchy. This is useful for testing or evaluation --- 209,215 ---- normally enough to build an IPTalk version of CAP with a basic feature set, it is also possible to include an extra set of features for the various CAP components, see the ! files CAP60.README and m4.features for more details. .sp One Configure option allows the CAP files to be built and used within a single directory hierarchy. This is useful for testing or evaluation *************** *** 222,234 **** .fi .sp .LP ! After Configure, or if you have edited the file m4.setup, run gen.makes to (re)generate your baseline makefiles. There are "Makefile"s included, but they are included for systems without the m4 preprocessor and shouldn't be used unless absolutely necessary. Some machines will generate a 'make' warning message about the presence of both ! makefile and Makefile. Ignore these. .SH [5] Install header files. .sp --- 247,262 ---- .fi .sp .LP ! After Configure, or if you have edited the files m4.setup or m4.features, run gen.makes to (re)generate your baseline makefiles. There are "Makefile"s included, but they are included for systems without the m4 preprocessor and shouldn't be used unless absolutely necessary. Some machines will generate a 'make' warning message about the presence of both ! makefile and Makefile. You can ignore these warnings or, after the ! first gen.makes, ! run 'make spotless' which removes both makefile versions. At this point it ! is necessary to run gen.makes again to continue with the CAP build. .SH [5] Install header files. .sp *************** *** 260,267 **** libraries in cap60/lib programs and servers in cap60/bin etc stuff in cap60/etc - - (you must create cap60/bin) .fi .sp In this case, it is not necessary to install the header files. --- 288,293 ---- *************** *** 320,329 **** .SH [10] Verification. .LP - (You should have already tested the gateway software before - proceeding further) .sp ! If you are using IPTalk, you must have /etc/atalk.local installed (see the file man/atalk.local.5 for details of the file contents). Skip from here to step A. below. .sp --- 346,356 ---- .SH [10] Verification. .LP .sp ! If you are using IPTalk, ! you should have already tested the gateway software before ! proceeding further and ! you must have /etc/atalk.local installed (see the file man/atalk.local.5 for details of the file contents). Skip from here to step A. below. .sp *************** *** 331,337 **** using Native EtherTalk, then you should read the file cap60/support/ethertalk/README and then run aarpd with suitable interface and zone name arguments. Follow this by ! atis which determines the necessary network numbers (see step C below for atis verification procedure). .sp If you are using Kernel AppleTalk, ensure that the necessary --- 358,364 ---- using Native EtherTalk, then you should read the file cap60/support/ethertalk/README and then run aarpd with suitable interface and zone name arguments. Follow this by ! atis which determines the AppleTalk network numbers from the network (see step C below for atis verification procedure). .sp If you are using Kernel AppleTalk, ensure that the necessary *************** *** 343,348 **** --- 370,379 ---- and the files to which it refers. Ensure that you edit and install the 'bridge_desc' file. .sp + If you are using UAR, see the README file supplied with the distribution. + The CAP FAQ also contains information about where to get UAR and its use + with CAP. + .sp At this point, the /etc/etalk.local file should look similar to the following: .sp *************** *** 389,394 **** --- 420,430 ---- ... .fi .sp + If getzones prints a warning message or fails with a -1096 error then the + problem is usually that there is no AppleTalk router on the local network + and therefore no zones available. In this situation you should be using "*" + as the zone name argument for aarpd. + .sp The next program to try is .I atlook. If everything is okay, you *************** *** 514,520 **** CHANGES FROM RUTGERS CAP .LP There are some important changes to note if you are already using Native ! EtherTalk from the Rutgers distribution. Shared memory is no longer used, the file /etc/cap.ether.shared is thus not required. The modifications needed to the file /etc/atalk.local to select a zone and an ethernet interface are not needed as CAP now uses the file /etc/etalk.local for both Native --- 550,556 ---- CHANGES FROM RUTGERS CAP .LP There are some important changes to note if you are already using Native ! EtherTalk from the original Rutgers distribution. Shared memory is no longer used, the file /etc/cap.ether.shared is thus not required. The modifications needed to the file /etc/atalk.local to select a zone and an ethernet interface are not needed as CAP now uses the file /etc/etalk.local for both Native *** lib/cap/abversion.c.orig Tue Feb 1 15:53:27 1994 --- lib/cap/abversion.c Fri Feb 4 15:38:19 1994 *************** *** 1,7 **** /* ! * $Author: djh $ $Date: 1994/02/01 04:53:21 $ ! * $Header: /mac/src/cap60/lib/cap/RCS/abversion.c,v 2.88 1994/02/01 04:53:21 djh Rel djh $ ! * $Revision: 2.88 $ * */ --- 1,7 ---- /* ! * $Author: djh $ $Date: 1994/02/04 04:38:13 $ ! * $Header: /mac/src/cap60/lib/cap/RCS/abversion.c,v 2.89 1994/02/04 04:38:13 djh Rel djh $ ! * $Revision: 2.89 $ * */ *************** *** 32,38 **** myversion.cv_name = "CAP"; myversion.cv_version = 6; myversion.cv_subversion = 0; ! myversion.cv_patchlevel = 188; myversion.cv_rmonth = "February"; myversion.cv_ryear = "1994"; switch (lap_proto) { --- 32,38 ---- myversion.cv_name = "CAP"; myversion.cv_version = 6; myversion.cv_subversion = 0; ! myversion.cv_patchlevel = 189; myversion.cv_rmonth = "February"; myversion.cv_ryear = "1994"; switch (lap_proto) { *** README.orig Tue Feb 1 15:54:09 1994 --- README Fri Feb 4 15:43:49 1994 *************** *** 2,8 **** CAP - Columbia AppleTalk Package for UNIX o RELEASE NOTES ! o CAP Distribution 6.0, Patch Level 188, February 1994 Notice ------ --- 2,8 ---- CAP - Columbia AppleTalk Package for UNIX o RELEASE NOTES ! o CAP Distribution 6.0, Patch Level 189, February 1994 Notice ------ *************** *** 28,34 **** Portions Copyright (c) 1984, Apple Computer Inc. Gene Tyacke, Alan Oppenheimer, G. Sidhu, Rich Andrews. ! Portions Copyright (c) 1990, 1991, 1992 The University of Melbourne Modules copyright in part or whole by any other entity than Columbia University are clearly marked as such. --- 28,34 ---- Portions Copyright (c) 1984, Apple Computer Inc. Gene Tyacke, Alan Oppenheimer, G. Sidhu, Rich Andrews. ! Portions Copyright (c) 1990 - 1994 The University of Melbourne Modules copyright in part or whole by any other entity than Columbia University are clearly marked as such. *************** *** 101,112 **** info-appletalk-request@andrew.cmu.edu. Important documentation resides in: ! NOTES - installation notes: READ THIS BEFORE STARTING INSTALLATION ! PORTING - notes on porting CAP to machines it doesn't know about ! MANIFEST - a list of files that comprise CAP doc/install.ms - stepwise installation document: assumes you have read NOTES and this document What's in CAP ------------- --- 101,117 ---- info-appletalk-request@andrew.cmu.edu. + Documentation + ------------- + Important documentation resides in: ! doc/install.ms - stepwise installation document: assumes you have read NOTES and this document + doc/print.cookbook - simple steps to implement CAP printing + man/* - UNIX manual entries for the various CAP programs + NOTES - installation notes: READ THIS BEFORE STARTING INSTALLATION + PORTING - notes on porting CAP to machines it doesn't know about What's in CAP -------------