[comp.protocols.appletalk] KIP0688/TOPS V2 compatability

duncan@comp.vuw.ac.nz (Duncan McEwan) (02/17/89)

I have just installed kip 0688 on a kinetics fastpath, and the appletalk admin
daemon on a pyramid running OSx 4.4.  I am able to use both SU-MacIP
telnet/ftp (v3.0) and NCSA telnet (v2.2) to communicate between a mac on
the localtalk and the pyramid on ethernet.

Unfortunately Mac's on the same localtalk can no longer use Tops (v2) to access
files from other Mac's.  The symptoms are that the Mac boots ok, but when the
user invokes the tops desk accessory, the Mac bombs with a system error, id=10
before tops comes up with the usual list of volumes.  I guess tops is sending
out a broadcast to locate all published volumes on the network, and not liking
one of the responses that it gets.

When we disconnect the Kbox from the appletalk, tops works fine, and when it is
connected but running the (old) kinetics supplied gateway code it also works
fine.  So it seems to be some interaction between tops v2 and kip 0688.

Here is an extract from the atalkad log file, showing what happens when we run
atalkad on the pyramid, and start the kip code running in the gateway.

2/17 11:54 ###	ATALKA daemon starting
2/17 11:54 (re)reading /usr/local/etc/atalkatab
2/17 11:54 art build: 3 entries, 64 maximum
2/17 11:54 zone names take 16 bytes in gateway
2/17 11:57 aaCONF to 0.0.0.0
2/17 11:57 aaROUTEI to 0.0.0.0
2/17 11:58 aaZONEq from 0.0.0.0
2/17 12:01 aaCONF to 0.0.0.0
2/17 12:01 aaROUTEI to 0.0.0.0
2/17 12:01 aaZONEq from 0.0.0.0
2/17 12:01 aaZONEq from 0.0.0.0

The 0.0.0.0 addresses look a little wierd, but I don't think they are related
to the problem (the pyramid "ping" program exhibits similar behaviour -- ie all
the received packets have an address of 0.0.0.0, regardless of what host you
ping, so I suspect this is a bug in pyramid's networking code).

Here is my atalkatab file.

55.9	N0	193.0.9.0	APMB1		#ethernet, appletalk-in-IP
57.9	E	193.0.9.100	APMB1		#ethertalk
56.1	KC	193.0.9.100	APMB1		#localtalk network
	I193.0.9.0	I193.0.9.41		#ipbroad ipname
	I193.0.9.1	L0			#ipdebug ipfile
	L0 L0 L0 L0	S57.9 	S200		#ipother atnetet ddprangestart
	LX0		S0	S10		#flags ipstatic ipdynamic
	S56.1	S55.9				#atneta atnete

The N0 field is because the ethernet has sun's running SunOS3.2 which only
supports the all-zero's form of broadcast address.  I added the "E"
specification *after* first observing the above behaviour to see if
it made any difference, but it didn't.

A few final points which may be of some relevance.

- The Kbox is a KFPS-3, with a 1.01 rev eprom.

- there is a sun on the ethernet with tops v2 installed, but even when
  it is not running the problem still occurs.

- the pyramid has tops v1 in its kernel.  The problem still occurs even
  though none of the tops related processes are running, though the
  ethernet interface had been ifconfig'ed with the "appletalk" option
  (I wasn't sure how to un-ifconfig it without shutting the machine
  down - which was not possible at that time).

Is the problem something simple, like "kip doesn't support tops"!  If
that is the case, what gateway code do we need to be able to run tops,
and still have nice features like dynamically assignable mac ip addresses
(and perhaps also support for CAP services)?

Thanks in advance for any advice that people can offer.  Email direct
to me unless you think your comments might be of interest to other folk.
I will summarise in a couple of weeks if appropriate.

Duncan.

Internet: duncan@comp.vuw.ac.nz		UUCP: ...!uunet!vuwcomp!duncan