Wireless Access

The welcome page on layer 3 authentication seems to behave very differently when using cpg, opposed to the native captive portal. Clearing the stations Web cache also seems significant in the operation of the welcome page. Does anyone have any specifics on how the welcome page on layer 3 authentication derives the original intended Web page target requested prior to captive portal authentication, after the stain had authenticated?

---

@soapdish wrote:
The welcome page on layer 3 authentication seems to behave very differently when using cpg, opposed to the native captive portal. Clearing the stations Web cache also seems significant in the operation of the welcome page. Does anyone have any specifics on how the welcome page on layer 3 authentication derives the original intended Web page target requested prior to captive portal authentication, after the stain had authenticated?

---

 

The original client requested page is pushed as an argument parameter when doing captive portal.  On the controller in the Captive Portal authentication profile you have a choice to have the client go to the original page after requesting, OR to hardcode an actual Welcome page you want the client to see after.  In CPG in the options for the guest page, you can also do this.

 

I have tried this with inconsistencies in behaviour. At the time I 'hard coded'it in as you suggested, more as a workaround of sorts. Do you know where the information for the argument is derived? I do not recall seeing it in the url used in the redirect, but if it is why does clearing the client web cache influence is behavior? I can't make sense of it.

The controller's captive portal authentication profile's welcome page parameter can override anything if an external page is set.  This is true if you are using the controller alone, OR cpg with the controller.

 

Leaving the captive portal authentication profile to the defaults will allow cpg to change the behavior.

 

Where does it get the argument parameter?

It is always sent when the client first opens the browser.  Take a look at the URL when the browser is first opened.