|
|
On Wed, 2 Mar 2005, Mathias Sundman wrote: > As OpenVPN 2.0 is closed for new features, I assume the > --explicit-exit-notify functionallity is not going to change before the > 2.0 release. > > Is the current implementation really that bad, or shouldn't it be > documented in the manpage? > > I've used it with success in all my installations since it was introduced > in beta11... I don't think the implementation is bad -- it's just experimental in the sense that the code will probably be ripped out at some point in the future and replaced with a general-purpose, bidirectional, ACK-based UDP disconnect notification. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-03/msg00052.html on line 193 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-03/msg00052.html on line 193 |