beautypg.com

Creating dns whitelists – Brocade Mobility RFS Controller System Reference Guide (Supporting software release 5.5.0.0 and later) User Manual

Page 634

background image

622

Brocade Mobility RFS Controller System Reference Guide

53-1003099-01

11

FIGURE 5

Captive Portal Policy Externally Hosted Web Page screen

21. Select OK when completed to update the captive portal’s advanced configuration. Select Reset

to revert the screen back to its last saved configuration.

Creating DNS Whitelists

A DNS whitelist is used in conjunction with a captive portal to provide access services to wireless
clients. Use the whitelist to create a set of allowed destination IP addresses within the captive
portal. To effectively host hotspot pages on an external Web server, the IP address of the
destination Web server(s) should be in the whitelist.

To define the whitelist:

Login URL

Define the complete URL for the location of the Login screen. The Login screen prompts the user for a
username and password to access either the Terms and Conditions or Welcome page.

Agreement URL

Define the complete URL for the location of the Terms and Conditions page. The Terms and Conditions
page provides conditions that must be agreed to before wireless client access is provided.

Welcome URL

Define the complete URL for the location of the Welcome page. The Welcome page asserts the user has
logged in successfully and can access network resources via the captive portal.

Fail URL

Define the complete URL for the location of the Fail page. The Fail page asserts authentication attempt
has failed, and the client cannot access the captive portal.The client needs to provide correct login
information to regain access.

Acknowledgement
URL

Define the complete URL to the location of the Acknowledgement page. The Acknowledgement URL is
needed by returning users whose MAC addresses has been validated previously, but must accept the
conditions of the captive portal again.

No Service

Define the complete URL to the location of the No URL page. The No URL is needed by users encountering
difficulties connecting to the external resource used to host the captive portal pages.