Openvpn Connect Windows ignores "pull-filter"

[KiPe]

Judging from [1] and [2], the pull-filter should be implemented in OpenVPN Core library since ~2021, core library version 3.7.

Nevertheless, filtering is not working with the Windows OpenVPN Connect client (version 3.3.6).

So is the latest OpenVPN Connect (3.3.6) for Windows really still based on "OpenVPN 3 library to 3.6.2 version", as stated here [3] in 2021 ?

If so, can we expect an update incorporating a later OpenVPN 3 library (>3.7) at some point to support filtering?

I am raising this issue again as I have tracked down an issue with the Synology OpenVPN server to generate a configuration and push options to clients that lead to misbehaving clients in certain situations (bogous IPv6 routes being pushed and also DNS pushed). As for the Synology package, I have no control over the actual server configuration and need to filter on client side to make it work. OpenVPN2 client for windows is not an option as it exposes other types of problems.

Would be willing to help testing betas or nightlies also.


[1]
https://github.com/OpenVPN/openvpn3/issues/144

[2]
https://github.com/OpenVPN/openvpn3/blo ... ptfilt.hpp

[3]
https://openvpn.net/vpn-client/release-notes/

[KiPe]

Any chance to get some feedback?

[KiPe]

Update. As of release 3.4.0 (3121), the OpenVPN Library version used was bumped to 3.8.0.
So it should support the pull-filter now.

Will re-test and report.


[1]
https://openvpn.net/vpn-server-resource ... hange-log/