Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.milw.wisc.edu!bionet!ames!oliveb!pyramid!nsc!csi!varian!kinetics!minshall
From: minshall@kinetics.UUCP (Greg Minshall)
Newsgroups: comp.protocols.appletalk
Subject: Re: KIP/CAP/K-STAR problems when upgrading from FastPath 3 to 4
Message-ID: <762@kinetics.UUCP>
Date: 7 Jun 89 21:17:36 GMT
References: <673@ndcheg.cheg.nd.edu>
Organization: Kinetics, Inc., Walnut Creek, CA
Lines: 73

From article <673@ndcheg.cheg.nd.edu>, by pigeon@ndcheg.cheg.nd.edu (Rich Pigeon):
...
> My /etc/atalkatab
> 
> 55.6	N1	129.74.6.0	Ethernet	#ms ob
> 56.1	K	129.74.6.193	apple-cheg	#chem.eng.appletalk
> 	I129.74.6.193	I129.74.6.8		#ipbroad ipname
> 	I129.74.6.8	L0			#ipdebug ipfile
> 	L0 L0 L0 L0	S0	S0		#ipother unused ddprangestart
> 	LX0		S6	S10		#flags ipstatic ipdynamic
> 	S56.1	S55.6		"Ethernet"	#atneta atnete zonea

I don't understand why you have "I129.74.6.193" set as the IP broadcast
address.  I would expect a number (from your subnet mask in the K-STAR
data) like I129.74.6.255 (or I129.74.6.0, if your CAP host is a 4.2 machine).

> 
> FastPath 4 Configuration: (using FastPath Manager II v4.1)
...

I always suggest that people using atalkad (ie: specifying the IP address
of the administrator host) leave everything "blank" ("*"s for zone names,
0's for network numbers) except the IP address of the KFPS AND the IP
address of the administrator host (host running atalkad).  [Plus whatever
options, including the all-important option 4; plus turning on the Remote
Boot switch.]

...
> 
> When we tried to specify the UDP side with the same inforamtion as the Ethernet
> side, AUFS worked fine, along with Telnet, but we could not print from Ethernet
> to the LocalTalk LaserWriters. 

OK.  When you are using "IP talk" (ie: Appletalk encapsulated in UDP in IP),
your fastpath has 3 *separate* DDP networks.  The first runs over
LocalTalk.  The second runs over EtherTalk (though FastPath manager calls
it "Ethernet side").  The third runs over IPtalk (though the FastPath manager
calls it "UDP Side" or some such thing).

THESE ARE THREE SEPARATE NETWORKS!  They need to be configured with three
separate (distinct) network numbers!  If you don't do it, it doesn't work
right.  (Again, my standard apology for the state of the current Kinetics'
documentation, and a sincere acknowledgement that I don't wonder why everyone
DOESN'T know this - I more wonder how anyone ever figured it out - it just
isn't well documented.)

So, if network number X is set for the EtherTalk network, you may not use
network number X for the IP talk network.

(Some of the confusion here revolves around the question "what is a network?"
After all, the IP talk network and the EtherTalk network run on the same cable;
aren't they, therefore, the same network?  My partial answer is that, for a
broadcast network, a network is the union of all machines that receive and
understand a particular node's broadcast packets.)

One additional point, the "atnete" entry in "atalkatab" relates to the
IP talk network, NOT the EtherTalk network.

> Putting in the IP Broadcast Address caused 
> problems on the LocalTalk side that weren't readily apparent.  Although all 
> LaserWriters would appear in the chooser, an NEC SilentWriter would not print
> on a regular basis.  It would signal that it was processing the document, but 
> no file would would actually print.  (We have had other problems with this 
> LaserWriter in the past -- seems to be very sensitive to problems in the 
> network.)

The above puzzles me, but I wonder what value for "IP Broadcast Address"
you used.

I hope this helps a bit.

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