The Splash Page Sequence

As you will see mentioned in the “How openNDS (NDS) Works” section, an initial port 80 request is generated on a client device, either by the user manually browsing to an http web page, or, more usually, automatically by the client device’s built in Captive Portal Detection (CPD).

This request is intercepted by NDS and an html Splash Page Sequence is served to the user of the client device to enable them to authenticate and be granted Internet access.

Types of Splash Page

This Splash page can be one of the following:

A Dynamic Web Page served by the built in openNDS web server (PreAuth)

A script or executable file is called by openNDS. This script or executable will generate html code for the openNDS web server.

In openNDS this is called “PreAuth”, as openNDS itself serves the splash page as a PRElude to AUTHentication.

Simple coding in the script enables a dialogue with the client user, for dissemination of information, user response and authentication.

This is an implementation of Forward Authentication Services (FAS), without the resource utilisation of a separate web server, particularly useful for legacy devices with limited flash and RAM capacity.

A Dynamic Web Page served by an independent web server

This independent web server can be on the same device as openNDS, on the same Local Area Network as NDS, or on External Web Hosting Services.

A script or executable file is called by openNDS on the independent web server.

This has the advantage having the full flexibility of using readily available mainstream web servers, located anywhere, enabling full flexibility in design and implementation of the captive portal functionality, ranging from a self contained system through to a fully integrated multi site system with a common database.

The Pre-Installed ThemeSpec Splash Pages

By default, the Splash pages consist of a simple click to continue dialogue followed by a Welcome or advertising page. A simple config option allows you to select instead a Name/EmailAddress login dialogue.

In many instances, one or other of these simple methods will be all that is required, but the power of FAS, ThemeSpec and BinAuth can be used to create very sophisticated Captive Portal Systems.

The Legacy splash.html Static Web Page

The legacy static splash.html page has been deprecated for some time and in openNDS v9.0.0 support was removed.

A ThemeSpec script that emulates the legacy Static Web page has been provided in th Community area of Github.

It can be downloaded from here:

https://github.com/openNDS/openNDS/tree/master/community/themespec/theme_legacy

Displaying Remote Content

openNDS supports the download on demand of remote content

openNDS can display content from third party web hosting, on the client user login screen.

This is ideal for serving information, banner advertising etc. and is configured simply by adding a custom_image or custom_file configuration option.

Walled Garden support

Sophisticated remote content can be served, with access controlled by the openNDS Walled Garden. Simple configuration options can enable such things as a Paypal payment system or access to Facebook resources.

For details see the Walled Garden Section.