Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!fluke!jeff
From: jeff@tc.fluke.COM (Jeff Stearns)
Newsgroups: comp.protocols.appletalk
Subject: Async AppleTalk && CAP
Keywords: Async AppleTalk CAP KIP
Message-ID: <7560@fluke.COM>
Date: 4 Apr 89 18:10:50 GMT
Sender: news@tc.fluke.COM
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 31

I have CAP installed and running.  I'm holding a floppy disk containing
Dartmouth's Async AppleTalk.  We have Macs and modems.  We also have a
GatorBox.

It seems like these are the ingredients for doing Something Interesting.

I'm thinking of creating a simple scheme so that a Mac running Async AppleTalk
can dial up from home and access files on the NFS.

There are several options.  Absolutely easiest would be to use a GatorBox
as a NFS<->KIP bridge; all that's missing is a KIP<->Async AppleTalk "repeater"
process running on, say, a Sun.

Or use the GatorBox as an NFS<->EtherTalk bridge, and write an
EtherTalk<->Async AppleTalk "repeater" program for the Sun.

A third option would be to skip the GatorBox and do all the work on the Sun.
This seems like substantially more work, because the Sun now has to play the
role of an AppleTalk bridge.  Still, CAP gives a good head start on the
problem; it seeems like I could rewrite the AUFS packet driver so that it
speaks Async AppleTalk instead of KIP.

It seems so straightforward that I'm sure others have already done it.

What problems did you run into?  Was it worth the trouble?
-- 
    Jeff Stearns        John Fluke Mfg. Co, Inc.               (206) 356-5064
    jeff@tc.fluke.COM   {uw-beaver,microsoft,sun}!fluke!jeff
						  
PS - Calling all users of the Vitalink TransLAN IV Ethernet bridge! Please
     drop me a line.