Hey,
We are using packetfence as an external captive portal. We are doing MAC authentication and after that's all set we do a policy on the captive portal role the user has as follows:
1 user <external CP IP> svc-https permit
2 user any svc-http dst-nat 8080
3 user any svc-https dst-nat 8081
HTTP works correctly. Client gets on wireless. Get's an IP. Goes to a site like google.com and receives a 302 redirect form Aruba saying redirect to external CP and proceeds to packetfence.
IF a user tries to go to an HTTPS site though, and types in https://google.com, the user first receives the default securelogin.arubanetworks.com certificate error saying it can't be validated, then I accept the warning and get to my external CP.
Why is Aruba presentig a cert first and how do I get around this so users aren't seeing an aruba cert before getting to packetfence.
Hope all that makes sense - please let me know if I can provide any more info or if anyone has any ideas.... Working with Aruba support at the same time but not getting anywhere yet.
Thanks!