Changes between Version 8 and Version 9 of OpenVPN2.4
- Timestamp:
- 01/06/14 13:45:35 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenVPN2.4
v8 v9 17 17 These tasks were originally from an [wiki:Topics-2013-04-18 IRC meeting agenda]: 18 18 19 * Android patchsets 20 * Dual stack client patches 21 * utun on mac os x 19 * ~~Android patchsets~~ **done** 20 * ~~Dual stack client patches~~ **done* 21 * Dual stack server and --inetd cleanup 22 * --preresolve patch 23 * ~~utun on mac os x~~ **done* 22 24 * native tun, no need for extra tun.kext 23 25 * Supported for all OS X >= 10.6.8 (latest PPC version) … … 25 27 * Real question: Drop tun.kext support and support only utun or "try utun first, fall back to tun.kext if it fails" 26 28 * svn 2.1 patchset (snappy support, push-peer-info changes, see trac#268-273) 27 * management interface changes (status 2/3)29 * ~~management interface changes (status 2/3)~~ **done* 28 30 * Formatting and whitespace fixes (just before 2.4 release) 29 * --version to include git commit id and branch?31 * ~~--version to include git commit id and branch?~~ **yes, done** 30 32 * OpenVPN-GUI installer from mattock 31 33 32 34 = Cleaning up IPv4/IPv6 split = 33 35 36 * what is this? 37 34 38 = Android/iPhone/Windows Phone 7 support = 39 40 * what is this? 41 42 = the grand compression cleanup = 43 44 * have the server select the "best" compression algorithm the client supports (lz4/snappy/lzo/none), based on pushed peer-info and server capabilities (can be done by a client-connect script, but "built-in" would be less error-prone) 45 * rework the whole "compress" and "comp-lzo " section of the openvpn.8 man page 46 * get rid of --enable-comp-stub - always include that, so a well-defined fallback exist (to be discussed) 47 48 = IPv6 payload / payload/routing integration = 49 * implement "redirect-gateway ipv6" in 2.x code base as well (3 has it) 50 * add --block-ipv6 51 * handle ipv6 payload over ipv6 transport, when the VPN server is inside the pushed IPv6 routes 52 * discover IPv6 default gateway 53 * install IPv6 route to VPN server via gateway 54 * cleanup afterwards 55 * handle iroute-ipv6 and pushed route-ipv6 consistently with IPv4: do not send pushed routes to the very client that the iroute-ipv6 points to (local route confusion at client), also trac#354.