Traditionally the mechanism would be to use WPAD over DNS.

That would make a Windows computer resolve "wpad.XXX" for every domain
every DNS interface has, which means your VPN interface domain name
could respond - telling the browser about the local proxy/etc.
AD-integrated Windows computers would also look up
"wpad.their.ad.domain" too - which is another opportunity to respond
with WPAD details

Jason

On 21/12/15 10:44, Gert Doering wrote:
> Hi,
>
> On Sun, Dec 20, 2015 at 11:44:36AM -0800, Laurens Vets wrote:
>> Is it possible somehow to push proxy settings from the OpenVPN server 
>> to clients (Windows or Linux)? I wasn't immediately able to find 
>> anything that might explain it if it's supported...
> It is not, because it doesn't make sense - at least for the proxy settings
> for OpenVPN itself, because you need them before you can connect to the
> server to receive the info which proxy to use...
>
> As for clients using the VPN, that might be possible by passing 
> environment variables ("push setenv ...") and setting up something
> in an --up script.  But I'm not aware of any ready-made implementation.
>
> gert
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-users


-- 
Cheers

Jason Haar
Corporate Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 481 8171
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1

------------------------------------------------------------------------------
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to