Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!ig!arizona!joel From: joel@arizona.edu (Joel M. Snyder) Newsgroups: comp.sys.att Subject: Re: ATT 3b2/400 and TCP/IP Message-ID: <9067@megaron.arizona.edu> Date: 7 Feb 89 05:00:04 GMT References: <513@wpi.WPI.EDU> Reply-To: jms@mis.arizona.edu (Joel M. Snyder) Organization: U of Arizona MIS Dept, Tucson Lines: 21 In a recent posting in this newsgroup, it was pointed out that Wollongong TCP/IP is being sold by AT&T for their 3B2s. This is true. However, any reader must be cautioned that this is the most miserable implementation of TCP/IP available. In particular, it tends not to communicate with Berkeley 4.3 systems (depending on how the kernel was genned, but exactly what's important, AT&T tech support has never been able to tell). There are other problems, mostly related to routing (which most people won't care about; using a 3B2 as an IP gateway isn't a typical application), and the support for "standard Berkeley Idiosyncracies" is not good (although, one must admit, not required for anything except interoperability). I have been told that there is a V2.2 release "in the offing" which resolves some of these bugs, but readers looking for IP on their 3B2 might be interested in talking to other vendors first. jms Disclaimer: I have no connection with any vendor of IP for 3B2s.