Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!dino!ceres!deimos.cis.ksu.edu!uxc.cso.uiuc.edu!csd4.milw.wisc.edu!bionet!ames!apple!voder!nsc!csi!varian!kinetics!minshall
From: minshall@kinetics.UUCP (Greg Minshall)
Newsgroups: comp.protocols.appletalk
Subject: Re: IPADDRESS vs IPGATEWAY
Message-ID: <787@kinetics.UUCP>
Date: 27 Jul 89 01:30:02 GMT
References: <928@wucs1.wustl.edu>
Organization: Kinetics, Inc., Walnut Creek, CA
Lines: 27

From article <928@wucs1.wustl.edu>, by kahn@wucs1.wustl.edu (Michael Kahn):
> We've recently switched from a K-3 box running KIP to a K-4 box
> running KSTAR
...
> Since making this change, atlook now views the K-4 box as an
> IPADDRESS, whereas previously atlook recognized the K-3 box as an
> IPGATEWAY (the "correct" answer).
> 
> Is this a bug?

Yes, it is a bug.  It is also a bug that KIP only answered IPADDRESS.
Both "should" answer everything they are - WHEN APPROPRIATE.  Bob Morgan,
in another follow-up to this message, indicated that neither KIP nor
K-STAR should reply in certain circumstances which have to do with
where the person doing the NBP lookup is sitting on the network (by the
way Bob, =:=@* *should* return an xxx:IPADDRESS@* answer from localtalk -
but that may be a second bug, sigh).

The reason that two K-boxes replying IPGATEWAY makes the various MacIP
programs die is that each K-box *also* replies to yyy:IPADDRESS@* queries
where "yyy" is NOT one of the IP addresses assigned to the individual K-box.
(This makes some MacIP programs work).

Hope this is useful.

Greg Minshall			Kinetics/Excelan/Novell
minshall@kinetics.com		1-415-947-0998