114
Specifying the local portal server for Layer 2 portal
authentication
L
ayer 2 portal authentication uses the local portal server. You need to specify the IP address of a Layer 3
interface on the device that is routable to the portal client as the listening IP address of the local portal
server. HP strongly recommends that you use the IP address of a loopback interface rather than a physical
Layer 3 interface, because:
The status of a loopback interface is stable. There will be no authentication page access failures
caused by interface failures.
A loopback interface does not forward received packets to any network, avoiding impact on system
performance when there are many network access requests.
Follow these steps to specify the local portal server for Layer 2 portal authentication:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Specify the listening IP address of
the local portal server for Layer 2
portal authentication
portal local-server ip
ip-address
Required
By default, no listening IP address
is specified.
NOTE:
The specified listening IP address can be changed or deleted only if Layer 2 portal authentication is not
enabled on any port.
Configuring the local portal server
Configuring a local portal server is required only for local portal authentication. During local portal
authentication, the local portal server pushes authentication pages to users. You can define the
authentication pages for users; otherwise, the default authentication pages will be used during the
authentication process.
Customizing authentication pages
Customized authentication pages exist in the form of HTML files. You can compress them and then save
them in the storage medium of the access device.
A set of authentication pages includes six main authentication pages and their page elements. The six
main authentication pages are the logon page, the logon success page, the logon failure page, the
online page, the system busy page, and the logoff success page. The page elements refer to the files that
the authentication pages reference, for example,
back.jpg
for page
Logon.htm
. Each main authentication
page can reference multiple page elements. If you define only some of the main authentication pages,
the system will use the default authentication pages for the undefined ones.
For the local portal server to operate normally and steadily, you need to follow the following rules when
customizing authentication pages:
Rules on file names
The main authentication pages have predefined file names, which cannot be changed. The following
table lists the names.