Xref: utzoo comp.protocols.tcp-ip:10587 comp.sys.mac.programmer:13230
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!hayes
From: hayes@Apple.COM (Jim Hayes)
Newsgroups: comp.protocols.tcp-ip,comp.sys.mac.programmer
Subject: Re: Mac TCP--Info??
Message-ID: <39520@apple.Apple.COM>
Date: 16 Mar 90 05:14:22 GMT
References: <39441@apple.Apple.COM> <RICH.90Mar15151409@sendai.sendai.ann-arbor.mi.us>
Followup-To: comp.sys.mac.programmer
Organization: Apple Computer Inc., ECO Networking Group
Lines: 52

This topic is being moved to comp.sys.mac.programmer.  My apologies
for wasting comp.protocols.tcp-ip bandwidth.

rich@sendai.ann-arbor.mi.us writes:
>Before you get your hopes up...
>
>In article <39441@apple.Apple.COM> hayes@Apple.COM (Jim Hayes) writes:
>
>   Functionally:
>
>	   It is co-resident with other drivers, including AppleTalk,
>	   so you can use AppleTalk AND MacTCP simultaneously.
>
>This isn't quite true.  Somehow there are collisions on a number of
>annoying things on my se30 with a dove ether board.  I don't know
>whose fault they are, (maybe mine), but when using net at all, (even
>over ether), you can't configure your printer port to do much of
>anything.  Also, you really have to reconfigure and reboot if you want
>to use a) macTCP things vs b) old style ncsaTelnet vs well, you get
>the idea.

1) Printer port problems:  Check with Dove.  My guess is that it's their
   driver doing it.  We havn't seen those problems.  The EtherTalk driver 
   allows attaching and detaching of protocol handlers (based on the "type"
   field in the packet) to the card so multiple protocols can be processed
   simultaneously.
2) NCSA Telnet 2.3 supports MacTCP.  Earlier versions of NCSA Telnet
   do not follow Apple's guidelines for accessing the EtherTalk driver and
   as such may interfere with MacTCP, AppleTalk, etc.

>   Technically:
>
>	   On LocalTalk (or Ethernet networks with no IP routing
>	   capabilities), MacTCP can encapsulate TCP/IP in AppleTalk
>	   packets for later decomposition at an AppleTalk/IP bridge
>	   on the destination network.  (I.e. Kinetics FastPath,
>	   Cayman GatorBox, etc.)
>
>But not vice verse.  ie, appletalk in ip, a la kip, so you would still
>need a gateway to do CAP.

1) It works both ways.  The Kinetics FastPath will RE-ENCAPSULATE IP back
   into AppleTalk so it may return to the source.  
2) CAP does not require "gateways" (what the author defines as a gateway)
   because it looks like an ordinary AppleTalk device.


-- 
Jim Hayes, TCP/IP Weenie
Advanced Technology Group, Apple Computer Inc.

Inet: hayes@apple.com		 UUCP: {amdcad|decwrl|ames}!apple!hayes