Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!husc6!bunny!cayman!brad From: brad@cayman.COM (Brad Parker) Newsgroups: comp.protocols.appletalk Subject: Re: EtherTalk vs. AppleTalk vs. ??? Message-ID: <1367@cayman.COM> Date: 22 Aug 88 18:22:08 GMT References: <1364@cayman.COM> Organization: Cayman Systems Inc., Cambridge Ma Lines: 25 From article , by >morgan@JESSICA.STANFORD.EDU: > Ah, the heart of the matter. To allow a Ethernet-attached MacII (or > MacSE) to communicate directly to a CAP-speaking Unix host, there are > two ways to go. If the MacII has an AppleTalk driver that puts out > AppleTalk-in-UDP packets, then it can talk directly to an unaltered > CAP. As far as I know this doesn't yet exist. Anybody working on > one? > The CAP code will not directly support the multiple, "ad hoc" gateways this solution creates. It could be changed to work with mac's speaking UDP encapsulated AppleTalk, but won't out of the box. The KIP0688 code does allow Ethertalk machines to access CAP servers, using the "washing machine" effect. The packets go in as Ethertalk and pop back out (the same interface) as UDP encapsulated AppleTalk. This also works with the GatorBox. -brad -- "What will you do when you wake up one morning to find that God's made you blind in a beautiful person's world and all those great recepies have let you down, and you're twenty and a half and you're not getting age where you go look for the boys 'says I love you lets get married and have kids." -Billy Bragg.