🚀 go-pugleaf

Kevin Brooks writes <27062@apple.Apple.com>:

   The fastpath 4 manual states that you can configure the fastpath to
   use atalkad daemon for configuration administration and CAP use.  Has
   anyone set this type of environment up?  How does atalkad interact 
   with K-Star?  Do you use the configuration file included with the KIP
   CAP release or do you configure K-Star in the normal way and just 
   download any additional configuration information from the atalkad
   server?  I have tried several ways to get the fastpath to talk to 
   the atalkad server with no luck.  I've got the appletalk port numbers 
   assigned to the 768+ range. 

   How do I get the fastpath 4 to use the atalkad daemon?  Am I missing
   something?

   Any help would be appreceiated.


   Kevin Brooks


I am using a a FastPath-4 (PROM version 4.1 as reported by FastPath Manager)
together with a Sun 4 SunOS4.01 running atalkad on the ethernet
side and a variety of AppleTalk hosts on the LocalTalk side.

After a few weeks of battling to get CAP 5.0 running, some
friendly folks pointed out the *right* way to use atalkad to
configure K-Star.  The trick is to completely reset the FastPath,
select K-Star mode, set auto-configure off and remote boot on,
download K-Star, Restart, then configure THE FOLLOWING INFORMATION
*ONLY*:

	1) IP address of FastPath
	2) IP address of administrative host (running atalkad)
	3) Subnet mask (only if not default).

Make sure atalkad is running with all the proper info in atalkatab
(you are correct to use the 768+ port range; be sure to specify
a ddpstartrange of S0 in atalkatab), then tell the FastPath to Go.

If everything's working, atis/atlook should report at least
an IP-GATEWAY or IP-ADDRESS record for your FastPath.

In my experience, the proper reset/boot sequence with the FastPath4
was crucial to the proper operation.  Too bad it's not so clearly
illustrated in the FastPath Manager manual...

Stephen C. Pope
The Santa Fe Institute
scp@santafe.edu