UPDATE# TCP/IP NETWORKING

See the networks sections in MSKERM.HLP (KERMIT.HLP) and MSKERM.BWR
(KERMIT.BWR) for additional information.  New networking features since
"Using MS-DOS Kermit", second edition, was published include:

 . Support for ODI, SLIP, and Novell SLIP_PPP drivers.

 . Up to six simultaneous TCP/IP sessions.  See below.

 . TCP/IP network connections thru Beame & Whiteside TCP/IP, via SET PORT
   BWTCP <ip-address>.	IP host names are not supported.

 . Ability to specify a particular packet-driver interrupt:

   SET TCP/IP PACKET-DRIVER-INTERRUPT { <number>, ODI }
     Normally Kermit searches from 0x60 to 0x7e for a packet driver.
     This command allows you to (a) specify a particular interrupt,
     in case you have more than one packet driver loaded, or (b) tell
     Kermit to skip the packet-driver interrupt search and use the ODI
     interface.	 Note: the ODI interface is used by default for TCP/IP
     connections if a packet driver cannot be found.

 . The ability to select a particular TCP port when making a connection:

   SET PORT TCP/IP <ip-name-or-address> [ <tcp-port-number> ]
     The default TCP port number is 23, which is the TELNET protocol socket.
     You can specify any other port number except 25.

 . New TCP/IP server mode accepts incoming TCP/IP connections:

   SET PORT TCP/IP * [ <tcp-port-number> ]
     If you specify asterisk (*) instead of an IP host name or address,
     MS-DOS Kermit waits for an incoming connection on the specified TCP
     port (23 by default).  This connection is useful only when MS-DOS Kermit
     is in SERVER mode or, for chatting, CONNECT mode.	It does not give
     clients a DOS command processor.

 . RFC 1395 BOOTP compliance allows MS-DOS Kermit to receive its fully
   qualified domain name from a BOOTP server.  Also, MS-DOS Kermit's SHOW
   COMMUNICATIONS command now displays the IP address of the BOOTP server
   from which its TCP/IP parameters were received.

 . New commands to govern TELNET protocol:

   SET TCP/IP TELNET-TERM-TYPE <text>
     Normally, MS-DOS Kermit sends its actual terminal-emulation type when
     the remote TELNET server asks for a terminal type report.	But the
     remote host computer might not support your current terminal type, or
     might know it by a different name.	 This command lets you specify a
     terminal-type name for Kermit to send instead of the default name.

   SET TCP/IP NEWLINE-MODE {OFF, ON}
     During terminal emulation on a TCP/IP connection, MS-DOS Kermit follows
     the TELNET specification and transmits carriage and line feed (CRLF)
     whenever you type carriage return (the Enter key).	 If the remote TELNET
     server is confused by this (i.e. it does not follow the TELNET
     specification), use SET TCP/IP NEWLINE-MODE OFF to make Kermit omit the
     line feed.

   SET TCP/IP DEBUG-OPTIONS { ON, OFF } 
     Whether to display TELNET options negotiation on the screen.  Default is
     OFF, don't display them.  When ON, you can view the negotiations on the
     screen, and you can capture them in screen dump or session log files, or
     print them, just like any other CONNECT-mode screen text.	DEBUG-OPTIONS
     is useful for debugging misbehaving TELNET sessions.  Refer to the
     TELNET RFCs, or a TCP/IP book, for an explanation of what they mean.

 . MS-DOS Kermit now replies to traceroute requests, handles ICMP redirects.

 . TELNET window (i.e. screen) size (NAWS) negotiation.


.