300
1.
When a user accesses the network for the first time, the access device generates a
MAC-trigger entry that records the user's MAC address and access interface. The user can
access the network without performing portal authentication if the user's network traffic is below
the free-traffic threshold.
2.
When the user's network traffic reaches the threshold, the access device sends a MAC binding
query to the MAC binding server.
3.
The MAC binding server checks whether the MAC address of the user is bound with a portal
user account.
{
If a matching MAC-account binding exists, the MAC binding server sends the user
authentication information to the access device to initiate portal authentication. The user is
authenticated without entering the username and password.
−
If the user fails portal authentication, an authentication failure message is returned to the
user. The MAC-trigger entry of the user on the access device is deleted when the entry
ages out.
−
If the user passes portal authentication, the access device deletes the MAC-trigger entry
of the user.
{
If no matching MAC-account binding exists, the MAC binding server notifies the access
device to perform normal portal authentication for the user.
−
If the user fails portal authentication, an authentication failure message is returned to the
user. The whole process is finished.
−
If the user passes portal authentication, the access device sends the user's MAC
address and authentication information to the MAC binding server for MAC-account
binding. Additionally, the access device deletes the MAC-trigger entry of the user.
NOTE:
For information about MAC binding server configuration, see the user manual of the server.
Restrictions: Hardware compatibility with portal
Portal is supported only on the CSPEX cards.
Restrictions and guidelines: Portal configuration
When you configure portal, follow these restrictions and guidelines:
•
Portal authentication through Web does not support security check for users. To implement
security check, the client must be the H3C iNode client.
•
Portal authentication supports NAT traversal whether it is initiated by a Web client or an H3C
iNode client. NAT traversal must be configured when the portal client is on a private network
and the portal server is on a public network.
Portal tasks at a glance
Tasks at a glance
Remarks
(Optional.)
Configuring a portal authentication server
Configuring a portal Web server
•
(Required.)
Configure basic parameters for a portal Web server
•
(Optional.)
Configuring a match rule for URL redirection
N/A
