Various client behavior with DHCP/DNS provided autoproxy settings
05-17-2017 05:29 AM
I struggle with the forum to ask this question, but hope that the wireless/byod community will have the widest client base and therefore experience in this. Sorry if it seems a little off topic.
My enterprise is switching from WCCP directed proxy access to proxy access directed by an autoproxy config script. For corporate machines, we have that covered (somewhat) thru various push mechanisms. We have a fairly large user population of BYO devices that could include IOS, Android, Windows and MacOS. We put them on the corporate network and treat them differently based on an Aruba onboarding profile.
I want to find the best way to push these BYO devices to the autoproxy script. I know I can specify that in the Clearpass onboarding profile, but that's going to take a long time (and a lot of work) to get everyone re-onboarded.
I read that DHCP and DNS can provide autoproxy settings and am wondering if anyone has experience in trouble areas? I remember hearing that some versions of Android don't like this.
Re: Various client behavior with DHCP/DNS provided autoproxy settings
05-17-2017 06:54 AM
The real solution for a BYOD proxy server is a transparent proxy. If you send dhcp options for a proxy, a user's browser would need to be on "auto" for it to even consider using those options. Unfortunately leaving the browser on "auto" creates delays in a number of browsers if there is no actual proxy, so alot of people turn it off, which would break your proxy options that you send.
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars