Appendix A Motorola ® Gateway Captive Portal Implementation; Overview - Motorola nvg589 Administrator's Hanbook

Appendix A
This section contains information about the Motorola Gateway Captive Portal Support.

Overview

Motorola follows the 2Wire RPC specification for implementation of Captive Portal.
The Captive Portal feature redirects all TCP traffic destined to port 80 and redirects it to a Captive Por-
tal URL. A White-IP address list can be configured to avoid the captive portal redirect. All HTTP traffic
destined to the IP addresses within this white IP address list will not be redirected to the Captive Por-
tal. Any Changes to the Captive Portal parameters will take place immediately and do not require a
reboot.
PortalURL can be a maximum of 512 characters long.
■
A maximum of 500 White IP Addresses are supported WhiteIPAddresses list takes a comma-sepa-
■
rated string, which can be Individual IP addresses or a range of IP addresses. For a range of IP
Addresses, subnet mask is required.
The following formats of IP address are accepted:
■
• Individual IP address - 144.130.120.62 or 144.130.120.62/32
• Range of 64 IP addresses - 144.130.120.64/26
White IP Address list gets rewritten on any changes.
■
Clearing the Captive Portal URL disables Captive Portal. Turning OFF the enable parameter can
■
also disable captive Portal functionality.
Captive Portal is disabled by default and enabled via TR-069
■
White List can be a combination of FQDN (Fully Qualified Domain Names) and white IP Address/
■
cidr.
FQDNs will be resolved to IP addresses on BOOT and whenever a new list is pushed.
■
For NVG589, Captive Portal implementation only redirects port 80 traffic.Traffic to port 443 is
■
allowed.
DNS Traffic will not be blocked
■
®
Motorola Gateway Captive Portal
Implementation
203