IPROUTE V0.94 Status as of 31-Jul-1996 * This release provides support for Microsoft's TRACERT. * Beta 0.932 included a minor change to the packet driver interface code that allows shims and other unusual packet drivers to work again (apparently broken by beta 0.917). * Beta 0.93 provided support for incoming passive mode FTP and incoming data connections from an FTP server that originate on ports other than 20. These features are controlled by the "set nat ftp-pasv {off,on}", and "set nat ftp-data-any {off,on}" commands. Both of these features are off by default. * Beta 0.93 allowed static routes to be associated with script labels via the "route" command. Scripts can now be written that dial one of several phone numbers, etc, based on the destination IP address using the "on packet *" command. * Beta 0.93 supported CHAP authentication as a server. This is controlled by the "set ppp authenticate chap" command. * Beta release 0.925 fixed the "set nat send-reset on" command, and CHAP authentication as a client. In addition, NAT and filtering supported more protocols. * Beta release 0.917 fixed the "timeout and re-dial" problem that was introduced into PPP in V0.91. * Beta release 0.916 fixed several problems in the PPP code that could result in "random" memory modifications, calls to bad addresses, and corruption of packet queues. * Tested on various 386 & 486 machines. 286 tested with IPR286.EXE. Users report success on Pentium CPUs. Can boot off a floppy, but cannot run totally diskless. * Tested with SMC Elite series ethernet (8 & 16-bit) cards, SMC Elite Ultra, with 3COM 3C503 and 3C509B, and with some NE2000 clone cards. Works much better with Crynwr packet driver release 11 drivers than with earlier Crynwr packet drivers. Users report success with Crynwr Token Ring packet driver. * Tested with various 8250/16450/16550 async ports. Used with US Robotics Courier V.34 external modem, Telebit T3000, and US Robotics Sportster V.34 internal & external modems. Users report success with the Motorola BitSurfer products. * European users report success with the use of ISDN interfaces with Herbert Hanewinkel's ISPA (packet driver that looks like an ethernet and interfaces to the European standard ISDN API CAPI). * SLIP tested with KA9Q, DECserver 700/16 terminal server, SCO UNIX. * PPP tested with Ascend MAX, Cisco 2509, KA9Q, Microsoft Windows NT 3.50 RAS, Rockwell Nethopper, Telebit NetBlazer, Trumpet Winsock. * Ethernet operation tested with Cisco, KA9Q, SCO UNIX, NetBSD, Trumpet Winsock, FTP PC/TCP, MacTCP, TGV MultiNet, etc. CRASHES & HANGS * Some 286 motherboards crash when running IPRoute. I don't know why. INTERFACE ISSUES * Some serial port UART chips apparently lose transmitter interrupts infrequently. The async driver now detects these conditions and resumes transmission and counts a serial "stall". This seems to be due to a UART chip design problem. If you see many stalls on your async ports then you should try changing the serial card or modem to avoid the performance loss involved in stall recovery. * If the PPP peer terminates the LCP connection then PPP will exit without a script "on" condition being taken. This is a good reason never to end a script with a "ppp" command (put a goto after it). * The "exit" command doesn't always work on async interfaces. * SLIP should allow a command interpreter or script processor to receive the cd loss "packet" that made SLIP exit, but SLIP flushes it. PPP has the same problem. * The only link-level encapsulations supported are ethernet over a packet driver, SLIP (with or without header compression) and asynchronous PPP. Synchronous PPP and frame relay are (still) on my wish list. IP & ROUTING ISSUES * IP option processing is not compliant with appropriate RFCs. The existing behavior is allowed, but not as the default, according to RFC 1812. Specifically, all source routed packets are dropped, and timestamp and record route options are ignored. * All outgoing datagrams are now routed by scanning an ordered list of routes. This is easy and guarantees correct operation, but could be faster. A routing cache hashed by destination IP address will be implemented eventually. * RIP does not make or respond to requests. Triggered updates are not sent. Routes for directly connected networks are not poisoned correctly when lost. RIP version 2 code does not send or listen to multicasts. * OSPF is not supported. * The ICMP router discovery protocol is not supported. NAT ISSUES * NAT should allow incoming IDENT requests to be proxied for outbound connections back to the internal originating machine. * A nat entry for an ftp control connection could time out and be removed while its data connection is still active. This is not much of a problem in practice, because the timeout is 24 hours. * The network manager cannot control the address translation timeout parameters. MISCELLANEOUS * Several users have asked for command line editing, etc. * Some users have asked for a way to make the router beep during script execution. * The logging subsystem needs to be finished. There should be a way to view the in-memory log without losing it. Eventually tcp transport should be supported. * There is no proxy ARP support. * There is no support for BOOTP or RARP. * There is no way to reconfigure the router, or supply a new executable, over the network. * There is no SNMP support.