Cant add WFP filter being fatal

[hildeb]

A user on Vista updated to 2.3.10 and cannot connect anymore:

--- OpenVPN log attached to this ticket ---

Is "Can't add WFP filter" the cause for that fatal error?

How can I find out WHY it could not be added?

[ValdikSS]

Is "Can't add WFP filter" the cause for that fatal error?

Yes. Early versions of the patch threat it as non-fatal error but somebody wanted block-outside-dns to be a security feature and that's why it's fatal.

How can I find out WHY it could not be added?

I'm not really sure why too. I'll install Vista and check it out.

[ValdikSS]

Oh my, oh my. It seems that Windows Vista doesn't support non-equal matching of application name and it's available only on Windows 7 and higher. I missed that. I will fix this and it would probably go to OpenVPN 2.3.11.
Right now please don't push block-outside-dns from server or tell your client to use route-nopull and manual settings in his/her config.

[ValdikSS]

Hi,

Here are test installers based on latest Git code plus the Interactive service patch, which allows non-admin users to launch OpenVPN connections:

• ​http://build.openvpn.net/downloads/temp/openvpn-install-2.3_iservice-I601-i686.exe
• ​http://build.openvpn.net/downloads/temp/openvpn-install-2.3_iservice-I601-x86_64.exe

A second pair of installers contain a patch which makes the new --block-outside-dns work with Windows Vista:

• ​http://build.openvpn.net/downloads/temp/openvpn-install-2.3_blockoutsidedns-I601-i686.exe
• ​http://build.openvpn.net/downloads/temp/openvpn-install-2.3_blockoutsidedns-I601-x86_64.exe

If you test these, please let us know about your experience with them (worked/did not work/had issues).

Samuli Seppanen

[Samuli Seppänen]

Original description of ticket 648