>> Also route-pull works in both OpenVPN 2.x and 3.x >> clients while pull-filter is currently 2.x only. > > Actually pull-filter cannot be compared with route-nopull as the > former is customizable. The real question is whether there is any > compelling reason to use it other than lack of alternatives in 2.3 and > older. I didn't know 3.x does not support pull-filter. Why? It's easy > to code (at least I know that for sure) so that can't be the reason.
The compelling reason for route-nopull is that it will catch all route related options even if OpenVPN adds a new one in a future version. It is a simple way of saying I don't want my routes to be modified. To emulate pull-filter with pull-filter you need to block this list: redirect-private redirect-gateway block-ipv6 client-nat route route-ipv6 route-gateway route-metric ip-win32 dhcp-option dhcp-renew register-dns tap-sleep block-outside-dns but not block route-gateway route-dealy And without looking at the source code you will be hard pressed to come up with the same list. Arne
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
