--- gvpe/NEWS 2005/03/26 03:16:23 1.52 +++ gvpe/NEWS 2006/01/18 13:15:07 1.68 @@ -1,9 +1,35 @@ -1.9 +TODO: enable bridging (compile-time option? ignore fragmentation?) + + - bugfix of callback.h, might have cause callback return values to + be corrupted on architectures like sparc before. + +2.0 Mon Dec 5 13:59:26 CET 2005 + - protocol version 0.1, compatible with older releases. + - implement allow-direct, deny-direct node config statements. + - implemented != for sockinfo. This fixes a bug where + gvpe sent packets to the old ip address of another host + even though it had received packets from it's new address. + This only causes problems if you forget to -HUP your gvpe after + your ip address changed, which is *required*. + - sets close-on-exec flag on tcp connections. This fixes a bug + where child processes kept tcp connections open and caused + connections to fail when only one side can connect. + - fixed a bug in receive sequence checking that made gvpe + accept out-of-window packets in most cases. + - tighter limit for the maximum sequence # to avoid overflow + conditions + allow more headroom for packet reordering. + - replace some asserts that trapped config mismatches by + more useful log messages. + - fix spurious extra newline in some log messages. + +1.9 Tue Apr 19 06:21:50 CEST 2005 + - protocol version 0.1, compatible with older releases. - WARNING: this version checks the return value of if-up etc. scripts and exits on failure. - IMPORTANT: run if-up/node-up etc. scripts via /bin/sh. - IMPORTANT: interface initialization (MAC, MTU) is now done automatically in most configurations. + - options can now be specified on the gvpe command line, too. - make some DNS transport values configurable and document them. - improved OS specific information in gvpe.osdep(5). - new tap device type "native/darwin", that supports the tap @@ -21,6 +47,7 @@ parsing and continuing with a certainly unusable config. 1.8 Fri Mar 18 00:58:55 CET 2005 + - protocol version 0.1, compatible with older releases. - enable-udp = yes is now default only when no other protocols are enabled. otherwise it is disabled unless explicitly enabled. - implemented dns tunneling (experimental now and in the future).