🚀 go-pugleaf

In article <1993Jan26.093530.15705@fzi.de> bwild@fzi.de writes:
>>In article <1993Jan25.182909.24681@pslu1.psl.wisc.edu>  
hoymand@wissago.wisc.edu  
>>(Dirk Herr-Hoyman) writes:
>>> Could you explain how you have your Next and your AppleTalk network  
>>connected?   
>>> If Ethertalk is not supported, I am not clear as to how this is done.
>>> 
>>> Also, do you know if anyone is working to bring up Ethertalk?  
>>> 
>>
>>All Macs are grouped together to LocalTalk clusters, typically 5 to 10 Macs  
per  
>>cluster. In every cluster a Kinetics FastPath is running which is hooked  
>>directly to our Ethernet backbone. The FP serves 
>>*	as a bridge between different LocalTalk clusters, thus connecting them
>>	together logically (i.e. the user doesn't see the Ethernet part)
>>*	as a gateway for MacTCP packages. These are Internet packages wrapped
>>	in AppleTalk packages. The FP removes the wrapper and sends them to the
>>	Ethernet as plain Internet packages and vice versa.
>>*	as a bridge for EtherTalk packages as they can be send by
>>	Ethernet-equipped Macs. But, the other Ethernet hosts like Suns or
>>	NeXTs have to understand the EtherTalk protocol. Up to now NeXT has  
only
>>	built in the AppleTalk protocol. EtherTalk is supported on some 
>>	platforms by CAP but not on NeXT. 

I thought it was just the opposite...that NeXT only implemented the ethertalk  
client and not the appletalk client.

Someone who really knows please clarify!!!

--
Ronald Pomeroy		"The Internet is just a giant petri dish"
Advanced Micro Devices
CAM Applications Group
rpomeroy@aunext1.amd.com (NeXTmail preferred)