[Openvpn-devel] [PATCH] Updated INSTALL-win32.txt

Signed-off-by: Samuli Seppänen --- INSTALL-win32.txt | 23 --- 1 files changed, 12 insertions(+), 11 deletions(-) diff --git a/INSTALL-win32.txt b/INSTALL-win32.txt index cc79d72..572309a 100644 --- a/INSTALL-win32.txt +++ b/INSTALL-win32.txt @@ -1,4

[Openvpn-devel] [PATCH] Replaced config-win32.h with win/config.h.in

The original config-win32.h - a static header file - has been superceded by both "domake-win" script and the new Python-based buildsystem. Transformed it into a template file, win/config.h.in, which obtains the most commonly used build parameters from win/settings.in. Added support code to

[Openvpn-devel] [PATCH] Fixes to win/openvpn.nsi

Added support for generating installer with unsigned TAP drivers. Fixed Windows Vista/7 Start menu shortcut uninstall failure. Signed-off-by: Samuli Seppänen --- win/openvpn.nsi | 19 +-- 1 files changed, 17 insertions(+), 2 deletions(-) diff --git

Re: [Openvpn-devel] [PATCH] Bind only to specified interface

Federico Heinz wrote: > * some other people agree that there is a use case, but propose > different ways of approaching the problem through various > mechanisms to resolve the interface name to an IP address before > passing it on to OpenVPN. The disagreement here seems to be in >

Re: [Openvpn-devel] [PATCH] Bind only to specified interface

On 14/03/2011, Gert Doering wrote: > > [...] Multiple openvpn daemons on different interfaces and > > same port. > That's one possible use case, but not how I understood Federico. That's part of my use case, not all. Please let me summarize what I've read in this discussion: * some people are