🚀 go-pugleaf

Seppo Kallio writes:
>I have problems with FastPath 4 with K-STAR configuration.
>The atlook in cap/aufs does not find the FastPath 4. 

After suffering through these same problems of my own several
months ago, I have responded directly to many others facing
similar difficulties.  So I thought I might post it to the net,
in hopes that I don't have to do it some many times in the
future!  My apologies for burning bandwidth.

I'll include my config files as an example.  Admittedly
my setup is quite simple - a few unix hosts, one FP-4,
a bunch of MacSEs and MacIIs and LW+s all living on localtalk.
No subnetting, no ethertalk.

First a few issues:

1) You must use atalkad.  Things do not seem to work if you
try to configure completely from the FastPath Manager II.
If you don't have atalkad, find kip0688; it's in there.
I know of a few minor changes for use on a sparc (Sun 4),
I'd be happy to send them out.

2) K-STAR does not and cannot use the new 200+ WKS udp port assignments.
You must list the old 768+ range assignments in your services database
on the unix host.  These entries (from my /etc/services) should look like:

#
# Appletalk (CAP) entries
#
at-rtmp         769/udp                         # udp: rtmp
at-nbp          770/udp                         # udp: nbp
at-echo         772/udp                         # udp: echo
at-zip          774/udp                         # udp: zip

Likewise, you need to use the value "S0" for your ddprangestart
in your atalkatab.

3) Create atalkatab.

Choose (if not already assigned) network numbers for your
AppleTalk networks.  The FastPath Manager will tell you
the node numbers automatically assigned to the LocalTalk
and AppleTalk-in-IP sides of the FP-4.  Use these in your
atalkatab.  I've not played around much with zone names,
but I think you can do just about whatever you want.

Be sure to choose the proper network specification based on your
network type (N1 for class C, N2 for class B, N3 for class A).
The FP-4 should be given the configuration parameters "KC".

Specify the obvious for the ipbraod, ipname, ipdebug, ipfile,
ipother, atnetet, flags, ipstatic, and ipdynamic. atneta and
atnete should have the same values given for the net numbers
in the first two configuration lines.

My atalkatab looks like:

# SFI KFPS configuration
12.0    N1      192.12.12.0     SantaFeInstitute        #sfi, appletalk-in-IP
12.1    KC      192.12.12.200   SantaFeInstitute        #sfi, localtalk
        I192.12.12.255  I192.12.12.1            #ipbroad ipname
        I192.12.12.1    L0                      #ipdebug ipfile
        L0 L0 L0 L0     S0 S0                   #ipother atnetet ddprangestart
        LX0             S20     S5              #flags ipstatic ipdynamic
        S12.1           S12.0                   #atneta atnete

4) Create atalk.local for your server (and likewise for other
unix hosts).

mynet and bridgenet were assigned in atalkatab, mynode is
generally set to the last part of the hosts IP address,
though this won't necessarily work in a situation with
subnetting, bridgenode is assigned by FP Manager, myzone
is the obvious, and bridgeIP is the IP address of the FP-4

my atalk.local on my server looks like:

# mynet mynode myzone
12.0 1 SantaFeInstitute
# bridgenet bridgenode bridgeIP
12.0 200 192.12.12.200

5) Now, from the FastPath Manager II (I should point out that
I'm using version 4.1 which reports a PROM version 4.1, and
that nasty old PAL has been replaced)
(Also note - you may need to use PAUSE for the download or
config steps below)

a) Do a *Total* RESET

b) Select K-STAR from the Configuration menu

c) Turn Autoconfig *off*, and Remote Boot *on*

d) Download K-STAR DOWNLOAD

e) RESTART

f) Set the following configuration items *only* (any more
and it may not work!):

    IP Address of FastPath-4
    IP Subnetwork Mask (if needed)
    IP Address of Default Router
    IP Address of Administrative Host (running atalkad)

My values are:
    192.12.12.200
    0.0.0.0
    192.12.12.128
    192.12.12.1

g) Hit GO, and you better see "K-Star" in the diagnostics window
after a few seconds.  Now, admittedly, my system generates an
"ETALK not seeded" message about every 10 seconds, but it
doesn't *seem* to create a problem.  Maybe someone out there
knows how to make this go away.


If everything is wonderful, atlook will suddenly report
"IPADDRESS XXXXXX ...", giving the IPADDRESS of the FP-4.
According to the literature, this should say "IPGATEWAY",
but there seems to be some bug lingering around.  In any
case, you will also see entries for any LaserWriters
and any Macs running Telnet or the like.

Also, I'm not at all sure, but some on some systems,
you may need to compile in the old 768+ udp ports when
you build CAP.  My system uses the yp database, so only the
/etc/services entry is necessary.


I hope that this is useful.  It's unfortunate that the
Kinetics manual doesn't say a little more about doing
remote boots with atalkad - it was not at all obvious
to me, especially with a FP Manager that seemed to do it all!
Credit is due to all those folks in netland who helped
me out in my time of need, especially those out at Stanford.
Excuse me for not reproducing your (some forgotten) names
here.

Stephen C. Pope
the Santa Fe Institute
scp@sfi.santafe.edu