References: <41c0e750-b27e-22ea-d5fb-b17fe391636d@...1147...> <689096e2-8bb8-95b8-5daf-22fd600a00ca@...515...> From: Jan Just Keijser Message-ID: Date: Mon, 17 Jul 2017 14:01:49 +0200 MIME-Version: 1.0 In-Reply-To: <689096e2-8bb8-95b8-5daf-22fd600a00ca@...515...> Content-Language: en-US Subject: Re: [Openvpn-devel] Windows installer with updated pkcs11-helper (1.22) available for testing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable To: =?UTF-8?Q?Samuli_Sepp=c3=a4nen?= , "openvpn-devel@lists.sourceforge.net" Hi all, On 17/07/17 12:34, Samuli Sepp=C3=A4nen wrote: > On 15/07/2017 00:43, Jan Just Keijser wrote: >> Hi Samuli, >> >> On 14/07/17 16:07, Samuli Sepp=C3=A4nen wrote: >>> Hi all, >>> >>> Those of you who use pkcs11 on Windows: could you please test this new >>> Windows installer: >>> >>> >>> >>> >>> The previous installer(s) had pkcs11-helper 1.11. This one has 1.22, so >>> some regression testing would be good to have. >>> >>> I'd like to push the updated installer out early next week, preferably >>> on Monday. >>> >> nice to see that pkcs11 support is still included in the Windows >> version; I can test the installer on monday morning(no Windows laptop in >> my house ;)) I will let you know my findings. >> >> cheers, >> >> JJK >> > Hi JJK, > > Excellent, thanks! I will push out the new installer if everything looks > good at your end. > good news and bad news: + the pkcs11 stuff works as expected, no problems there - with openvpn 2.4.3 my existing setup using "redirect-gateway def1" stopp= ed working! I'll downgrade OpenVPN to see if this problem was already there in 2.3.XX ;= what happens is this: - openvpn wants to add a direct route to the VPN server - there happen to be TWO gateways to that server with the SAME IP address, = one via wired ethernet, one via wireless - openvpn gets confused and says "route gateway is ambiguous" and refuses t= o add it - after that, all traffic is jammed, as there is no direct route to the VPN= server itself, and thus all encrypted traffic is fed=20 back into the tunnel, where it is encrypted again, etc etc ("biting your ow= n tail"). Disconnecting either wired or wireless solves the issue AFTER restarting Op= enVPN. Annoying. It looks like a (minor) patch is needed to deal with this special case cheers, JJK