______________________________________________________________________ news@ftp The FTP Software Quarterly Newsletter ______________________________________________________________________ Volume I, Number 2 July 1988 currently under study. So the Table of Contents Internet isn't really going away, it's just evolving into Item Page something more useful. Masthead 2 What's up with TCP/IP? New Product News 2, 3, 6 According to a recent Compatibility Issues 4 Infonetics survey of 150 large companies, there is strong user Technical Support 5 satisfaction with TCP/IP, even given the lack of network Questions and Answers 7 management facilities. Also, a few of the trade magazines have noted that even after the Enterprise Networking Continued TCP/IP and Internet Conference in Baltimore at the Growth beginning of June, LAN managers at corporations are still Every now and then rumors skeptical about OSI. The abound asking if TCP/IP consensus at the conference interest has died in favor of seemed to indicate that OSI is the OSI standards or some other still mostly hype, and that any protocol suite. We've heard a significant benefits from the few lately, but we've also OSI standardization process are heard quite a few people saying still many years away. that TCP/IP is alive and well. The technical and academic We've noticed that more and markets have always been strong more companies are planning harbors of TCP/IP support, but Wide Area Network (WAN) that support has also spread to installations. This seems to the corporate arena. be an outgrowth of several different situations. First, Rumors also abound about the corporations have discovered demise of the Internet. While the benefits of LAN technology, the Internet is still viable, and the benefits of WAN the ARPANET will be replaced in technology are further steps about five years with a non- along the same path. Second, experimental version which will word of large resource sharing be maintained by contractors networks, such as the DARPA who are paid by those agencies sponsored Internet, USENET, making use of the services. BITNET and others, has spread How this will be done is ______________________________________________________________________ 2 July 1988 news@ftp ______________________________________________________________________ pretty widely. Corporations want to tap into these resources (or similar resources), if possible. Third, the WAN technology has become stable enough to allow even major corporations to feel comfortable with it. The upshot of all of this is that TCP/IP is a reasonable networking solution which fills the immediate needs of the user community. TCP/IP can be used now, across links that span departments or countries. It can be used to communicate with any of the available networks, so it's simple to access resources and information. As such, support for TCP/IP is too widespread for it to become obsolete any time soon. What's up with the Internet? The Internet is growing at a surprising rate. Current estimates indicate that the Internet has grown to over 100,000 nodes, and more are being added constantly. With so many nodes involved, it is natural for organizations to express concern over the possibility that access to these newfound resources may be terminated. continued ______________________________________________________________________ 3 July 1988 news@ftp ______________________________________________________________________ Copyright 1988 by FTP news@ftp Software, Inc. Permission to use, copy, modify, and distribute this publication Volume I, Number 2 for any purpose and without July 1988 fee is hereby granted, provided that this copyright and permission notice appear Published quarterly by FTP on all copies, the name of Software, Inc. Editor: FTP Software, Inc. not be Nancy Connor. Communications used in advertising or pertaining to this newsletter publicity pertaining to should be directed to: distribution of the material without specific prior news@ftp permission, and notice be FTP Software, Inc. given that copying and P.O. Box 150 distribution is by permission Kendall Square Branch of FTP Software, Inc. Boston, MA 02142 (617) 868-4878 continued from page 1 Telex: 981970 Answerback: FTP SFTWRE The ARPANET was founded in UD the early 70's when 56Kbit per FAX: (617) 864-3943 second trunks were on the Electronic mail: cutting edge of modulation and news@ftp.com transmission technology, and packet switching was unheard FTP Software welcomes of. At that time, the average suggestions and contributions terminal of the day was 30 from readers. Submissions characters per second, which for the next issue of the means that the network trunks newsletter must be received were about 230 times faster no later than June 1, 1988. than the average user interface. Now it has become FTP Software and LANWatch an Internet, where a number of are trademarks of, and PC/TCP dissimilar networks are is a registered trademark of interconnected relatively FTP Software, Inc. Micro transparently. LANs and WANs Channel is a trademark of the have become larger and faster. International Business As a result, in 1973 a large Machines Corporation. number of users could effectively share one trunk, while today, one user on a PC can overload the entire capacity of the ARPANET. In addition to being overloaded, the ARPANET is no longer able to support its other prime function, that of a research base. When the ARPANET project began, it was ______________________________________________________________________ 4 July 1988 news@ftp ______________________________________________________________________ designed to be an experimental PC/TCP 2.03 network. Now, conducting any kind of experiment on the PC/TCP Version 2.03 will be ARPANET causes too much service released sometime in August. disruption to the community. It will contain several new features of interest, and it The researchers who began the will also have some impact on ARPANET project are planning to the development environment. phase out the ARPANET/Internet The planned features include: and replace it with two new networks. The follow on * PC/telnet and PC/rlogin network experiment will be will be able to open called the Defense Research multiple sessions, and Internet (DRI). will provide additional statistics via the escape Long distance trunk capacity character. The separate and initial speeds of 1.5Mbit terminal emulation per second per link are software will be merged currently planned. The DRI so that there is only one will also be segregated into PC/telnet program and one experimental and an operational PC/rlogin program. Our networks. The experimental 3270 Telnet emulation side will have higher will support 3278 Model 4 performance, with the (43 lines by 80 columns) possibility of higher degree of on an EGA. net problems, while the operational side will support * PC/smtpsrv will be able high data-rate applications to accept more than one such as image transfer and will message during a single take over for the connection, and both ARPANET/Internet. The PC/smtp and PC/smtpsrv experimental side will be will be able to use MX phased from 1.5Mbit to higher records. and higher bandwidths with the intent of eventually reaching * PC/ftpsrv will be able to gigabit per second performance. handle multiple simultaneous connections. Current plans are that the new DRI will be operated by a * PC/ping will provide more contractor, and will be funded statistics. as overhead on individual users' projects rather than In addition, much work is becoming a drain on the going into improving the Networking research budget. protocol implementations to After the DRI is stable, the handle additional options. ARPANET and Internet will be Improvements include: phased out, because they will no longer be necessary. * IP security and type of service options will be implemented. * TCP support for the ICMP Source Quench and ______________________________________________________________________ 5 July 1988 news@ftp ______________________________________________________________________ Destination Unreachable using compilers we don't options will be support, or languages implemented. other than C. People who currently use them, or * ICMP will handle a expect to need them, broader range of should let us know. messages. * We are considering the * ARP support for increased removal of the system cache sizes and timeouts calls which use the will be provided. PACKET structure, because they are difficult to Several features and system support in a number of calls in the development new environments. The environment are less useful calls that would be than we anticipated. We are removed are: considering the removal of pkt_alloc(), pkt_free(), these features in a later send(), sendto(), recv(), release, so people who are and recvfrom(). The depending on them should NET_AS_RCVFLUSH contact us to discuss the option/upcall would also issues. be removed. * Support for the obsolete We would also like feedback IEN-116 name server on the 4.2 BSD style socket protocol (nm_ien116()) is emulation that we provide. Do being considered for the developers out there like removal from Version 2.0 what we have provided? Have only. Customers who are you encountered any problems actively using it instead caused by the differences of host tables or domain between 4.2 and 4.3? name servers should let us know. We will need to know how important this LANWatch 1.2 support is and how long you expect to need it LANWatch 1.2 will be released before converting to the in July, and it will have domain system. several new features of note: * We are considering the * LANWatch 1.2 displays IP removal of support for layer host names instead the inverse look-up of addresses, when functions (ad_res_name(), desired. ad_htable(), and ad_domain()). If and * We have added support for when we removed them from the Banyan VINES, 802.5, the kernel, these BOOTP and DECNet functions would still protocols. reside in a C library, but this would mean that * In prior versions, you they would not be could only access the accessible to people first 254 packets of a ______________________________________________________________________ 6 July 1988 news@ftp ______________________________________________________________________ dump file; LANWatch 1.2 LANWatch and the ProNET-10 reads in new portions of the file on demand as you We have been notified of a scroll through the dump potential problem by Proteon. file. The ProNET-10 network interface from Proteon operates in one of * LANWatch 1.2 displays two modes: it can run in a each protocol layer in a mode which allows it to only different color. This listen to packets addressed to allows you to distinguish itself (normal mode), or it can different protocols at a run in a mode which allows it glance. to listen to all packets on the network (match-all mode). The * We have added support for p1300 interface card comes pre- two new drivers: the wired for normal mode. Since Proteon P1340 token ring LANWatch requires the board to interface, and the 3COM use match-all mode, if you 3c523 Micro Channel wanted to run LANWatch software interface. in a PC which has a p1300 or p1300/v interface, you would Unfortunately, due to memory have to modify the network card limitations, this version of so that it is constantly in LANWatch does not contain match-all mode, and this would support for the full complement void your warranty. of protocols. If you want to use LANWatch with protocols Proteon has made available that are not present, you will another version of the p1300 need to re-compile LANWatch to network interface, called the take out some protocols that P1301, which comes with a you don't use and add the switch on the end bracket of protocols that you want. The the card. This switch will next version of LANWatch will change the behavior of the be ported to medium memory board so that it will run in model, and will therefore either match-all mode or normal contain all of the protocols . mode on demand. We highly recommend buying one of these There are a few incompatible cards for any PC which will be changes that have been running LANWatch in a ProNET-10 introduced since the last site. version of LANWatch. LANWatch 1.1 had one filter for DECNet, The potential problem is that but since we've added support all P1800 Micro Channel network for the lower level DECNet cards and new p1300 cards protocols, we replaced the (revision F and higher) use a single DECNet filter with new chip which will not allow several individual filters. the card to go into match-all LANWatch 1.1 was compiled with mode at all. Therefore, those the 4.0 version of Microsoft C, users who want to run LANWatch but LANWatch 1.2 was compiled on a Micro Channel card will with the 5.1 version of not be able to do so. Microsoft C. ______________________________________________________________________ 7 July 1988 news@ftp ______________________________________________________________________ PC/TCP and Banyan VINES encapsulated over the VINES transport protocol rather than by Shelli Meyers simply sharing the network interface card to send Today, PC users have a Ethernet-encapsulated packets. variety of choices for network solutions in a LAN environment. This approach has several Proprietary PC LAN operating important advantages. First of systems provide high-speed, all, PC/TCP will be independent transparent access to shared not only of the specific resources, while TCP/IP-based hardware interface, but also of solutions offer communications the type of network implemented with a myriad of non-PC at the physical level. Thus, systems. However, the ideal PC/TCP users will have TCP/IP solution combines both of these access on any VINES-supported scenarios, allowing PC users to media, including networks use both the proprietary LAN previously inaccessible to program and TCP/IP software in TCP/IP users, such as ARCNET. conjunction with each other, And, with the TCP/IP Routing without the expense of having Option in the VINES server, the to add an additional network server performs IP routing off interface card. the local area network, providing TCP/IP access to non- In the April edition of VINES networks without having news@ftp, we discussed the to purchase an expensive IP joint development efforts by router. FTP Software and Banyan Systems, a leader in the PC LAN In addition to communications marketplace, which resulted in with the VINES server and such a product. The current beyond, users will also be able solution, available from FTP as to communicate with any other part numbers PC-115 or PC-215, VINES node on the network via allows PC/TCP to call the VINES PC/TCP. All traffic will be device driver and have it send directed through the VINES and receive Ethernet server, simplifying IP address encapsulated IP packets, thus configuration and access. sharing the network interface card. This new version of PC/TCP providing IP encapsulation over While this solution provides VINES will be available from the compatibility VINES users Banyan under a server-based need, it was believed by both license. For more information, FTP and Banyan that the contact your Banyan integration between PC/TCP and representative. VINES could become more symbiotic to increase functionality and performance to the end user. Later this summer, Banyan and FTP will release a new version of PC/TCP to run with VINES 3.0. In this version, IP packets generated by PC/TCP utilities will be ______________________________________________________________________ 8 July 1988 news@ftp ______________________________________________________________________ Developing PC/TCP Based passively opening and closing Applications network connections, setting asynchronous event handlers for by John Romkey a variety of asynchronous events, setting options for PC/TCP offers a rich and networks, and accessing the varied application development underlying services and environment. Three different statistics provided by the TSR. programming interfaces are The asynchronous event handlers available for developers of also aid in writing TSR modules network applications: PC/TCP which use the PC/TCP kernel. Version 1, PC/TCP Version 2 PC-502 also includes some native and PC/TCP Version 2 assembly source code to aid Sockets. The development programmers who want to use environment for PC/TCP Sockets languages other than Microsoft is included with the PC/TCP C. Version 2 native environment. The TSR system call mechanism is documented in the reference Version 1 guide, and it can be used from almost any programming Applications based on PC/TCP language. For instance, Gold Version 1 will require the Hill Computers markets an PC/TCP Programming Libraries interface to the PC/TCP 2.0 TSR (PC-501). They work only with that their 80286-protected mode Microsoft C Version 4.0, small Lisp calls. memory model. If you are not familiar with the tasking and upcall structure of M.I.T.'s PC/TCP Sockets PC/IP and are not trying to port a program from PC/IP to PC-502 also contains the PC/TCP, then you should socket compatibility library, probably use the PC/TCP Version which provides an emulation of 2 Development Kit instead of Berkeley UNIX Sockets as found the PC/TCP Version 1 in 4.2 BSD UNIX. These work Programming Libraries. with all memory models of Microsoft C. They're a great aid to anyone who is trying to Version 2 Native port code from a 4.2 BSD UNIX system to PC/TCP. The major PC/TCP Version 2.0 has a problems to watch when porting Terminate and Stay Resident such code are differences (TSR) kernel which contains the between the Microsoft C network hardware driver, ARP, development environment and the IP, ICMP, UDP, TCP and some BSD development environment miscellaneous services. The (for instance, differences in PC/TCP Development Kit (PC-502) basic C data types and in the contains a set of Microsoft C I/O libraries). The sockets libraries which allow any compatibility library is only memory model program to call available for PC/TCP Version 2. the TSR kernel. This provides a very rich set of primitive functions for actively and ______________________________________________________________________ 9 July 1988 news@ftp ______________________________________________________________________ New applications should be add-on peripherals and cards. written with PC-502, either the For instance, the disk native programming interface or controller, memory boards, I/O the sockets interface. If the cards and network interfaces application should be portable are all plugged into the bus. to, or is being ported from, a There must be a standard for UNIX system, the sockets how the bus is organized, or interface should be used. If what electrical signals are on the application requires any of which pins on the connectors, the unusual features provided and the timing of these signals by the native programming must be agreed upon. Otherwise interface (such as asynchronous even though two cards use the event notification and support same connectors they won't work for TSRs), then the Version 2 in the same slots because they native interface should be use the connections used. The PC/TCP Version 1 differently. Programming Libraries should currently only be used to port The oldest IBM personal an old application (perhaps computer bus is the PC bus. M.I.T. PC/IP-based) to PC/TCP. Those are the eight bit slots in IBM PCs, XTs and ATs (ATs Please note that PC/TCP also have sixteen bit slots versions 2.02 and earlier were which are a little different). built with Version 4.0 of the The eight bit slots can only Microsoft C compiler. However, move eight bits (one byte) of PC/TCP Version 2.03 will be data at a time across the bus, built with Version 5.1 of the and they allow the peripherals Microsoft C compiler. access to eight interrupt vectors and four DMA channels Documentation for PC-501 and (actually less, since some of PC-502 is available separately these are already permanently (part numbers PC-702 and PC- allocated). 704, respectively). One way that bus processing is often sped up is to increase The Micro Channel Bus the number of bytes of data moved, so the AT bus, by John Romkey introduced with the PC/AT, has sixteen bit slots, which carry When IBM introduced the PS/2 sixteen bits (two bytes) of series of computers more than a data across the bus. This year ago, they also introduced allows one bus cycle to move more confusion when the user is twice as much data on the AT trying to figure out which bus as it did on the PC bus. network interfaces work in what The AT bus also allows computers. IBM now supports peripherals access to sixteen three substantially different interrupt vectors and eight DMA buses for their line of channels (again, they really personal computers. can only use fewer than this since some are already The computer's bus is the allocated). The IBM PC/AT has electrical pathway by which the several sixteen bit slots as processor communicates with ______________________________________________________________________ 10 July 1988 news@ftp ______________________________________________________________________ well as two eight bit slots. the Micro Channel. Often, The eight bit slots are there since the card must be for use with old peripherals. redesigned, the programming One common compatibility interface to it will be problem is that many older different in order to take cards had printed circuit board advantage of features of the overhanging in the place where Micro Channel bus. This means the second connector for the that the software that uses the sixteen bit extension for the card will also have to be AT bus is, so they physically rewritten. couldn't plug into sixteen bit slots. For instance, most Micro Channel Ethernet cards are very The AT bus is really just an different from the PC bus cards extension of the PC bus; there their vendors had previously is an additional connector that built, so the software that carries some additional worked with the PC bus cards signals. The bus senses if the won't work with the Micro card is using this additional Channel cards and must be connector and does the proper rewritten. This means that transfer based on what it PC/TCP requires new drivers to senses. There are no support most Micro Channel fundamental differences between network interfaces. Network the two buses. interfaces that work like the IBM Token Ring card are an The PS/2 models 20, 25 and 30 exception; they come with a all have PC or AT buses in driver for the card which them; there are no major PC/TCP calls, so PC/TCP is changes. However, the PS/2 insulated from changes in the models 50 and up all have a new hardware and you always get the bus called the Micro Channel right version of this driver bus, which is a major departure since it comes with the board from the PC and AT buses. you buy. The Micro Channel bus is Some programs may also have designed to allow faster data to be revised to work correctly transfer than the original with the Micro Channel DMA and architecture of the AT bus interrupt controllers, even if would allow, and has different the network interface is very signals to allow better support similar to an older PC or AT of peripherals and multiple bus bus network interface that is masters. The Micro Channel already supported. also has a different connector, so it's not possible to confuse FTP Software is working on a Micro Channel card with a PC new versions of PC/TCP to or AT bus card. support Micro Channel-based computers. Some versions of Because the Micro Channel is PC/TCP currently work on Micro so different, it's necessary to Channel machines; some new re-engineer cards which were versions to support new network designed for the PC bus or the interfaces are under AT bus to get them to work on development. Please call and ______________________________________________________________________ 11 July 1988 news@ftp ______________________________________________________________________ ask for the list of currently Another example is the supported Micro Channel PC/supdup program. Supdup interfaces if you'd like up to support is provided with date information. Lisp machines, and is available on the 4.3 At publication, versions of supplemental software tape PC/TCP were available for Micro from Berkeley, but few Channel systems with the commercial implementations following network interfaces: currently support it. The IBM Token Ring (PC-119 and PC- source is available from 219), SLIP (PC-105 and PC-205), M.I.T. via FTP on the host 3COM 3C523 (PC-124 and PC-224), WHEATIES.AI.MIT.EDU. This Banyan VINES (PC-115 and PC- is a way to get support for 215), and the Generic Ethernet Supdup, but it is not or Packet Driver interface (PC- something that the average 110 and PC-210). We are user wants to do, since currently working on a version super-user privileges are of PC/TCP for the Proteon P1800 needed to install it, and (PC-101 and PC-201) interface. the code is provided support free. Questions and Answers Q. Where did the Ping server go in Version 2? by Stev Knowles A. A special Ping server is not To help you support your needed in Version 2. When users, here are some typical the PC/TCP kernel is loaded, questions asked by people it will always answer Ping upgrading from Version 1 to requests, and it will try to Version 2 of PC/TCP. accept TCP connections if there are any applications Q. Version 2 supports a running which listen on the selection of new programs, socket. The kernel will but what if my system also reset (shut down) any doesn't support them? application which tries to open connections to sockets A. Some of the programs will on which no server is still be useful, even though listening.. complete support is not available. For instance, Q. Why does my screen-blanking you can still extract files TSR always blank my Telnet from a Tar format file, even sessions after a few if the file resides on a minutes? remote host which doesn't support the RMT (Remote A. PC/telnet, PC/rlogin and Magnetic Tape) protocol. PC/supdup have new re- You simply use the PC/ftp mappable keyboards. This program to transfer the file allows for support of to your PC, then use the several keyboards, and PC/tar program to extract allows the user to customize the files. the keyboard for other languages or specially labeled keys. However, it ______________________________________________________________________ 12 July 1988 news@ftp ______________________________________________________________________ also steals the keyboard only) and PC/ipconfig interrupt from other program from either PC/TCP programs, which means that distribution can be used any TSR programs that listen with either version of the to the keyboard interrupt PC/TCP software. (most TSRs do this because it allows them to use "hot keys") will not work while you are using the re- mappable PC/telnet, PC/rlogin and PC/supdup programs. The keyboard interrupt will be returned to its original state when the program exits, so TSRs which use hot keys will work fine when you leave the program. Q. When I run the PC/ipconfig program, sometimes I get an error like this: C> ipconfig $ipcust ds 128.127.2.100 FTP Software PC/TCP ipconfig Version 2.02 pl 1 Copyright (c) 1986,1988 by FTP Software, Inc. PC/TCP resident module is not loaded; aborting program... What does it mean? A. First, you should note that the changes you made have taken effect. This message means that there was no kernel loaded when you ran the configuration program, and it is a warning that you cannot use the network until you load the kernel into memory. This message will be printed if you use the Version 2 configuration program with the Version 1 software. This is not harmful, since these programs do not use the network. The PC/mail, PC/tar (for local files ______________________________________________________________________ 13 July 1988 news@ftp ______________________________________________________________________ Q. Do I need to reconfigure the dev.sys and ipcust.sys files? A. If you are upgrading to Version 2 from a Version 1 distribution, you should be able to use the same dev.sys and ipcust.sys files. Of course, whenever you change interfaces you must also configure the new dev.sys file. If it ever becomes necessary to change these files, a note in the Release Notes that accompany that release will advise you to update your files, the version number in the files will be incremented, and the PC/ifconfig and PC/ipconfig programs will tell you that you are running an old version of the files. ______________________________________________________________________ Corporate headquarters: FTP Software, Inc. 501 Cambridge Street, Cambridge, MA 02141 (617) 868-4878 Correspondence: FTP Software, Inc. P.O. Box 150, Kendall Square Branch, Boston, MA 02142