Wireless Access

last person joined: 16 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Configure Websense

This thread has been viewed 0 times
  • 1.  Configure Websense

    Posted Aug 16, 2012 10:17 AM

    We are trying to configure websense to filter all http and https traffic for the wireless. We created a policy and added dst-nat ip with ip and port of our proxy. For the services in the rules we added http and https. On a laptop filtering works for both http and https. Now when we connect an iphone/ipad device, only http works. We are not able to access any https site on the iphone/ipad.

     

    To test that it is not webseseb, we created another policy that allows all traffic. We connected the iphone to the wireless and manually added the proxy ip and port on the wireless configuration on the iphone. Both http and https filtering works without any issues.

     

    Has anyone successfully configure websense on an aruba620 so it works with iphones/ipads?



  • 2.  RE: Configure Websense

    Posted Nov 20, 2012 05:15 PM

    we're having the exact same issue.. Using DST NAT for both http and https..

     

    I actually had to permit DST NAT instead of using the same address and port as HTTP... if we didnt do this, all HTTPS traffic is blocked.

     

    Did you find a resolution?

     

    thanks.



  • 3.  RE: Configure Websense

    EMPLOYEE
    Posted Nov 20, 2012 05:22 PM

    DST-NAT does not work with https from a protocol perspective.

     

    DST-nat only works on http with a transparent proxy.

     



  • 4.  RE: Configure Websense

    Posted Nov 20, 2012 05:32 PM

    thanks for the quick reply  - Is there any other way to govern this?

     

    Certain users are allowed Quota Time to limit their web usage but adding an S to HTTP seems to be their way around it.

     

    Any other suggestions or ideas?



  • 5.  RE: Configure Websense

    EMPLOYEE
    Posted Nov 20, 2012 08:41 PM

    You might need to have a time-based ACL for those users.  DST-NAT the http, allow the https and just use time-based ACLs for both of them.