Open Transport

Revision as of 00:18, 21 September 2020 by Netfreak (talk | contribs) (→‎See Also)
Smopentransport.gif

Open Transport is the new communications and networking architecture that will become the standard for Macintosh networking and communications. Open Transport provides a mechanism for communications applications to operate independently from underlying networks such as AppleTalk, TCP, or IPX. Open Transport provides a code base and architecture that supports network stacks while eliminating many of the interrupt latency problems associated with AppleTalk.

Open Transport has two major aspects: the client interfaces and the environment for developing protocols and communications modules. The Open Transport client interfaces are a superset of the XTI interface from X/Open, a consortium of UNIX vendors. XTI is a superset of TLI, a UNIX standard interface. By using the Open Transport interfaces, applications (called clients) can operate independently of the transport layer.

Open Transport does not use the conventional .ENET-style drivers; instead it uses Streams-based DLPI drivers that are more appropriate for use with PCI devices. In addition to being consistent with industry standards, Streams-based DLPI drivers provide higher performance than .ENET-style drivers.

Apple Computer’s Open Transport software includes new stack implementations for AppleTalk and MacTCP. Apple expects that third parties will provide implementations of DECnet, IPX, and other network protocols.

The Open Transport implementation of TCP/IP is a replacement for MacTCP. It is designed for use under the Open Transport software interface.

New Features of Open Transport

The new features of Open Transport include

  • a new API
  • dynamic loading and shared code
  • an optional static node number (AppleTalk)
  • an optional NBP-to-catalog server (AppleTalk)
  • IP multicasting (MacTCP)
  • dynamic retransmission timers (MacTCP)

Compatibility

Open Transport is compatible with existing AppleTalk networks and supports existing .ENET clients such as Soft Windows and DECnet. On the PCI-based Power Macintosh computers, this .ENET compatibility is provided by a module that maps .ENET calls to the corresponding DLPI calls.

Open Transport provides compatibility with 680x0-based computers by means of the following features:

  • environment options
  • 680x0-based APIs and stacks
  • Open Transport APIs and stacks
  • API compatibility glue
  • use of parameter-block APIs with Open Transport stacks for 680x0-based applications

Open Transport provides compatibility with Power Macintosh computers by means of the following features:

  • environment options
  • 680x0-based APIs and stacks run in emulation mode
  • Open Transport APIs and stacks run in native mode
  • API compatibility glue runs in mixed mode
  • 680x0-based applications can use parameter-block APIs with Open Transport stacks
  • 680x0-based applications can use Open Transport APIs and stacks
  • native applications can use parameter block APIs with 680x0-based stacks
  • native applications can use parameter block APIs with Open Transport stacks

Troubleshooting

1.0.8 and Type 11 errors

To owners of PowerMac 7200, 7500, 8500, 9500 here is a solution to those
terrible type 11 errors experienced with OpenTranport 1.0.8*.

* Some may not have any problems, and thus should ignore this FAQ.  However
if you do switch providers be aware that some providers have a terrible
time supporting OpenTranport 1.0.8, and therefore in those cases use this
FAQ.

1. Get a Dynamic IP addressing account with all the gateway domain server
information from the provider, you may want to ask for a Compressed PPP
account with RARP addressing.
2. Clean install the system using the CD and Command-Sh-k at the startup of
opening the installer software.
3. Make sure you have OpenTransport 1.0.8 from ftp://ftp.support.apple.com,
install it and reboot.
4. Delete all non-Apple INITs, or archive them away in a .CPT, .SIT, or
.SEA file (clean install your system, and then install Open Transport
1.0.8).
5. Delete or archive the TCP/IP control panel and its corresponding
preference file in the System Folder::Preferences folder.
6. Delete or archive these extensions:
Open Tpt Internet Library
OpenTptInternetLib

7. Don't touch these extensions:
Open Tpt AppleTalk Library
Open Transport Library
OpenTptAppleTalkLib
OpenTransportLib.

8. Don't touch this Control Panel:
AppleTalk

9. Install MacPPP 2.0.1 or MacPPP 2.2.0a (available in the sumex mirror
archives).
Don't forget to set your TimeOut variable to at least 90 seconds,
and to setup your Connect Script.  If you have trouble setting up your
connect script, please e-mail me at my address below.  Also be sure no
other versions of PPP, PPP Preferences, Config PPP are on your machine when
you install it.
REBOOT your machine.

10. Install MacTCP 2.0.6.
Be sure to set it for Server addressing!  Yes, this appears to work on
dynamic addressing servers that claim to use RARP.  Strange but true of my
provider.
Gateway address and Domain Nameserver address is critical.  The IP address
is set by the server.
REBOOT your machine.

This configuration appears to work fine with the following:

~ATM 3.8.2 from System CD-ROM's Adobe Acrobat 2.1
Conflict Catcher 3.0
PPPop 1.3.2
Square One 3.0
Alps Glidepoint 1.1
Netscape 2.0b6 with no additional plugins installed*
Eudora 1.5.3
Fetch 3.0
Internet Config 1.2
IceTee 1.2b1
Virex 5.6.1
QuickTime 2.1
ClickThereItIs (installed with Ze at the beginning of the filename)
Directory Assistance II (installed with Ze at the beginning of the filename)
Aaron 1.1.3 (installed with ~ at the beginning of the filename.

Hayes Accura 14.4 k bps modem.
PowerMac 7200, 24 MB of RAM, Virtual Memory off.
Server at internet service provider is a SunOS 4.1 with AT&T Teledyn 28.8 k bps
modems.

* MacroMedia Shockwave 68k and Tumbleweed plugins both have caused Type 11
and or Unimplemented trap errors.

If anyone succeeds in eliminating Type 11 errors with the above
configuration with a newer version of OpenTransport, please let me know.
Server I might add has two name server addresses it recommends putting in
MacTCP, the first of which has its radio button checked.

Standard disclaimers apply.
Hope this helps.

Sincerely,
[email protected]

See Also