Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!njin!khnphwzhn.njin.net!rapatel From: rapatel@khnphwzhn.njin.net ( Rakesh Patel) Newsgroups: comp.protocols.appletalk Subject: Re: CAP.Etalk Message-ID: Date: 17 Aug 90 18:38:09 GMT References: Organization: Rutgers Univ., New Brunswick, N.J. Lines: 33 The ethertalk version of CAP uses UAB to "bridge" to Ethertalk, so a bridge description file needs to be set up and uab needs to be running before the Ethertalk version of CAP runs. The reason I set the distribution up to use /etc/etalk.local instead of /etc/atalk.local was so that it would be easy to test with and convert to the Ethertalk based CAP with the ability to easily go back to the IPtalk based mechanism if things failed. For your current problem, you need to create an empty /etc/etalk.local before running UAB, and provide the network and zone info in the bridge description file. When you run UAB, it will add the correct information into /etc/etalk.local for the Ethertalk based CAP library applications to run. You should make sure that the etalk.local actually contains the appropriate information after you start up uab. It should use the loopback interface for communicating with CAP applications. This distribution will be obsoleted soon. The version Charles Hedrick is working on to use the Berkeley enet packet driver instead of the NIT driver is being readied. This version will run either IPtalk or Ethertalk based upon the information format provided within /etc/atalk.local. I believe he has also made it so that it can use the NIT driver for those who need that capability. There will be a few more bug fixes added as well. I may add in the PC support for AUFS for the new release. If anyone has additional bug fixes that are not in the Rutgers distribution that they would like to see incorporated into the new version, they should send them to me soon. Rakesh Patel.