Presumably i'm looking for similar functionality as intel2k is here, allthough pushing it from the server wouldn't be necessary. Having the app acknowledging the proxy-setting in it's ovpn-file would suffice.
The changelog of the OpenVPN Connect app for iOS 1.0.3. shows:
So it looks as if it's already implemented in the iOS app from version 1.0.3 onwards.What's New in Version 1.0.3
...
* Added the capability for server to push proxy options, e.g.:
push "dhcp-option PROXY_HTTP 10.144.5.14 3128"
push "dhcp-option PROXY_HTTPS 10.144.5.14 3128"
push "dhcp-option PROXY_BYPASS http://www.openvpn.net http://www.openvpn.org"
push "dhcp-option PROXY_AUTO_CONFIG_URL http://www.openvpn.net/proxy.pac"
Note that this is a separate and distinct feature from the one to connect through an HTTP proxy. This feature allows proxy options to be set for Safari (and possibly other apps as well) for the duration of the VPN session.
These options can be placed directly in the profile, i.e.
--> dhcp-option PROXY_HTTP 10.144.5.14 3128
or pushed by the server:
--> push "dhcp-option PROXY_HTTP 10.144.5.14 3128"
I tested "dhcp-option PROXY_HTTP" with the OpenVPN Connect Android app (current version, 1.1.13 build 53) on KitKat 4.4.2. by adding it in it's ovpn-file, but to no success. The app completely ignores that setting, while the OpenVPN connection itself works flawlessly.
The logfile mentions:
Did i probably overlook something, or is that functionality not (yet) implemented in the Android app?Error setting dhcp-option for proxy:
tun_builder_dhcp_option_error:
tun_builder_set_proxy_http
I can imagine implementation with pushing from the serverside to be pretty complicated, but having the app at least recognizing a proxy-setting in its own configuration-file would help a lot.
Therefore the question whether this "dhcp-option PROXY_HTTP"-functionality will be implemented in the Android app as well?