Introduction

      Captive portal provides user to configure their Wi-Fi SSID, credentials.On fresh boot-up and factory-reset, Captive Portal prompts to change the default ssid name and password for browsing a any url's on connected client's through Gateway network.

Captive Portal Working steps :

Step No : 1

                     On Fresh boot-up/Factor-Reset , User's associated with Emulator Gateway Network. Wi-Fi AccessPoint broadcasting in client Mobile.

Step No : 2

                            User's can browse any http url's  on connected clients, It will automatically redirects to Captive Portal Page as shown as below

Step No : 3 

                            Type GatewayIP:80(eg: 10.0.0.1:80) on connected clinet's browser, WebUI will automatically redirected to Captive Portal

Step No : 4

                          Enabling and Disabling the captive portal page on fresh boot-up / factory-reset

root@RaspberryPi-Gateway:~# dmcli eRT getv Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable
CR component name is: eRT.com.cisco.spvtg.ccsp.CR
subsystem_prefix eRT.
getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable
Execution succeed.
Parameter    1 name: Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable
              type:       bool,    value: false
 
root@RaspberryPi-Gateway:~# dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable bool false
CR component name is: eRT.com.cisco.spvtg.ccsp.CR
subsystem_prefix eRT.
setv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable
Execution succeed.

If this Parameter "Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable"  gets disabled, WebUI should be UP instead of captiveportal.

If this parameter "Device.DeviceInfo.X_RDKCENTRAL-COM_CaptivePortalEnable" gets enabled, Captive Portal should be UP instead of WebUI.