Patch/description attached; this resolves bug #320. On an unrelated note, I'm trying out OpenPGP/MIME (RFCs 4880 & 3156) in this submission since it appears the only non-broken way to sign patches. Sane clients should eat this fine (Outlook Express may not.) If this poses a particular problem for you or an archiving service (sf.net, gmane, etc) I'd like to know about it.
-- Josh Cepek
From 24be21ea2f1d02631685a0a11bf187372cf10fa4 Mon Sep 17 00:00:00 2001
From: Josh Cepek <josh.ce...@usa.net>
List-Post: openvpn-devel@lists.sourceforge.net
Date: Wed, 21 Aug 2013 16:20:30 -0500
Subject: [PATCH] Correct error text when no Windows TAP device is present
Starting with the 2.3-series, the TAP-Windows driver/utilities and
OpenVPN are separately installed components. The error message given to
users without available TAP devices uses the pre-2.3 path that does not
exist. The path should be listed under the TAP-Windows program group
that the tap-windows project installer uses.
Resolves bug #320
Signed-off-by: Josh Cepek <josh.ce...@usa.net>
---
src/openvpn/tun.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/openvpn/tun.c b/src/openvpn/tun.c
index f0ea2c4..86a43f2 100644
--- a/src/openvpn/tun.c
+++ b/src/openvpn/tun.c
@@ -3403,7 +3403,7 @@ static void
at_least_one_tap_win (const struct tap_reg *tap_reg)
{
if (!tap_reg)
- msg (M_FATAL, "There are no TAP-Windows adapters on this system. You should be able to create a TAP-Windows adapter by going to Start -> All Programs -> " PACKAGE_NAME " -> Add a new TAP-Windows virtual ethernet adapter.");
+ msg (M_FATAL, "There are no TAP-Windows adapters on this system. You should be able to create a TAP-Windows adapter by going to Start -> All Programs -> TAP-Windows -> Utilities -> Add a new TAP-Windows virtual ethernet adapter.");
}
/*
--
1.8.1.5
signature.asc
Description: OpenPGP digital signature
