Path: utzoo!mnetor!uunet!husc6!bbn!mit-eddie!rutgers!columbia!cunixc!cck
From: cck@cunixc.columbia.edu (Charlie C. Kim)
Newsgroups: comp.protocols.appletalk
Subject: Re: problems with CAP (look, looks, macdump, etc.)
Message-ID: <626@cunixc.columbia.edu>
Date: 26 Apr 88 14:29:35 GMT
References: <938@hsi.UUCP>
Reply-To: cck@cunixc.columbia.edu (Charlie C. Kim)
Organization: Columbia University
Lines: 35

In article <938@hsi.UUCP> wright@hsi.UUCP (Gary Wright) writes:
>I am having problems getting some of the CAP program to work on our system.
...
>
># mynet mynode myzone 
>02.00 2 COMPSERV
># bridgenet bridgenode bridgeIP
>02.00 220 1.0.0.8
>
...

The kip install documentation isn't clear:
	Just type in the appletalk net number for the UNIX's ether cable as the
	first number.  The second number will be the low byte of the host's IP
	address.  The third field is the local zone name.  On the second
	(noncomment) line we give the address for the 'closest' kbox.  The
	first and second numbers are the anet and node number.  The third
	number is the IP address of the kbox.  (This can be a IP host name as
should really read something like:
	Just type in the appletalk net number for the UNIX's ether
	cable as the first number.  The second number, the node
	number, will be the low byte of the host's IP address.  The
	third field is the local zone name.  On the second
	(noncomment) line we give the address for the 'closest' kbox.
	The first number should be the kbox's "anete" network number.
	The second number is its node number and since we are using
	the anete interface, it is the last byte of the IP address of
	the kbox. (The use of the "atneta" network number of the kbox
	is not recommended since the node number is not constant).
	The third number is the IP address of the kbox.  (This can be
	a IP host name as

Charlie C. Kim
User Services
Columbia University