If you set the login page in the captive portal profile on the controller to be the Amigopod page, at that point, the settings you state are all based on Amigopod settings. For example:
Amigopod is at IP 1.1.1.1 and you are using a web login page called guest-login.php.
Aruba Controller is using initial-role of guest-logon that uses a CP-Profile of amigopod-cp.
Then edit amigopod-cp profile on Aruba controller to use login page of "http://1.1.1.1/guest-logon.php"
- If you want a DNS name to show, put the DNS name for amigopod in the above instead of IP and make sure that this name resolves to amigopod from the DNS server that guests use.
I am assuming that other integration steps have been completed including:
On controller:
- Edit guest-logon role (or equivalent) to allow guest clients to open web pages on Amigopod
- Add Amigopod as radius server, add to server-group, and set as server-group in the CP profile used
- Optional: enable interim radius accounting in aaa profile
- Optional: add amigopod as XML server in aaa profile
On Amigopod:
- Add controller as NAS
Regards,
Austin