1Version 1.0: August 11, 1996 (cjm) 2 3Version 1.1: August 20, 1996 (cjm) 4 - Host accepts incoming connections for ports 0 to 1023. 5 6Version 1.2: September 7, 1996 (cjm) 7 - Fragment handling error in alias_db.c corrected. 8 9Version 1.3: September 15, 1996 (cjm) 10 - Generalized mechanism for handling incoming 11 connections (no more 0 to 1023 restriction). 12 13 - Increased ICMP support (will handle traceroute now). 14 15 - Improved TCP close connection logic. 16 17Version 1.4: September 16, 1996 (cjm) 18 19Version 1.5: September 17, 1996 (cjm) 20 - Corrected error in handling incoming UDP packets 21 with zero checksum. 22 23Version 1.6: September 18, 1996 24 - Simplified ICMP data storage. Will now handle 25 tracert from Win95 and NT as well as FreeBSD 26 traceroute, which uses UDP packets to non-existent 27 ports. 28 29Verstion 1.7: January 9, 1997 (cjm) 30 - Reduced malloc() activity for ICMP echo and 31 timestamp requests. 32 33 - Added handling for out-of-order IP fragments. 34 35 - Switched to differential checksum computation 36 for IP headers (TCP, UDP and ICMP checksums 37 were already differential). 38 39 - Accepts FTP data connections from other than 40 port 20. This allows one ftp connections 41 from two hosts which are both running packet 42 aliasing. 43 44Version 1.8: January 14, 1997 (cjm) 45 - Fixed data type error in function StartPoint() 46 in alias_db.c (this bug did not exist before v1.7) 47 48Version 1.9: February 1, 1997 (Eivind Eklund <[email protected]>) 49 - Added support for IRC DCC (ee) 50 51 - Changed the aliasing routines to use ANSI style 52 throughout (ee) 53 54 - Minor API changes for integration with other 55 programs than PPP (ee) 56 57 - Fixed minor security hole in alias_ftp.c for 58 other applications of the aliasing software. 59 Hole could _not_ manifest in ppp+pktAlias, but 60 could potentially manifest in other applications 61 of the aliasing. (ee) 62 63 - Connections initiated from packet aliasing 64 host machine will not have their port number 65 aliased unless it conflicts with an aliasing 66 port already being used. (There is an option 67 to disable this for debugging) (cjm) 68 69 - Sockets will be allocated in cases where 70 there might be port interference with the 71 host machine. This can be disabled in cases 72 where the ppp host will be acting purely as a 73 masquerading router and not generate any 74 traffic of its own. 75 (cjm) 76 77Version 2.0: March, 1997 (cjm) 78 - Aliasing links are cleared only when a host interface address 79 changes. 80 81 - PacketAliasPermanentLink() API added. 82 83 - Option for only aliasing private, unregistered 84 IP addresses added. 85 86 - Substantial rework to the aliasing lookup engine. 87 88Version 2.1: May, 1997 (cjm) 89 - Continuing rework to the aliasing lookup engine 90 to support multiple incoming addresses and static 91 NAT. PacketAliasRedirectPort() and 92 PacketAliasRedirectAddr() added to API. 93 94 - Now supports outgoing as well as incoming ICMP 95 error messges. 96 97Version 2.2: July, 1997 (cjm) 98 - Rationalized API function names to all begin with 99 "PacketAlias..." Old function names are retained 100 for backwards compatitibility. 101 102 - Packet aliasing engine will now free memory of 103 fragments which are never resolved after a timeout 104 period. Once a fragment is resolved, it becomes 105 the users responsibility to free the memory. 106