Path: utzoo!censor!geac!jtsv16!uunet!lll-winken!ames!pacbell!varian!zehntel!kinetics!minshall
From: minshall@kinetics.UUCP (Greg Minshall)
Newsgroups: comp.protocols.appletalk
Subject: Re: Still stuck trying to set up cap with kstar on a kinetics
Message-ID: <758@kinetics.UUCP>
Date: 1 Jun 89 22:59:18 GMT
References: <1219@durin.sparta.COM>
Distribution: usa
Organization: Kinetics, Inc., Walnut Creek, CA
Lines: 62

(Down toward the bottom is some interesting information for K-STAR users...)

From article <1219@durin.sparta.COM>, by frankh@durin.sparta.COM (Frank Halsema):
> I have been trying to set up a Kinetics Fastpath 4 running kstar.  I have the
> bridge operational and NCSA Telnet works great. But I can not get atlook to
> "see" any of the appletalk devices. Not even the bridge itself. My CAP host is
> a Sun running 3.5 at address 192.0.0.7. Below are my configuration tables. Any
> help I can get would be greatly appreciated. Thanks in advance.

First, as has been pointed out in this newsgroup before (and as I may
have mentioned before), the current K-STAR documentation is quite bad,
especially in regards with how to set anything up.  That said...

If you are using "atalkad" (which you are) you want to leave everything
in the FastPath configuration file blank (0 for network numbers, * for zone
names, etc.), EXCEPT the IP address of the FastPath and the IP address of
the "administrator host" (ie: the host running atalkad).  In the example
you have given, you have configured everything by hand, but you should
really get all that information from atalkad.  Information configured
with FastPath manager takes precedence over atalkad-derived information
(conceivably the wrong design decision, but there it is), yet atalkad-derived
information is (in the miraculous event of a correctly-configured atalkatab
file) likely to be internally consistent.

So, rule #1 - leave out all the other configuration information.  (Except,
by the way, any OPTIONs you want to turn on - like 0-based IP broadcast
addresses, etc.  Also, you probably want "Remote Boot" on, just like you
currently have.)

...
> My /etc/atalkatab
> 55.0	N0	192.0.0.7  	Neverland	#Laguna Eng, appletalk-in-IP
> 57.0	E	192.0.0.195	Neverland	#Laguna Eng, ethertalk
> 56.0	KC	192.0.0.195	Neverland	#Laguna Eng, localtalk
> 	I192.0.0.0	I192.0.0.7		#ipbroad ipname
> 	I192.0.0.7	L0				#ipdebug ipfile
> 	L0 L0 L0 L0	%n  S200		#ipother atnetet ddprangestart
> 	L0		S3	S40		#flags ipstatic ipdynamic
> 	%n		%n			#atneta atnete

OK.  This is a restriction in the current version of K-STAR.  "ddprangestart"
should be specified as 0 (or, equivalently, 768).  Additionally, the "at-"
entries installed in /etc/services during the CAP 5.0 install should be
removed.  Then, restart CAP, and you should see what is going on.

ANNOUNCEMENT:  There is a new version of K-STAR available which removes this
restriction, as well as correcting a series of annoying bugs.  This version
will be included in new FastPaths (after some date).  Customers needing
this capability now can request the new K-STAR (version 7.0 - aren't version
numbers wonderful?) from Kinetics technical support at 1-415-947-0998.

> # mynet mynode myzone 
> 55.0 7 Neverland
> # bridgenet bridgenode bridgeIP
> 55.0 195 192.0.0.195 

This looks good.

Hope this helps.

Greg Minshall				Kinetics, a division of Excelan
minshall@kinetics.com			1-415-947-0998