Portal authentication controls user access to networks. Portal authenticates a user by the username and password the user enters on a portal authentication page. Therefore, portal authentication is also known as Web authentication. When portal authentication is deployed on a network, an access device redirects unauthenticated users to the website provided by a portal Web server. The users can access the resources on the website without authentication. If the users want to access other network resources, they must pass authentication on the website.

Portal authentication is classified into the following types:

· Active authentication—Users visit the authentication website provided by the portal Web server and enter their username and password for authentication.

· Forced authentication—Users are redirected to the portal authentication website for authentication when they visit other websites.

Portal authentication flexibly imposes access control on the access layer and vital data entries. It has the following advantages:

· Allows users to perform authentication through webpages without installing client software.

· Provides ISPs with diversified management choices and extended functions. For example, the ISPs can place advertisements, provide community services, and publish information on the authentication page.

· Supports multiple authentication modes. For example, re-DHCP authentication implements a flexible address assignment scheme and saves public IP addresses. Cross-subnet authentication can authenticate users who reside in a different subnet than the access device.

The device supports Portal 1.0, Portal 2.0, and Portal 3.0.

Extended portal functions

By forcing patching and anti-virus policies, extended portal functions help hosts to defend against viruses. Portal supports the following extended functions:

· Security check—Detects after authentication whether or not a user host installs anti-virus software, virus definition file, unauthorized software, and operating system patches.

· Resource access restriction—Allows an authenticated user to access certain network resources such as the virus server and the patch server. Users can access more network resources after passing security check.

Security check must cooperate with the H3C IMC security policy server and the iNode client.

Portal system components

A typical portal system consists of these basic components: authentication client, access device, portal authentication server, portal Web server, AAA server, and security policy server.

Figure 1 Portal system components

Authentication client

An authentication client is a Web browser that runs HTTP/HTTPS or a user host that runs a portal client application. Security check for the user host is implemented through the interaction between the portal client and the security policy server.

Access device

An access device refers to a broadband access device such as a switch or a router. An access device has the following functions:

· Redirects all HTTP requests of unauthenticated users to the portal Web server.

· Interacts with the portal authentication server and the AAA server to complete authentication, authorization, and accounting.

· Allows users that pass portal authentication to access authorized network resources.

Portal authentication server

The portal authentication server receives authentication requests from authentication clients and interacts with the access device to authenticate users.

Portal Web server

The portal Web server pushes the Web authentication page to authentication clients and forwards user authentication information (username and password) to the portal authentication server. The access device also redirects HTTP requests from unauthenticated users to the portal Web server.

The portal Web server can be integrated with the portal authentication server or an independent server.

AAA server

The AAA server interacts with the access device to implement authentication, authorization, accounting for portal users. In a portal system, a RADIUS server can perform authentication, authorization, accounting for portal users, and an LDAP server can perform authentication for portal users.

Security policy server

The security policy server interacts with the portal client and the access device for security check and authorization for users.

Portal system using the local portal Web server

The access device supports the local portal Web server feature. Using this feature, the access device also acts as the portal Web server and the portal authentication server to perform local portal authentication on portal users. In this case, the portal system consists of only three components: authentication client, access device, and authentication/accounting server, as shown in Figure 2.

Figure 2 Portal system using the local portal Web server

The authentication client cannot be an H3C iNode client. Local portal authentication only supports authenticating Web clients.

No security policy server is needed because local portal authentication does not support extended portal functions.

The local portal Web server feature implements only some simple portal server functions. It only allows users to log in and log out through the Web interface. It cannot take the place of independent portal Web and authentication servers.

Client and local portal Web server interaction protocols

HTTP and HTTPS can be used for interaction between an authentication client and a local portal Web server. If HTTP is used, there are potential security problems because HTTP packets are transferred in plain text. If HTTPS is used, secure data transmission is ensured because HTTP packets are secured by SSL.

Portal page customization

To perform local portal authentication, you must customize a set of authentication pages that the device will push to users. You can customize multiple sets of authentication pages, compress each set of the pages to a .zip file, and upload the compressed files to the storage medium of the device.

For more information about authentication page customization, see "Customizing authentication pages." For more information about the default-logon-page command, see Security Command Reference.

Interaction between portal system components

The components of a portal system interact as follows:

1. An unauthenticated user initiates authentication by accessing an Internet website through a Web browser. When receiving the HTTP or HTTPS request, the access device redirects it to the Web authentication page provided by the portal Web server. The user can also visit the authentication website to log in. The user must log in through the H3C iNode client for extended portal functions.

2. The user enters the authentication information on the authentication page/dialog box and submits the information. The portal Web server forwards the information to the portal authentication server. Then the portal authentication server processes the information and forwards it to the access device.

3. The access device interacts with the AAA server to implement authentication, authorization, accounting for the user.

4. If the user passes the authentication and no security policies are imposed on the user, the access device allows the authenticated user to access networks.

If the user passes the authentication and security policies are imposed on the user, the portal client, the access device, and the security policy server interact to check the user host. If the user passes the security check, the security policy server authorizes the user to access resources based on the check result. Portal authentication through Web does not support security check for users. To implement security check, the client must be the H3C iNode client.

If the user fails the authentication, an authentication failure message is returned to the user. The whole authentication process is finished.

NOTE:

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 authentication modes

Portal authentication has three modes: direct authentication, re-DHCP authentication, and cross-subnet authentication. In direct authentication and re-DHCP authentication, no Layer 3 forwarding devices exist between the authentication client and the access device. In cross-subnet authentication, Layer 3 forwarding devices can exist between the authentication client and the access device.

Direct authentication

A user manually configures a public IP address or obtains a public IP address through DHCP. Before authentication, the user can access only the portal Web server and predefined authentication-free websites. After passing authentication, the user can access other network resources. The process of direct authentication is simpler than that of re-DHCP authentication.

Re-DHCP authentication

Before a user passes authentication, DHCP allocates an IP address (a private IP address) to the user. The user can access only the portal Web server and predefined authentication-free websites. After the user passes authentication, DHCP reallocates an IP address (a public IP address) to the user. The user then can access other network resources. No public IP address is allocated to users who fail authentication. Re-DHCP authentication saves public IP addresses. For example, an ISP can allocate public IP addresses to broadband users only when they access networks beyond the residential community network.

Only the H3C iNode client supports re-DHCP authentication. IPv6 portal authentication does not support the re-DHCP authentication mode.

Cross-subnet authentication

Cross-subnet authentication is similar to direct authentication, except it allows Layer 3 forwarding devices to exist between the authentication client and the access device.

In direct authentication, re-DHCP authentication, and cross-subnet authentication, a user's IP address uniquely identifies the user. After a user passes authentication, the access device generates an ACL for the user based on the user's IP address to control forwarding of the packets from the user. Because no Layer 3 forwarding device exists between authentication clients and the access device in direct authentication and re-DHCP authentication, the access device can learn the user MAC addresses. The access device can enhance its capability of controlling packet forwarding by using the learned MAC addresses.

Portal support for EAP

Compared with username and password based authentication, digital certificate-based authentication ensures higher security.

The Extensible Authentication Protocol (EAP) supports several digital certificate-based authentication methods, for example, EAP-TLS. Working together with EAP, portal authentication can implement digital certificate-based user authentication.

Figure 3 Portal support for EAP working flow diagram

As shown in Figure 3, the authentication client and the portal authentication server exchange EAP authentication packets. The portal authentication server and the access device exchange portal authentication packets that carry the EAP-Message attributes. The access device and the RADIUS server exchange RADIUS packets that carry the EAP-Message attributes. The RADIUS server that supports the EAP server function processes the EAP packets encapsulated in the EAP-Message attributes, and provides the EAP authentication result.

The access device does not process but only transports EAP-Message attributes between the portal authentication server and the RADIUS server. Therefore, the access device requires no additional configuration to support EAP authentication.

NOTE:

· To use portal authentication that supports EAP, the portal authentication server and client must be the H3C IMC portal server and the H3C iNode portal client.

· Local portal authentication does not support EAP authentication.

Portal authentication process

Direct authentication and cross-subnet authentication share the same authentication process. Re-DHCP authentication has a different process as it has two address allocation procedures.

Direct authentication/cross-subnet authentication process (with CHAP/PAP authentication)

Figure 4 Direct authentication/cross-subnet authentication process

The direct/cross-subnet authentication process is as follows:

1. A portal user access the Internet through HTTP, and the HTTP packet arrives at the access device.

¡ If the packet matches a portal free rule, the access device allows the packet to pass.

¡ If the packet does not match any portal-free rule, the access device redirects the packet to the portal Web server. The portal Web server pushes the Web authentication page to the user for him to enter his username and password.

2. The portal Web server submits the user authentication information to the portal authentication server.

3. The portal authentication server and the access device exchange CHAP messages. This step is skipped for PAP authentication. The portal authentication server decides the method (CHAP or PAP) to use.

4. The portal authentication server adds the username and password into an authentication request packet and sends it to the access device. Meanwhile, the portal authentication server starts a timer to wait for an authentication reply packet.

5. The access device and the RADIUS server exchange RADIUS packets.

6. The access device sends an authentication reply packet to the portal authentication server to notify authentication success or failure.

7. The portal authentication server sends an authentication success or failure packet to the client.

8. If the authentication is successful, the portal authentication server sends an authentication reply acknowledgment packet to the access device.

If the client is an iNode client, the authentication process includes step 9 and step 10 for extended portal functions. Otherwise the authentication process is complete.

9. The client and the security policy server exchange security check information. The security policy server detects whether or not the user host installs anti-virus software, virus definition files, unauthorized software, and operating system patches.

10. The security policy server authorizes the user to access certain network resources based on the check result. The access device saves the authorization information and uses it to control access of the user.

Re-DHCP authentication process (with CHAP/PAP authentication)

Figure 5 Re-DHCP authentication process

The re-DHCP authentication process is as follows:

Step 1 through step 7 are the same as those in the direct authentication/cross-subnet authentication process.

8. After receiving the authentication success packet, the client obtains a public IP address through DHCP. The client then notifies the portal authentication server that it has a public IP address.

9. The portal authentication server notifies the access device that the client has obtained a public IP address.

10. The access device detects the IP change of the client through DHCP and then notifies the portal authentication server that it has detected an IP change of the client IP.

11. After receiving the IP change notification packets sent by the client and the access device, the portal authentication server notifies the client of login success.

12. The portal authentication server sends an IP change acknowledgment packet to the access device.

Step 13 and step 14 are for extended portal functions.

13. The client and the security policy server exchanges security check information. The security policy server detects whether or not the user host installs anti-virus software, virus definition files, unauthorized software, and operating system patches.

14. The security policy server authorizes the user to access certain network resources based on the check result. The access device saves the authorization information and uses it to control access of the user.

Portal filtering rules

The access device uses portal filtering rules to control user traffic forwarding on a portal-enabled interface.

Based on the configuration and authentication status of portal users, the device generates the following categories of portal filtering rules:

· First category—The rule permits user packets that are destined for the portal Web server and packets that match the portal-free rules to pass through.

· Second category—For an authenticated user with no ACL authorized, the rule allows the user to access any destination network resources. For an authenticated user with an ACL authorized, the rule allows users to access resources permitted by the ACL. The device adds the rule when a user comes online and deletes the rule when the user goes offline.

· Third category—The rule redirects all HTTP requests from unauthenticated users to the portal Web server.

· Fourth category—For direct authentication and cross-subnet authentication, the rule forbids any user packets to pass through. For re-DHCP authentication, the device forbids user packets with private source addresses to pass.

After receiving a user packet, the device compares the packet against the filtering rules from the first category to the fourth category. Once the packet matches a rule, the matching process completes.

Restrictions and guidelines

To configure portal on a Layer 3 aggregate interface that has traffic processing slots specified, make sure each slot has one or more member ports for the aggregate interface. For more information about specifying traffic processing slots for a Layer 3 aggregate interface, see Layer 2—LAN Switching Configuration Guide.

Portal configuration task list

Tasks at a glance
(Optional.) Configuring a portal authentication server
(Required.) Configuring a portal Web server
(Required.) Enabling portal authentication
(Required.) Specifying a portal Web server
(Optional.) Controlling portal user access · Configuring a portal-free rule · Configuring an authentication source subnet · Configuring an authentication destination subnet · Setting the maximum number of portal users · Specifying a portal authentication domain · Specifying a preauthentication domain · Specifying a preauthentication IP address pool for portal users · Enabling strict-checking on portal authorization information · Enabling portal authentication only for DHCP users · Enabling outgoing packets filtering on a portal-enabled interface · Configure support of dual stack for portal authentication
(Optional.) Configuring portal detection features · Configuring online detection of portal users · Configuring portal authentication server detection · Configuring portal Web server detection · Configuring portal user synchronization
(Optional.) Configuring the portal fail-permit feature
(Optional.) Configuring the BAS-IP or BAS-IPv6 attribute
(Optional.) Specifying a format for the NAS-Port-Id attribute
(Optional.) Specifying the device ID
(Optional.) Enabling portal roaming
(Optional.) Logging out online portal users
(Optional.) Disabling traffic accounting for portal users
(Optional.) Configuring Web redirect On Etherchannel interfaces, both Web redirect and portal authentication can be enabled at the same time. On non-Etherchannel interfaces, Web redirect does not work when both Web redirect and portal authentication are enabled.
(Optional.) Applying a NAS-ID profile to an interface
(Optional.) Configuring the local portal Web server feature
(Optional.) Enabling ARP or ND entry conversion for portal clients
(Optional.) Configuring HTTPS redirect
(Optional.) Configuring portal safe-redirect
(Optional.) Configuring the captive-bypass feature
(Optional.) Excluding an attribute from portal protocol packets
(Optional.) Enabling portal logging
(Optional.) Configuring portal support for third-party authentication · Editing buttons and pages for third-party authentication · Configuring a third-party authentication server · Specifying an authentication domain for third-party authentication
(Optional.) Configuring portal temporary pass

Configuration prerequisites

The portal feature provides a solution for user identity authentication and security check. To complete user identity authentication, portal must cooperate with RADIUS.

The prerequisites for portal authentication configuration are as follows:

· The portal authentication server, portal Web server, and RADIUS server have been installed and configured correctly.

· To use the re-DHCP portal authentication mode, make sure the DHCP relay agent is enabled on the access device, and the DHCP server is installed and configured correctly.

· The portal client, access device, and servers can reach each other.

· To use the remote RADIUS server, configure usernames and passwords on the RADIUS server, and configure the RADIUS client on the access device. For information about RADIUS client configuration, see "Configuring AAA."

· To implement extended portal functions, install and configure CAMS EAD or IMC EAD. Make sure the ACLs configured on the access device correspond to the isolation ACL and the security ACL on the security policy server. For information about security policy server configuration on the access device, see "Configuring AAA." For installation and configuration about the security policy server, see CAMS EAD Security Policy Component User Manual or IMC EAD Security Policy Help.

Configuring a portal authentication server

Configure this feature when user authentication uses an external portal authentication server.

Perform this task to configure the following portal authentication server parameters:

· IP address of the portal authentication server.

· VPN instance of the portal authentication server.

· Shared encryption key used between the device and the portal authentication server.

· Destination UDP port number used by the device to send unsolicited portal packets to the portal authentication server.

· Portal authentication server type, which must be the same as the server type the device actually uses.

The device supports multiple portal authentication servers.

Do not delete a portal authentication server in use. Otherwise, users authenticated by that server cannot log out normally.

To configure a portal authentication server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a portal authentication server, and enter its view.	portal server server-name	By default, no portal authentication servers exist.
3. Specify the IP address of the portal authentication server.	· To specify an IPv4 portal server: ip ipv4-address [ vpn-instance vpn-instance-name] [ key { cipher \| simple } string ] · To specify an IPv6 portal server: ipv6 ipv6-address [ vpn-instance vpn-instance-name] [ key { cipher \| simple } string ]	Specify an IPv4 portal authentication server, an IPv6 authentication portal server, or both. By default, no portal authentication server is specified.
4. (Optional.) Set the destination UDP port number used by the device to send unsolicited portal packets to the portal authentication server.	port port-number	By default, the UDP port number is 50100. This port number must be the same as the listening port number specified on the portal authentication server.
5. (Optional.) Specify the portal authentication server type.	server-type { cmcc \| imc }	By default, the portal authentication server type is IMC.
6. Return to system view.	quit	N/A
7. (Optional.) Set the maximum number of times and the interval for retransmitting a logout notification packet.	logout-notify retry retries interval interval	By default, the device does not retransmit a logout notification packet.
8. (Optional.) Configure the device to periodically send register packets to the portal authentication server.	server-register [ interval interval ]	By default, the device does not send register packets to the portal authentication server.

Configuring a portal Web server

The device supports multiple portal Web servers.

Perform this task to configure the following portal Web server parameters:

· VPN instance of the portal Web server.

· URL of the portal Web server.

· Parameters carried in the URL when the device redirects the URL to users.

· Portal Web server type, which must be the same as the server type the device actually uses.

· URL redirection match rule.

A URL redirection match rule matches HTTP or HTTPS requests by user-requested URL or User-Agent information, and redirects the matching HTTP or HTTPS requests to the specified redirection URL.

For a user to successfully access a redirection URL, configure a portal-free rule to allow HTTP or HTTPS requests destined for the redirection URL to pass. For information about configuring portal-free rules, see the portal free-rule command.

The url command redirects all HTTP or HTTPS requests from unauthenticated users to the portal Web server for authentication. The if-match command allows for flexible URL redirection by redirecting specific HTTP or HTTPS requests to specific redirection URLs. If both commands are configured for a portal Web server, the if-match command takes priority to perform URL redirection.

The device does not detect the reachability of the redirection URL configured by the if-match command. If the if-match command rather than the url command is configured to redirect HTTP requests to portal Web servers, the device does not trigger the following features:

¡ The fail-permit feature for the portal Web servers.

¡ The switch between primary and backup portal Web servers.

To configure a portal Web server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a portal Web server and enter its view.	portal web-server server-name	By default, no portal Web servers exist.
3. Specify the VPN instance to which the portal Web server belongs.	vpn-instance vpn-instance-name	By default, the portal Web server belongs to the public network.
4. Specify the URL of the portal Web server.	url url-string	By default, no URL is specified.
5. Configure the parameters to be carried in the URL when the device redirects it to users.	url-parameter param-name { nas-id \| nas-port-id \| original-url \| source-address \| source-mac [ format section { 1 \| 3 \| 6 } { lowercase \| uppercase } ] [ encryption { aes \| des } key { cipher \| simple } string ] \| value expression \| vlan }	By default, no redirection URL parameters are configured.
6. (Optional.) Specify the portal Web server type.	server-type { cmcc \| imc \| oauth }	By default, the portal Web server type is IMC.
7. (Optional.) Configure a match rule for URL redirection.	if-match { original-url url-string redirect-url url-string [ url-param-encryption { aes \| des } key { cipher \| simple } string ] \| user-agent string redirect-url url-string }	By default, no URL redirection match rules exist.
8. (Optional.) Enable local portal user password modification.	user-password modify enable	By default, local portal user password modification is disabled.

Enabling portal authentication

You must first enable portal authentication on an access interface before it can perform portal authentication for connected clients.

With portal authentication enabled, the device searches for a portal authentication server for a received portal packet according to the source IP address and VPN information of the packet.

· If the packet matches a locally configured portal authentication server, the device regards the packet valid and sends an authentication response packet to the portal authentication server. After a user logs in to the device, the user interacts with the portal authentication server as needed.

· If the packet does not match a portal authentication server, the device drops the packet.

Configuration restrictions and guidelines

When you enable portal authentication on an interface, follow these restrictions and guidelines:

· Make sure the interface has a valid IP address before you enable re-DHCP portal authentication on the interface.

· Do not add the Ethernet interface enabled with portal authentication to an aggregation group. Otherwise, portal authentication does not take effect.

· Cross-subnet authentication mode (layer3) does not require Layer 3 forwarding devices between the access device and the portal authentication clients. However, if a Layer 3 forwarding device exists between the authentication client and the access device, you must use the cross-subnet portal authentication mode.

· With re-DHCP portal authentication, configure authorized ARP on the interface as a best practice to make sure only valid users can access the network. With authorized ARP configured on the interface, the interface learns ARP entries only from the users who have obtained a public address from DHCP.

· For successful re-DHCP portal authentication, make sure the BAS-IP/BAS-IPv6 attribute value is the same as the device IP or IPv6 address specified on the portal authentication server. To configure the BAS-IP/BAS-IPv6 attribute, use the portal { bas-ip | bas-ipv6 } command.

· An IPv6 portal server does not support re-DHCP portal authentication.

· You can enable both IPv4 portal authentication and IPv6 portal authentication on an interface.

Configuration procedure

To enable portal authentication on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	The interface must be a Layer 3 interface.
3. Enable portal authentication on the interface.	· To enable IPv4 portal authentication: portal enable method { direct \| layer3 \| redhcp } · To enable IPv6 portal authentication: portal ipv6 enable method { direct \| layer3 }	Enable IPv4 portal authentication, IPv6 portal authentication, or both on an interface. By default, portal authentication is disabled on an interface.

Specifying a portal Web server

With a portal Web server specified on an interface, the device redirects the HTTP or HTTPS requests of portal users on the interface to the portal Web server.

IPv4 and IPv6 portal authentication can both be enabled on an interface. You can specify both a primary portal Web server and a backup portal Web server after enabling each type (IPv4 or IPv6) of portal authentication.

The device first uses the primary portal Web server for portal authentication. When the primary portal Web server is unreachable but the backup portal Web server is reachable, the device uses the backup portal Web server. When the primary portal Web server becomes reachable, the device switches back to the primary portal Web server for portal authentication.

To automatically switch between the primary portal Web server and the backup portal Web server, configure portal Web server detection on both servers.

You can specify both IPv4 and IPv6 portal Web servers on an interface.

To specify a portal Web server on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	The interface must be a Layer 3 interface.
3. Specify a portal Web server on the interface.	· To specify an IPv4 portal Web server: portal apply web-server server-name [ secondary ] · To specify an IPv6 portal Web server: portal ipv6 apply web-server server-name [ secondary ]	Specify an IPv4 portal Web server, an IPv6 portal Web server, or both on an interface. By default, no portal Web servers are specified on an interface.

Controlling portal user access

Configuring a portal-free rule

A portal-free rule allows specified users to access specified external websites without portal authentication.

The matching items for a portal-free rule include the host name, source/destination IP address, TCP/UDP port number, source MAC address, access interface, and VLAN. Packets matching a portal-free rule will not trigger portal authentication, so users sending the packets can directly access the specified external websites.

You cannot configure two or more portal-free rules with the same filtering criteria. Otherwise, the system prompts that the rule already exists.

Regardless of whether portal authentication is enabled or not, you can only add or remove a portal-free rule. You cannot modify it.

To configure an IP-based portal-free rule:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure an IPv4-based portal-free rule.	portal free-rule rule-number { destination ip { ip-address { mask-length \| mask } \| any } [ tcp tcp-port-number \| udp udp-port-number ] \| source ip { ip-address { mask-length \| mask } \| any } [ tcp tcp-port-number \| udp udp-port-number ] } * [ interface interface-type interface-number ]	By default, no IPv4-based portal-free rule exists.
3. Configure an IPv6-based portal-free rule.	portal free-rule rule-number { destination ipv6 { ipv6-address prefix-length \| any } [ tcp tcp-port-number \| udp udp-port-number ] \| source ipv6 { ipv6-address prefix-length \| any } [ tcp tcp-port-number \| udp udp-port-number ] } * [ interface interface-type interface-number ]	By default, no IPv6-based portal-free rule exists..

To configure a source-based portal-free rule:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a source-based portal-free rule.	portal free-rule rule-number source { interface interface-type interface-number \| mac mac-address \| object-group object-group-name \| vlan vlan-id } * }	By default, no source-based portal-free rule exists. If you specify both a VLAN and an interface, the interface must belong to the VLAN. Otherwise, the portal-free rule does not take effect.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Configure a source-based portal-free rule.

portal free-rule rule-number source { interface interface-type interface-number | mac mac-address | object-group object-group-name | vlan vlan-id } * }

By default, no source-based portal-free rule exists.

If you specify both a VLAN and an interface, the interface must belong to the VLAN. Otherwise, the portal-free rule does not take effect.

To configure a destination-based portal-free rule:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a destination-based portal-free rule.	portal free-rule rule-number destination host-name	By default, no destination-based portal-free rule exists.

To configure a description for a portal-free rule:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a description for a portal-free rule.	portal free-rule rule-number description text	By default, no description is configured for a portal-free rule.

Configuring an authentication source subnet

By configuring authentication source subnets, you specify that only HTTP packets from users on the authentication source subnets can trigger portal authentication. If an unauthenticated user is not on any authentication source subnet, the access device discards all the user's HTTP packets that do not match any portal-free rule.

When you configure a portal authentication source subnet, follow these restrictions and guidelines:

· Authentication source subnets apply only to cross-subnet portal authentication.

· In direct or re-DHCP portal authentication mode, a portal user and its access interface (portal-enabled) are on the same subnet. It is not necessary to specify the subnet as the authentication source subnet. If the specified authentication source subnet is different from the access subnet of the users, the users will fail the portal authentication.

¡ In direct mode, the access device regards the authentication source subnet as any source IP address.

¡ In re-DHCP mode, the access device regards the authentication source subnet on an interface as the subnet to which the private IP address of the interface belongs.

· If both authentication source subnets and destination subnets are configured on an interface, only the authentication destination subnets take effect.

· You can configure multiple authentication source subnets. If the source subnets overlap, the subnet with the largest address scope (with the smallest mask or prefix) takes effect.

To configure an IPv4 portal authentication source subnet:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure an IPv4 portal authentication source subnet.	portal layer3 source ipv4-network-address { mask-length \| mask }	By default, no IPv4 portal authentication source subnet is configured, and users from any subnets must pass portal authentication.

To configure an IPv6 portal authentication source subnet:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure an IPv6 portal authentication source subnet.	portal ipv6 layer3 source ipv6-network-address prefix-length	By default, no IPv6 portal authentication source subnet is configured, and IPv6 users from any subnets must pass portal authentication.

Configuring an authentication destination subnet

By configuring authentication destination subnets, you specify that users trigger portal authentication only when they accessing the specified subnets (excluding the destination IP addresses and subnets specified in portal-free rules). Users can access other subnets without portal authentication.

If both authentication source subnets and destination subnets are configured on an interface, only the authentication destination subnets take effect.

You can configure multiple authentication destination subnets. If the destination subnets overlap, the subnet with the largest address scope (with the smallest mask or prefix) takes effect.

To configure an IPv4 portal authentication destination subnet:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure an IPv4 portal authentication destination subnet.	portal free-all except destination ipv4-network-address { mask-length \| mask }	By default, no IPv4 portal authentication destination subnet is configured, and users accessing any subnets must pass portal authentication.

To configure an IPv6 portal authentication destination subnet:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure an IPv6 portal authentication destination subnet.	portal ipv6 free-all except destination ipv6-network-address prefix-length	By default, no IPv6 portal authentication destination subnet is configured, and users accessing any subnets must pass portal authentication.

Setting the maximum number of portal users

Perform this task to control the total number of portal users in the system, and the maximum number of IPv4 or IPv6 portal users on an interface.

If you set the maximum total number smaller than the number of current online portal users on the device, this configuration still takes effect. The online users are not affected but the system forbids new portal users to log in.

If you set the maximum number smaller than the current number of portal users on an interface, this configuration still takes effect. The online users are not affected but the system forbids new portal users to log in from the interface.

Make sure the maximum combined number of IPv4 and IPv6 portal users specified on all interfaces does not exceed the system-allowed maximum number. Otherwise, the exceeding number of portal users will not be able to log in to the device.

To set the maximum number of total portal users allowed in the system:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the maximum number of total portal users.	portal max-user max-number	By default, no limit is set on the number of portal users in the system.

To set the maximum number of portal users on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Set the maximum number of portal users on the interface.	portal { ipv4-max-user \| ipv6-max-user } max-number	By default, no limit is set on the number of portal users on an interface.

Specifying a portal authentication domain

An authentication domain defines a set of authentication, authorization, and accounting policies. Each portal user belongs to an authentication domain and is authenticated, authorized, and accounted in the domain.

With an authentication domain specified on an interface, the device uses the authentication domain for AAA of portal users. This allows for flexible portal access control.

The device selects the authentication domain for a portal user in this order:

1. ISP domain specified for the interface.

2. ISP domain carried in the username.

3. System default ISP domain. For information about the default ISP domain, see "Configuring AAA."

You can specify an IPv4 portal authentication domain, an IPv6 portal authentication domain, or both on an interface.

To specify a portal authentication domain on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Specify a portal authentication domain on the interface.	portal [ ipv6 ] domain domain-name	By default, no portal authentication domains are specified on an interface.

Specifying a preauthentication domain

The preauthentication domain takes effect only on portal users with IP addresses obtained through DHCP or DHCPv6.

After you configure a preauthentication domain on a portal-enabled interface, the device authorizes users on the interface as follows:

1. After an unauthenticated user obtains an IP address, the user is assigned authorization attributes configured for the preauthentication domain.

The authorization attributes in a preauthentication domain include ACL, user profile, and CAR.

An unauthenticated user who is authorized with the authorization attributes in a preauthentication domain is called a preauthentication user.

2. After the user passes portal authentication, the user is assigned new authorization attributes from the AAA server.

3. After the user goes offline, the user is reassigned the authorization attributes in the preauthentication domain.

The preauthentication domain does not take effect on interfaces enabled with cross-subnet portal authentication.

Make sure you specify an existing ISP domain as a preauthentication domain. If the specified ISP domain does not exist, the device might operate incorrectly.

You must delete a preauthentication domain (by using the undo portal [ ipv6 ] pre-auth domain command) and reconfigure it in the following situations:

· You create the ISP domain after specifying it as the preauthentication domain.

· You delete the specified ISP domain and then re-create it.

To specify a preauthentication domain:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Specify a preauthentication domain.	portal [ ipv6 ] pre-auth domain domain-name	By default, no preauthentication domain is specified on an interface.

Specifying a preauthentication IP address pool for portal users

You must specify a preauthentication IP address pool on a portal-enabled interface in the following situation:

· Portal users access the network through a subinterface of the portal-enabled interface.

· The subinterface does not have an IP address.

· Portal users need to obtain IP addresses through DHCP.

After a user connects to a portal-enabled interface, the user uses an IP address for portal authentication according to the following rules:

· If the interface is configured with a preauthentication IP address pool, the user uses the following IP address:

¡ If the client is configured to obtain an IP address automatically through DHCP, the user obtains an address from the specified IP address pool.

¡ If the client is configured with a static IP address, the user uses the static IP address. However, if the interface does not have an IP address, users using static IP addresses cannot pass authentication.

· If the interface has an IP address but no preauthentication IP pool specified, the user uses the static IP address or the IP address obtained from a DHCP server.

· If the interface has no IP address or preauthentication IP pool specified, the user cannot perform portal authentication.

After the user passes portal authentication, the AAA server authorizes an IP address pool for re-assigning an IP address to the user. If no authorized IP address pool is deployed, the user continues using the previous IP address.

If the portal user does not perform authentication or fails to pass authentication, the assigned IP address is still retained.

When you specify a preauthentication IP address pool, follow these guidelines and restrictions:

· This configuration takes effect only when the direct IPv4 portal authentication is enabled on the interface.

· Make sure the specified IP address pool exists and is complete. Otherwise, the user cannot obtain the IP address and cannot perform portal authentication.

To specify an IP address pool before portal authentication:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Specify a preauthentication IP address pool for portal users.	portal [ ipv6 ] pre-auth ip-pool pool-name	By default, no preauthentication IP address pool is specified on an interface.

Enabling strict-checking on portal authorization information

The strict checking mode allows a portal user to stay online only when the authorized information for the user is successfully deployed on the interface.

You can enable strict checking on authorized ACLs, authorized user profiles, or both. If you enable both ACL checking and user profile checking, the user will be logged out if either checking fails.

An ACL/user profile checking fails when the authorized ACL/user profile does not exist on the device or the ACL/user profile fails to be deployed.

To enable strict-checking on portal authorization information on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable strict checking mode on portal authorization information.	portal authorization { acl \| user-profile } strict-checking	By default, the strict checking mode is disabled. In this case, the portal users stay online even when the authorized ACLs or user profiles do not exist or fail to be deployed.

Enabling portal authentication only for DHCP users

To ensure that only users with valid IP addresses access the network, enable this feature on an interface. This feature allows only users with DHCP-assigned IP addresses to pass portal authentication. Users with static IP addresses cannot pass portal authentication to get online.

To enable portal authentication only for DHCP users on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable portal authentication only for users with IP addresses obtained through DHCP.	portal [ ipv6 ] user-dhcp-only	By default, both users with IP addresses obtained through DHCP and users with static IP addresses can pass authentication to get online.

Enabling outgoing packets filtering on a portal-enabled interface

When you enable this feature on a portal-enabled interface, the device permits the interface to send the following packets:

· Packets whose destination IP addresses are IP addresses of authenticated portal users.

· Packets that match portal-free rules.

Other outgoing packets on the interface are dropped.

To enable outgoing packets filtering on a portal-enabled interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable outgoing packets filtering.	portal [ ipv6 ] outbound-filter enable	By default, outgoing packets filtering is disabled. The interface can send any packets.

Configure support of dual stack for portal authentication

Typically, IPv4 portal users can access only the IPv4 network after passing portal authentication, and IPv6 portal users can access only the IPv6 network after passing portal authentication. To allow portal users to access both IPv4 and IPv6 networks after passing one type (IPv4 or IPv6) of portal authentication, enable the portal dual-stack feature.

Only direct portal authentication supports the portal dual-stack feature.

To configure support of dual stack for portal authentication:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable the portal dual-stack feature on the interface.	portal dual-stack enable	By default, the portal dual-stack feature is disabled on an interface.
4. Enable separate IPv4 and IPv6 traffic statistics for dual-stack portal users on the interface.	portal dual-stack traffic-separate enable	By default, separate IPv4 and IPv6 traffic statistics is disabled for dual-stack portal users on an interface. The device collects IPv4 and IPv6 traffic statistics collectively.

Configuring portal detection features

Configuring online detection of portal users

Configure online detection to quickly detect abnormal logouts of portal users.

· Configure ARP or ICMP detection for IPv4 portal users.

· Configure ND or ICMPv6 detection for IPv6 portal users.

If the device receives no packets from a portal user within the idle time, the device detects the user's online status as follows:

· ICMP or ICMPv6 detection—Sends ICMP or ICMPv6 requests to the user at configurable intervals to detect the user status.

¡ If the device receives a reply within the maximum number of detection attempts, it considers that the user is online and stops sending detection packets. Then the device resets the idle timer and repeats the detection process when the timer expires.

¡ If the device receives no reply after the maximum number of detection attempts, the device logs out the user.

· ARP or ND detection—Sends ARP or ND requests to the user and detects the ARP or ND entry status of the user at configurable intervals.

¡ If the ARP or ND entry of the user is refreshed within the maximum number of detection attempts, the device considers that the user is online and stops detecting the user's ARP or ND entry. Then the device resets the idle timer and repeats the detection process when the timer expires.

¡ If the ARP or ND entry of the user is not refreshed after the maximum number of detection attempts, the device logs out the user.

ARP and ND detections apply only to direct and re-DHCP portal authentication. ICMP detection applies to all portal authentication modes.

To configure online detection of IPv4 portal users:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure online detection of IPv4 portal users.	portal user-detect type { arp \| icmp } [ retry retries ] [ interval interval ] [ idle time ]	By default, this feature is disabled on the interface.

To configure online detection of IPv6 portal users:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure online detection of IPv6 portal users.	portal ipv6 user-detect type { icmpv6 \| nd } [ retry retries ] [ interval interval ] [ idle time ]	By default, this feature is disabled on the interface.

Configuring portal authentication server detection

During portal authentication, if the communication between the access device and portal authentication server is broken, both of the following occur:

· New portal users are not able to log in.

· The online portal users are not able to log out normally.

To address this problem, the access device needs to be able to detect the reachability changes of the portal server quickly and take corresponding actions to deal with the changes.

With the portal authentication server detection feature, the device periodically detects portal packets sent by a portal authentication server to determine the reachability of the server. If the device receives a portal packet within a detection timeout (timeout timeout) and the portal packet is valid, the device considers the portal authentication server to be reachable. Otherwise, the device considers the portal authentication server to be unreachable.

Portal packets include user login packets, user logout packets, and heartbeat packets. Heartbeat packets are periodically sent by a server. By detecting heartbeat packets, the device can detect the server's actual status more quickly than by detecting other portal packets.

The portal authentication server detection feature takes effect only when the device has a portal-enabled interface.

Only the IMC portal authentication server supports sending heartbeat packets. To test server reachability by detecting heartbeat packets, you must enable the server heartbeat feature on the IMC portal authentication server.

You can configure the device to take one or more of the following actions when the server reachability status changes:

· Sending a trap message to the NMS. The trap message contains the name and current state of the portal authentication server.

· Sending a log message, which contains the name, the current state, and the original state of the portal authentication server.

· Enabling portal fail-permit. When the portal authentication server is unreachable, the portal fail-permit feature on an interface allows users on the interface to have network access. When the server recovers, it resumes portal authentication on the interface. For more information, see "Configuring the portal fail-permit feature."

To configure portal authentication server detection:

Step	Command	Remarks
1. Enter system view.	system-view	N/A-
2. Enter portal authentication server view.	portal server server-name	N/A
3. Configure portal authentication server detection.	server-detect [ timeout timeout ] { log \| trap } *	By default, portal authentication server detection is disabled. This feature takes effect regardless of whether portal authentication is enabled on an interface or not. Make sure the detection timeout is greater than the portal server heartbeat interval on the portal authentication server.

Configuring portal Web server detection

A portal authentication process cannot complete if the communication between the access device and the portal Web server is broken. To address this problem, you can enable portal Web server detection on the access device.

With the portal Web server detection feature, the access device simulates a Web access process to initiate a TCP connection to the portal Web server. If the TCP connection can be established successfully, the access device considers the detection successful, and the portal Web server is reachable. Otherwise, it considers the detection to have failed. Portal authentication status on interfaces of the access device does not affect the portal Web server detection feature.

The portal Web server detection feature takes effect only when the URL of the portal Web server is specified and the device has a portal-enabled interface.

You can configure the following detection parameters:

· Detection interval—Interval at which the device detects the server reachability.

· Maximum number of consecutive failures—If the number of consecutive detection failures reaches this value, the access device considers that the portal Web server is unreachable.

You can configure the device to take one or more of the following actions when the server reachability status changes:

· Sending a trap message to the NMS. The trap message contains the name and current state of the portal Web server.

· Sending a log message, which contains the name, the current state, and the original state of the portal Web server.

· Enabling portal fail-permit. When the portal Web server is unreachable, the portal fail-permit feature on an interface allows users on the interface to have network access. When the server recovers, it resumes portal authentication on the interface. For more information, see "Configuring the portal fail-permit feature."

To configure portal Web server detection:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter portal Web server view.	portal web-server server-name	N/A
3. Configure portal Web server detection.	server-detect [ interval interval ] [ retry retries ] { log \| trap } *	By default, portal Web server detection is disabled. This feature takes effect regardless of whether portal authentication is enabled on an interface or not.

Configuring portal user synchronization

Once the access device loses communication with a portal authentication server, the portal user information on the access device and that on the portal authentication server might be inconsistent after the communication resumes. To address this problem, the device provides the portal user synchronization feature. This feature is implemented by sending and detecting portal synchronization packets, as follows:

1. The portal authentication server sends the online user information to the access device in a synchronization packet at the user heartbeat interval.

The user heartbeat interval is set on the portal authentication server.

2. Upon receiving the synchronization packet, the access device compares the users carried in the packet with its own user list and performs the following operations:

¡ If a user contained in the packet does not exist on the access device, the access device informs the portal authentication server to delete the user. The access device starts the synchronization detection timer (timeout timeout) immediately when a user logs in.

¡ If the user does not appear in any synchronization packet within a synchronization detection interval, the access device considers the user does not exist on the portal authentication server and logs the user out.

Portal user synchronization requires a portal authentication server to support the portal user heartbeat function. Only the IMC portal authentication server supports the portal user heartbeat function. To implement the portal user synchronization feature, you also need to configure the user heartbeat function on the portal authentication server. Make sure the user heartbeat interval configured on the portal authentication server is not greater than the synchronization detection timeout configured on the access device.

Deleting a portal authentication server on the access device also deletes the user synchronization configuration for the portal authentication server.

To configure portal user information synchronization:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter portal authentication server view.	portal server server-name	N/A
3. Configure portal user synchronization.	user-sync timeout timeout	By default, portal user synchronization is disabled.

Configuring the portal fail-permit feature

The portal fail-permit feature takes effects when the portal authentication server or portal Web server is unreachable. When the access device detects that the portal authentication server or portal Web server is unreachable, it allows users on the interface to have network access without portal authentication.

When portal fail-permit is enabled for a portal authentication server and portal Web servers, the interface disables portal authentication in either of the following conditions:

· All portal Web servers are unreachable.

· The specified portal authentication server is unreachable.

Portal authentication resumes when the specified portal authentication server and a minimum of one portal Web server becomes reachable. After portal authentication resumes, users who failed portal authentication and unauthenticated portal users need to pass authentication to access network resources. Portal users who have passed authentication can continue accessing network resources.

On the same interface, the portal Web server is unreachable when both primary and backup portal Web servers are unreachable.

To configure portal fail-permit on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable portal fail-permit for a portal authentication server.	portal [ ipv6 ] fail-permit server server-name	By default, portal fail-permit is disabled for a portal authentication server.
4. Enable portal fail-permit for the portal Web servers specified for the interface.	portal [ ipv6 ] fail-permit web-server	By default, portal fail-permit is disabled for portal Web servers.

Configuring the BAS-IP or BAS-IPv6 attribute

If the device runs Portal 2.0, the unsolicited packets sent to the portal authentication server must carry the BAS-IP attribute. If the device runs Portal 3.0, the unsolicited packets sent to the portal authentication server must carry the BAS-IP or BAS-IPv6 attribute.

If IPv4 portal authentication is enabled on an interface, you can configure the BAS-IP attribute on the interface. If IPv6 portal authentication is enabled on an interface, you can configure the BAS-IPv6 attribute on the interface.

The device uses the configured BAS-IP or BAS-IPv6 address as the source IP address of the portal notifications sent to the portal authentication server. If you do not configure the BAS-IP or BAS-IPv6 attribute, the source IP address is the IP address of the packet's output interface.

During a re-DHCP portal authentication or mandatory user logout process, the device sends portal notification packets to the portal authentication server. For the authentication or logout process to complete, make sure the BAS-IP/BAS-IPv6 attribute is the same as the device IP or IPv6 address specified on the portal authentication server.

To configure the BAS-IP or BAS-IPv6 attribute:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure the BAS-IP attribute on the interface.	portal bas-ip ipv4-address	By default: · The BAS-IP attribute of an IPv4 portal reply packet sent to the portal authentication server is the source IPv4 address of the packet. · The BAS-IP attribute of an IPv4 portal notification packet sent to the portal authentication server is the IPv4 address of the packet's output interface.
4. Configure the BAS-IPv6 attribute on the interface.	portal bas-ipv6 ipv6-address	By default: · The BAS-IPv6 attribute of an IPv6 portal reply packet sent to the portal authentication server is the source IPv6 address of the packet. · The BAS-IPv6 attribute of an IPv6 portal notification packet sent to the portal authentication server is the IPv6 address of the packet's output interface.

Specifying a format for the NAS-Port-Id attribute

RADIUS servers from different vendors might require different formats of the NAS-Port-Id attribute in the RADIUS packets. You can specify the NAS-Port-Id attribute format as required.

The device supports the NAS-Port-Id attribute in format 1, format 2, format 3, and format 4. For more information about the formats, see Security Command Reference.

To specify a format for the NAS-Port-Id attribute:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify the format for the NAS-Port-Id attribute.	portal nas-port-id format { 1 \| 2 \| 3 \| 4 }	By default, the format for the NAS-Port-Id attribute is format 2.

Specifying the device ID

The portal authentication server uses device IDs to identify the devices that send protocol packets to the portal server.

Make sure the configured device ID is different than any other access devices communicating with the same portal authentication server.

To specify the device ID:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify the device ID.	portal device-id device-id	By default, a device is not configured with a device ID.

Enabling portal roaming

Portal roaming takes effect only on portal users logging in from VLAN interfaces. It does not take effect on portal users logging in from common Layer 3 interface.

If portal roaming is enabled on a VLAN interface, an online portal user can access resources from any Layer 2 port in the VLAN without re-authentication.

If portal roaming is disabled, to access external network resources from a Layer 2 port different from the current access port in the VLAN, the user must do the following:

· First log out from the current port.

· Then re-authenticate on the new Layer 2 port.

To enable portal roaming:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable portal roaming.	portal roaming enable	By default, portal roaming is disabled.

Logging out online portal users

This feature deletes users that have passed portal authentication and terminates ongoing portal authentications.

When the number of online users exceeds 2000, executing the portal delete-user command takes a few minutes. To ensure successful logout of online users, do not perform the following operations during the command execution:

· Master/backup device switchover.

· Active/standby MPU switchover.

· Disabling portal authentication on the interface.

To log out online users:

Step	Command
1. Enter system view.	system-view
2. Log out IPv4 online portal users.	portal delete-user { ipv4-address \| all \| auth-type { cloud \| email \| local \| normal \| qq \| wechat } \| interface interface-type interface-number \| ipv6 ipv6-address \| mac mac-address \| username username }
3. Log out IPv6 online portal users.	portal delete-user { all \| auth-type { cloud \| email \| local \| normal \| qq \| wechat } \| interface interface-type interface-number \| ipv6 ipv6-address \| mac mac-address \| username username }

Disabling traffic accounting for portal users

The accounting server might perform time-based or traffic-based accounting, or it might not perform accounting.

If the accounting server does not perform traffic-based accounting, disable traffic accounting for portal users on the device. The device will provide quick accounting for portal users, and the traffic statistics will be imprecise.

If the accounting server performs traffic-based accounting, enable traffic accounting for portal users. The device will provide precise traffic statistics for portal users.

To disable traffic accounting for portal users:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Disable traffic accounting for portal users.	portal traffic-accounting disable	By default, traffic accounting is enabled for portal users.

Configuring Web redirect

Web redirect is a simplified portal feature. This feature redirects a user on an interface to the specified URL when the user accesses an external network through a Web browser. After the specified redirect interval, the user is redirected from the visiting website to the specified URL again.

Web redirect can provide ISPs with extended services. For example, the ISPs can place advertisements and publish information on the redirected webpage.

On Etherchannel interfaces, both Web redirect and portal authentication can be enabled at the same time. On non-Etherchannel interfaces, Web redirect does not work when both Web redirect and portal authentication are enabled.

To configure Web redirect on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Configure Web redirect on the interface.	web-redirect [ ipv6 ] url url-string [ interval interval ]	By default, Web redirect is disabled on an interface.

Applying a NAS-ID profile to an interface

By default, the device sends its device name in the NAS-Identifier attribute of all RADIUS requests.

A NAS-ID profile enables you to send different NAS-Identifier attribute strings in RADIUS requests from different VLANs. The strings can be organization names, service names, or any user categorization criteria, depending on the administrative requirements.

For example, map the NAS-ID companyA to all VLANs of company A. The device will send companyA in the NAS-Identifier attribute for the RADIUS server to identify requests from any Company A users.

You can apply a NAS-ID profile to a portal-enabled interface. If no NAS-ID profile is specified on the interface or no matching NAS-ID is found in the specified profile, the device uses the device name as the interface NAS-ID.

To apply a NAS-ID profile to an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a NAS-ID profile and enter NAS-ID profile view.	aaa nas-id profile profile-name	For more information about this command, see Security Command Reference.
3. Configure a NAS ID and VLAN binding in the profile.	nas-id nas-identifier bind vlan vlan-id	For more information about this command, see Security Command Reference.
4. Return to system view.	quit	N/A
5. Enter interface view.	interface interface-type interface-number	N/A
6. Specify the NAS-ID profile on the interface.	portal nas-id-profile profile-name	By default, no NAS-ID profile is specified on the interface.

Configuring the local portal Web server feature

To perform local portal authentication for users, perform the following tasks:

· Configure a local portal Web server.

· Configure a name for the portal Web server and specify a local IP address of the device as the server's URL.

· Enable portal authentication on the user access interface.

· Specify the portal Web server on the portal-enabled interface.

During local portal authentication, the local Web portal server pushes authentication pages to users.

Customizing authentication pages

Authentication pages are HTML files. Local portal authentication requires the following authentication pages:

· Logon page

· Logon success page

· Logon failure page

· Online page

· System busy page

· Logoff success page

You must customize the authentication pages, including the page elements that the authentication pages will use, for example, back.jpg for authentication page Logon.htm.

Follow the authentication page customization rules when you edit the authentication page files.

File name rules

The names of the main authentication page files are fixed (see Table 1). You can define the names of the files other than the main authentication page files. File names and directory names are case insensitive.

Table 1 Main authentication page file names

Main authentication page	File name
Logon page	logon.htm
Logon success page	logonSuccess.htm
Logon failure page	logonFail.htm
Online page Pushed after the user gets online for online notification	online.htm
System busy page Pushed when the system is busy or the user is in the logon process	busy.htm
Logoff success page	logoffSuccess.htm

Page request rules

The local portal Web server supports only Get and Post requests.

· Get requests—Used to get the static files in the authentication pages and allow no recursion. For example, if file Logon.htm includes contents that perform Get action on file ca.htm, file ca.htm cannot include any reference to file Logon.htm.

· Post requests—Used when users submit username and password pairs, log in, and log out.

Post request attribute rules

1. Observe the following requirements when editing a form of an authentication page:

¡ An authentication page can have multiple forms, but there must be one and only one form whose action is logon.cgi. Otherwise, user information cannot be sent to the local portal Web server.

¡ The username attribute is fixed as PtUser. The password attribute is fixed as PtPwd.

¡ The value of the PtButton attribute is either Logon or Logoff, which indicates the action that the user requests.

¡ A logon Post request must contain PtUser, PtPwd, and PtButton attributes.

¡ A logoff Post request must contain the PtButton attribute.

2. Authentication pages logon.htm and logonFail.htm must contain the logon Post request.

The following example shows part of the script in page logon.htm.

<p>Password :<input type="password" name = "PtPwd" style="width:160px;height:22px" maxlength=32>

</form>

3. Authentication pages logonSuccess.htm and online.htm must contain the logoff Post request.

The following example shows part of the script in page online.htm.

</form>

Page file compression and saving rules

You must compress the authentication pages and their page elements into a standard zip file.

· The name of a zip file can contain only letters, numbers, and underscores.

· The authentication pages must be placed in the root directory of the zip file.

· Zip files can be transferred to the device through FTP or TFTP and must be saved in the root directory of the device.

Examples of zip files on the device:

<Sysname> dir

Directory of flash:

1 -rw- 1405 Feb 28 2008 15:53:20

0 -rw- 1405 Feb 28 2008 15:53:31

2 -rw- 1405 Feb 28 2008 15:53:39

3 -rw- 1405 Feb 28 2008 15:53:44

2540 KB total (1319 KB free)

Redirecting authenticated users to a specific webpage

To make the device automatically redirect authenticated users to a specific webpage, do the following in logon.htm and logonSuccess.htm:

1. In logon.htm, set the target attribute of Form to _blank.

See the contents in gray:

2. Add the function for page loading pt_init() to logonSucceess.htm.

See the contents in gray:

<html>

<head>

<title>LogonSuccessed</title>

</head>

... ...

</body>

</html>

Configuring a local portal Web server

Perform the following tasks for the local portal Web server to support HTTPS:

· Configure a PKI policy, obtain the CA certificate, and request a local certificate. For more information, see "Configuring PKI."

· Configure an SSL server policy, and specify the PKI domain configured in the PKI policy. For more information, see "Configuring SSL."

To configure a local portal Web server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure a local portal Web server and enter its view.	portal local-web-server { http \| https [ ssl-server-policy policy-name ] }	By default, no local portal Web servers exist.
3. Specify the default authentication page file for the local portal Web server.	default-logon-page filename	By default, a default authentication page file exists for the local portal Web server.
4. (Optional.) Configure the listening TCP port for the local portal Web server.	tcp-port port-number	By default, the HTTP service listening port number is 80 and the HTTPS service listening port number is 443.
5. (Optional.) Enable local portal user password modification.	user-password modify enable	By default, local portal user password modification is disabled.

Enabling ARP or ND entry conversion for portal clients

This feature converts the ARP or ND entries to Rule ARP or ND entries for portal users. Rule ARP or ND entries will not be aged and they will be deleted immediately when the portal users go offline.

When this feature is disabled, ARP or ND entries for portal users are dynamic entries and will be aged out when their respective aging timers expire. Rule ARP or ND entries created before the feature is disabled still exist until the portal users go offline.

This feature is enabled by default. If a user logs out and then tries to get online before the ARP or ND entry is relearned for the user, the user will fail the authentication. Therefore, in scenarios where portal users might get online and offline frequently in a short time, disable this feature to avoid immediate deletion of the ARP or ND entries when users go offline.

Enabling or disabling of this feature takes effect only on portal users who pass authentication after the feature is enabled or disabled.

To configure ARP or ND entry conversion for portal clients:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable ARP or ND entry conversion for portal clients.	portal refresh { arp \| nd } enable	By default, ARP or ND entry conversion is enabled for portal clients.
3. Disable ARP or ND entry conversion for portal clients.	undo portal refresh { arp \| nd } enable	By default, ARP or ND entry conversion is enabled for portal clients.

Configuring HTTPS redirect

The device can redirect HTTPS requests to the portal Web server for portal authentication. During SSL connection establishment, the user browser might display a message that it cannot verify server identity by certificate. For users to perform portal authentication without checking such a message, configure an SSL server policy to request a client-trusted certificate on the device. The name of the policy must be https_redirect. For information about SSL server policy configuration, see "Configuring SSL." For information about certificate request, see "Configuring PKI."

To configure HTTPS redirect:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an SSL server policy and enter its view.	ssl server-policy policy-name	By default, no SSL server policies exist on the device. The name of the SSL server policy for HTTPS redirect must be https_redirect. For more information about this command, see Security Command Reference.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create an SSL server policy and enter its view.

ssl server-policy policy-name

By default, no SSL server policies exist on the device.

The name of the SSL server policy for HTTPS redirect must be https_redirect.

For more information about this command, see Security Command Reference.

Configuring portal safe-redirect

Portal safe-redirect filters HTTP requests by HTTP request method, browser type (in HTTP User Agent), and destination URL, and redirects only the permitted HTTP requests. This reduces the risk that the portal Web server cannot respond to HTTP requests because of overload.

Table 2 Browser types supported by portal safe-redirect

Browser type	Description
Safari	Apple browser
Chrome	Google browser
Firefox	Firefox browser
UC	UC browser
QQBrowser	QQ browser
LBBROWSER	Cheetah browser
TaoBrowser	Taobao browser
Maxthon	Maxthon browser
BIDUBrowser	Baidu browser
MSIE 10.0	Microsoft IE 10.0 browser
MSIE 9.0	Microsoft IE 9.0 browser
MSIE 8.0	Microsoft IE 8.0 browser
MSIE 7.0	Microsoft IE 7.0 browser
MSIE 6.0	Microsoft IE 6.0 browser
MetaSr	Sogou browser

To configure portal safe-redirect:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable portal safe-redirect.	portal safe-redirect enable	By default, the portal safe-redirect feature is disabled.
3. (Optional.) Specify HTTP request methods permitted by portal safe-redirect.	portal safe-redirect method { get \| post } *	By default, the device can redirect only HTTP requests with GET method after portal safe-redirect is enabled.
4. (Optional.) Specify a browser type permitted by portal safe-redirect.	portal safe-redirect user-agent user-agent-string	By default, no browser types are specified. The device can redirect HTTP requests sent by all supported browsers (see Table 2) after portal safe-redirect is enabled.
5. (Optional.) Configure a URL forbidden by portal safe-redirect.	portal safe-redirect forbidden-url user-url-string	By default, no forbidden URLs are configured. The device can redirect HTTP requests with any URLs.
6. (Optional.) Configure a filename extension forbidden by portal safe-redirect.	portal safe-redirect forbidden-file filename-extension	By default, no forbidden filename extensions are configured. The device redirects HTTP requests regardless of the file extension in the URL.

Configuring the captive-bypass feature

Typically, when iOS mobile devices or some Android mobile devices are connected a portal-enabled network, the device pushes the authentication page to the mobile devices.

The captive-bypass feature enables the device to push the portal authentication page to the iOS and Android devices only when the users access the Internet by using a browser. If the users do not perform authentication but press the home button to return to the desktop, the Wi-Fi connection is terminated. To maintain the Wi-Fi connection in such cases, you can enable the optimized captive-bypass feature.

When optimized captive-bypass is enabled, the portal authentication page is automatically pushed to iOS mobile devices after they connects to the network. Users can perform authentication on the page or press the home button to return to the desktop without performing authentication, and the Wi-Fi connection is not terminated.

When an iOS client is connected to a network, it automatically sends a server reachability detection packet to determine whether the Apple server is reachable. If the server is reachable, the Wi-Fi connection displays connected. If the server is not reachable, the Wi-Fi connection is terminated.

When the network condition is poor, the device cannot detect a server reachability detection packet from an iOS mobile client within the captive-bypass detection timeout time. The client cannot receive a response for the server reachability detection packet, and therefore it determines the server to be unreachable and terminates the Wi-Fi connection. To avoid Wi-Fi disconnections caused by server reachability detection failure, set a longer captive-bypass detection timeout time when the network condition is poor.

To configure the captive-bypass feature:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a portal Web server and enter its view.	portal web-server server-name	By default, no portal Web servers exist.
3. Enable the captive-bypass feature.	captive-bypass [ android \| ios [ optimize ] ] enable	By default, the captive-bypass feature is disabled. The device automatically pushes the portal authentication page to iOS mobile devices and some Android mobile devices when they are connected to a portal-enabled network.
4. Return to system view.	quit	N/A
5. (Optional.) Set the captive-bypass detection timeout time.	portal captive-bypass optimize delay seconds	By default, the captive-bypass detection timeout time is 6 seconds.

Excluding an attribute from portal protocol packets

Support of the portal authentication server for portal protocol attributes varies by the server type. If the device sends the portal authentication server a packet that contains an attribute unsupported by the server, the device and the server cannot communicate.

To address this issue, you can configure portal protocol packets to not carry the attributes unsupported by the portal authentication server.

To exclude an attribute from portal protocol packets for a portal authentication server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter portal authentication server view.	portal server server-name	N/A
3. Exclude an attribute from portal protocol packets.	exclude-attribute number { ack-auth \| ntf-logout \| ack-logout }	By default, no attributes are excluded from portal protocol packets.

Enabling portal logging

To help with security audits, you can enable portal logging to record portal authentication information.

For portal log messages to be sent correctly, you must also configure the information center on the device. For more information about information center configuration, see Network Management and Monitoring Configuration Guide.

To enable portal logging:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable logging for portal user logins and logouts.	portal user log enable	By default, portal user login and logout logging is disabled.
3. Enable logging for portal protocol packets.	portal packet log enable	By default, portal protocol packet logging is disabled.
4. Enable logging for portal redirect.	portal redirect log enable	By default, portal redirect logging is disabled.

Configuring portal support for third-party authentication

You can configure the device to support QQ authentication or email authentication as third-party authentication for portal. Users can use QQ or email accounts to complete portal authentication instead of using a dedicated portal account. No portal authentication servers are required to be deployed, and no local portal users are required to be created on the device. This reduces the management and maintenance cost.

Only direct portal authentication that uses a local portal Web server supports third-party authentication.

Editing buttons and pages for third-party authentication

To use third-party authentication for portal users, you must add a QQ or email authentication button to the portal logon page. After a portal user clicks the QQ or email authentication button on the portal logon page, the user is redirected to the QQ or email authentication page.

Editing a third-party authentication button on the logon page

Edit a third-party authentication button on the portal logon page (logon.htm). For more information about editing portal authentication pages, see "Customizing authentication pages."

When you edit the QQ authentication button, you must call the pt_getQQSubmitUrl() function to get the URL of the QQ authentication page.

The following example shows part of the script of the QQ authentication button.

<html>

<head>

<title>Logon</title>

function setQQUrl(){

document.getElementById("qqurl").href = pt_getQQSubmitUrl();

}

</script>

</head>

<body>

... ...

... ...

</body>

</html>

No special requirements exist in the process of editing an email authentication button.

Editing a third-party authentication page

You only need to edit the email authentication page. The QQ authentication page is provided by Tencent.

When you edit the email authentication page, follow the rules in "Customizing authentication pages" and the following rules:

· Set the action attribute of the beginning form tag to maillogin.html. Otherwise, the device cannot send the user information

· Save the login page as emailLogon.htm.

The following example shows part of the script of the emailLogon.htm page.

<p>Password :<input type="password" name = "PtPwd" style="width:160px;height:22px" maxlength=32>

</form>

Configuring a third-party authentication server

Configuring the QQ authentication server

To use QQ authentication for portal users, you must go to the Tencent Open Platform (http://connect.qq.com/intro/login) to finish the following tasks:

1. Register as a developer by using a valid QQ account.

2. Apply the access to the platform for your website. The website is the webpage to which users are redirected after passing QQ authentication.

You will obtain the APP ID and APP key from the Tencent Open Platform after your application succeeds.

After a portal user passes QQ authentication, the QQ authentication server sends the authorization code of the user to the portal Web server. After the portal Web server receives the authorization code, it sends the authorization code of the user, the APP ID, and the APP key to the QQ authentication server for verification. If the information is verified as correct, the device determines that the user passes QQ authentication.

To configure the QQ authentication server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a QQ authentication server and enter its view.	portal extend-auth-server qq	By default, no QQ authentication server exists.
3. Specify the URL of the QQ authentication server.	auth-url url-string	By default, the URL of QQ authentication server is https://graph.qq.com.
4. Specify the redirection URL for QQ authentication success.	redirect-url url-string	By default, the redirection URL for QQ authentication success is http://lvzhou.h3c.com/portal/qqlogin.html. The redirection URL must be the same as that specified during website application on the Tencent Open Platform.
5. Specify the APP ID for QQ authentication.	app-id app-id	By default, an APP ID for QQ authentication exists.
6. Specify the APP key for QQ authentication.	app-key { cipher \| simple } app-key	By default, an APP key for QQ authentication exists.

Configuring the email authentication server

If a user chooses email authentication, the user can access the network after passing email authentication.

To configure the email authentication server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an email authentication server and enter its view.	portal extend-auth-server mail	By default, no email authentication server exists.
3. Specify protocols for email authentication.	mail-protocol { imap \| pop3 } *	By default, no protocols are specified for email authentication.
4. Specify an email domain name for email authentication.	mail-domain-name string	By default, no email domain names are specified for email authentication.

Specifying an authentication domain for third-party authentication

You must specify an authentication domain for third-party authentication. Make sure the authentication, authorization, and accounting methods in the authentication domain for portal users are none.

To specify an authentication domain for third-party authentication on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Specify an authentication domain for third-party authentication on the interface.	portal extend-auth domain domain-name	By default, no authentication domain is specified for third-party authentication on an interface.

Configuring portal temporary pass

Typically, a portal user cannot access the Internet before passing portal authentication. This feature allows a user to access the Internet temporarily if the user uses a WeChat account to perform portal authentication. During the temporary pass period, the user can provide WeChat authentication information to the WeChat server for the server to interact with the access device to finish portal authentication.

To configure portal temporary pass on an interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Enable portal temporary pass and set the temporary pass period on the interface.	portal temp-pass [ period period-value ] enable	By default, portal temporary pass is disabled on an interface.
4. Return to system view.	quit	N/A
5. Enter portal Web server view.	portal web-server server-name	N/A
6. Configure a match rule for temporary pass.	if-match { original-url url-string \| user-agent user-agent } * temp-pass [ redirect-url url-string \| original ]	By default, no match rules for temporary pass exist.

Configure the portal authentication monitoring feature

The portal authentication monitoring feature records portal user offlines, authentication failures, and authentication errors. These records provide facilitation for the administrator to quickly determine causes of authentication faults.

To configure the portal authentication monitoring feature:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable portal user offline recording.	portal logout-record enable	By default, portal user offline recording is disabled.
3. Set the maximum number of portal user offline records.	portal logout-record max number	By default, the maximum number of portal user offline records is 32000.
4. Export portal user offline records to a path.	portal logout-record export url url-string [ start-time start-date start-time end-time end-date end-time ]	N/A
5. Enable portal authentication failure recording.	portal auth-fail-record enable	By default, portal authentication failure recording is disabled.
6. Set the maximum number of portal authentication failure records.	portal auth-fail-record max number	By default, the maximum number of portal authentication failure records is 32000.
7. Export portal authentication failure records to a path.	portal auth-fail-record export url url-string [ start-time start-date start-time end-time end-date end-time ]	N/A
8. Enable portal authentication error recording.	portal auth-error-record enable	By default, portal authentication error recording is disabled.
9. Set the maximum number of portal authentication error records.	portal auth-error-record max number	By default, the maximum number of portal authentication error records is 32000.
10. Export portal authentication error records to a path.	portal auth-error-record export url url-string [ start-time start-date start-time end-time end-date end-time ]	N/A

Displaying and maintaining portal

Execute display commands in any view and the reset command in user view.

Task	Command
Display portal authentication error records.	display portal auth-error-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time }
Display portal authentication failure records.	display portal auth-fail-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time \| username username }
Display packet statistics for portal captive-bypass (in standalone mode).	display portal captive-bypass statistics [ slot slot-number ]
Display packet statistics for portal captive-bypass feature (in IRF mode).	display portal captive-bypass statistics [ chassis chassis-number slot slot-number ]
Display information about third-party authentication servers.	display portal extend-auth-server { all \| qq \| mail }
Display portal user offline records.	display portal logout-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time \| username username }
Display portal rules (in standalone mode).	display portal rule { all \| dynamic \| static } interface interface-type interface-number [ slot slot-number ]
Display portal rules (in IRF mode).	display portal rule { all \| dynamic \| static } interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Display portal configuration and portal running state information.	display portal interface-type interface-number
Display portal authentication server information.	display portal server [ server-name ]
Display portal Web server information.	display portal web-server [ server-name ]
Display packet statistics for portal authentication servers.	display portal packet statistics [extend-auth-server { cloud \| mail \| qq \| wechat } \| server server-name ]
Display portal redirect packet statistics (in standalone mode).	display portal redirect statistics [ slot slot-number ]
Display portal redirect packet statistics (in IRF mode).	display portal redirect statistics [ chassis chassis-number slot slot-number ]
Display portal user information.	display portal user { all \| auth-type { cloud \| email \| local \| normal \| qq \| wechat } \| interface interface-type interface-number \| ip ip-address \| ipv6 ipv6-address \| mac mac-address \| pre-auth [ interface interface-type interface-number \| ip ip-address \| ipv6 ipv6-address ] \| username username } [ brief \| verbose ]
Display the number of portal users.	display portal user count
Display Web redirect rule information (in standalone mode).	display web-redirect rule { interface interface-type interface-number [ slot slot-number ] }
Display Web redirect rule information (in IRF mode).	display web-redirect rule interface interface-type interface-number [ chassis chassis-number slot slot-number ] }
Clear portal authentication error records.	reset portal auth-error-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time }
Clear portal authentication failure records.	reset portal auth-fail-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time \| username username }
Clear packet statistics for portal captive-bypass (in standalone mode).	reset portal captive-bypass statistics [ slot slot-number ]
Clear packet statistics for portal captive-bypass (in IRF mode).	reset portal captive-bypass statistics [ chassis chassis-number slot slot-number ]
Clear portal user offline records.	reset portal logout-record { all \| ipv4 ipv4-address \| ipv6 ipv6-address \| start-time start-date start-time end-time end-date end-time \| username username }
Clear packet statistics for portal authentication servers.	reset portal packet statistics [ extend-auth-server { cloud \| mail \| qq \| wechat } \| server server-name ]
Clear portal redirect packet statistics (in standalone mode).	reset portal redirect statistics [ slot slot-number ]
Clear portal redirect packet statistics (in IRF mode).	reset portal redirect statistics [ chassis chassis-number slot slot-number ]
Display packet statistics for portal safe-redirect (in standalone mode).	display portal safe-redirect statistics [ slot slot-number ]
Display packet statistics for portal safe-redirect (in IRF mode).	display portal safe-redirect statistics [ chassis chassis-number slot slot-number ]
Clear packet statistics for portal safe-redirect (in standalone mode).	reset portal safe-redirect statistics [ slot slot-number ]
Clear packet statistics for portal safe-redirect (in IRF mode).	reset portal safe-redirect statistics [ chassis chassis-number slot slot-number ]

Portal configuration examples

Configuring direct portal authentication

Network requirements

As shown in Figure 6, the host is directly connected to the router (the access device). The host is assigned a public IP address either manually or through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication, so the host can access only the portal server before passing the authentication and access other network resources after passing the authentication.

Figure 6 Network diagram

Configuration prerequisites

· Configure IP addresses for the host, router, and servers as shown in Figure 6 and make sure they can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

Configuring the portal authentication server on IMC PLAT 3.20

In this example, the portal server runs on IMC PLAT 3.20-R2602P13 and IMC UAM 3.60-E6301.

1. Configure the portal authentication server:

a. Log in to IMC and click the Service tab.

b. Select Access Service > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 7.

c. Configure the portal server parameters as needed.

This example uses the default values.

d. Click OK.

Figure 7 Portal authentication server configuration

2. Configure the IP address group:

a. Select Access Service > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.

b. Click Add to open the page as shown in Figure 8.

c. Enter the IP group name.

d. Enter the start IP address and end IP address of the IP group.

Make sure the host IP address (2.2.2.2) is in the IP group.

e. Select a service group.

This example uses the default group Ungrouped.

f. Select Normal from the Action list.

g. Click OK.

Figure 8 Adding an IP address group

3. Add a portal device:

a. Select Access Service > Portal Service Management > Device from the navigation tree to open the portal device configuration page.

b. Click Add to open the page as shown in Figure 9.

c. Enter the device name NAS.

d. Enter the IP address of the router's interface connected to the host.

e. Enter the key, which must be the same as that configured on the router.

f. Set whether to enable IP address reallocation.

This example uses direct portal authentication, and therefore select No from the Reallocate IP list.

g. Set whether to support the portal server heartbeat and user heartbeat functions.

In this example, select No for both Support Server Heartbeat and Support User Heartbeat.

h. Click OK.

Figure 9 Adding a portal device

4. Associate the portal device with the IP address group:

a. As shown in Figure 10, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.

Figure 10 Device list

b. Click Add to open the page as shown in Figure 11.

Figure 11 Port group configuration

c. Enter the port group name.

d. Select the configured IP address group.

The IP address used by the user to access the network must be within this IP address group.

e. Click OK.

5. Select Access Service > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the portal authentication server on IMC PLAT 5.0

In this example, the portal server runs on IMC PLAT 5.0(E0101) and IMC UAM 5.0(E0101).

1. Configure the portal authentication server:

a. Log in to IMC and click the Service tab.

b. Select User Access Manager > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 12.

c. Configure the portal server parameters as needed.

This example uses the default settings.

d. Click OK.

Figure 12 Portal server configuration

2. Configure the IP address group:

a. Select User Access Manager > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.

b. Click Add to open the page as shown in Figure 13.

c. Enter the IP group name.

d. Enter the start IP address and end IP address of the IP group.

Make sure the host IP address is in the IP group.

e. Select a service group.

This example uses the default group Ungrouped.

f. Select Normal from the Action list.

g. Click OK.

Figure 13 Adding an IP address group

3. Add a portal device:

a. Select User Access Manager > Portal Service Management > Device from the navigation tree to open the portal device configuration page.

b. Click Add to open the page as shown in Figure 14.

c. Enter the device name NAS.

d. Enter the IP address of the router's interface connected to the host.

e. Enter the key, which must be the same as that configured on the router.

f. Set whether to enable IP address reallocation.

This example uses direct portal authentication, and therefore select No from the Reallocate IP list.

g. Select whether to support server heartbeat and user heartbeat functions.

In this example, select No for both Support Server Heartbeat and Support User Heartbeat.

h. Click OK.

Figure 14 Adding a portal device

4. Associate the portal device with the IP address group:

a. As shown in Figure 15, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.

b. Click Add to open the page as shown in Figure 16.

c. Enter the port group name.

d. Select the configured IP address group.

The IP address used by the user to access the network must be within this IP address group.

e. Use the default settings for other parameters.

f. Click OK.

Figure 15 Device list

Figure 16 Adding a port group

5. Select User Access Manager > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the router

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.112

[Router-radius-rs1] primary accounting 192.168.0.112

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] key accounting simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[Router-radius-rs1] user-name-format without-domain

[Router-radius-rs1] quit

# Enable RADIUS session control.

[Router] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

# Configure domain dm1 as the default ISP domain. If a user enters the username without the ISP domain name at login, the authentication and accounting methods of the default domain are used for the user.

[Router] domain default enable dm1

3. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable direct portal authentication on GigabitEthernet 1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method direct

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 2.2.2.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 2.2.2.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Router] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet 1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Direct

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 2.2.2.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

A user can perform portal authentication by using the H3C iNode client or a Web browser. Before passing the authentication, the user can access only the authentication page http://192.168.0.111:8080/portal. All Web requests from the user will be redirected to the authentication page. After passing the authentication, the user can access other network resources.

# After the user passes authentication, use the following command to display information about the portal user.

[Router] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 2.2.2.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: N/A

CAR: N/A

Configuring re-DHCP portal authentication

Network requirements

As shown in Figure 17, the host is directly connected to the router (the access device). The host obtains an IP address through the DHCP server. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure re-DHCP portal authentication. Before passing the authentication, the host is assigned a private IP address. After passing the authentication, the host gets a public IP address and can access network resources.

Figure 17 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 17 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· For re-DHCP portal authentication, configure a public address pool (20.20.20.0/24) and a private address pool (10.0.0.0/24) on the DHCP server. (Details not shown.)

· For re-DHCP portal authentication:

¡ The router must be configured as a DHCP relay agent.

¡ The portal-enabled interface must be configured with a primary IP address (a public IP address) and a secondary IP address (a private IP address).

For information about DHCP relay agent configuration, see Layer 3—IP Services Configuration Guide.

· Make sure the IP address of the portal device added on the portal server is the public IP address (20.20.20.1) of the router's interface connecting the host. The private IP address range for the IP address group associated with the portal device is the private subnet 10.0.0.0/24 where the host resides. The public IP address range for the IP address group is the public subnet 20.20.20.0/24.

Configuration procedure

Perform the following tasks on the router.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.113

[Router-radius-rs1] primary accounting 192.168.0.113

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] key accounting simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[Router-radius-rs1] user-name-format without-domain

[Router-radius-rs1] quit

# Enable RADIUS session control.

[Router] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

[Router] domain default enable dm1

3. Configure DHCP relay and authorized ARP:

# Configure DHCP relay.

[Router] dhcp enable

[Router] dhcp relay client-information record

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] ip address 20.20.20.1 255.255.255.0

[Router–GigabitEthernet1/1/2] ip address 10.0.0.1 255.255.255.0 sub

[Router-GigabitEthernet1/1/2] dhcp select relay

[Router-GigabitEthernet1/1/2] dhcp relay server-address 192.168.0.112

# Enable authorized ARP.

[Router-GigabitEthernet1/1/2] arp authorized enable

[Router-GigabitEthernet1/1/2] quit

4. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable re-DHCP portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router-GigabitEthernet1/1/2] portal enable method redhcp

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 20.20.20.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Router] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Redhcp

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 20.20.20.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

Before passing the authentication, a user that uses the H3C iNode client can access only the authentication page http://192.168.0.111:8080/portal. All Web requests from the user will be redirected to the authentication page. After passing the authentication, the user can access other network resources.

# After the user passes authentication, use the following command to display information about the portal user.

[Router] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 20.20.20.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: N/A

CAR: N/A

Configuring cross-subnet portal authentication

Network requirements

As shown in Figure 18, Router A supports portal authentication. The host accesses Router A through Router B. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure Router A for cross-subnet portal authentication. Before passing the authentication, the host can access only the portal server. After passing the authentication, the user can access other network resources.

Figure 18 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 18 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· Make sure the IP address of the portal device added on the portal authentication server is the IP address (20.20.20.1) of the router's interface connecting the host. The IP address group associated with the portal device is the subnet of the host (8.8.8.0/24).

Configuration procedure

Perform the following tasks on Router A.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<RouterA> system-view

[RouterA] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[RouterA-radius-rs1] primary authentication 192.168.0.112

[RouterA-radius-rs1] primary accounting 192.168.0.112

[RouterA-radius-rs1] key authentication simple radius

[RouterA-radius-rs1] key accounting simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[RouterA-radius-rs1] user-name-format without-domain

[RouterA-radius-rs1] quit

# Enable RADIUS session control.

[Router] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[RouterA] domain dm1

# Configure AAA methods for the ISP domain.

[RouterA-isp-dm1] authentication portal radius-scheme rs1

[RouterA-isp-dm1] authorization portal radius-scheme rs1

[RouterA-isp-dm1] accounting portal radius-scheme rs1

[RouterA-isp-dm1] quit

[Router] domain default enable dm1

3. Configure portal authentication:

# Configure a portal authentication server.

[RouterA] portal server newpt

[RouterA-portal-server-newpt] ip 192.168.0.111 key simple portal

[RouterA-portal-server-newpt] port 50100

[RouterA-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[RouterA-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[RouterA-portal-websvr-newpt] quit

# Enable cross-subnet portal authentication on GigabitEthernet 1/1/2.

[RouterA] interface gigabitethernet 1/1/2

[RouterA–GigabitEthernet1/1/2] portal enable method layer3

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[RouterA–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[RouterA–GigabitEthernet1/1/2] portal bas-ip 20.20.20.1

[RouterA–GigabitEthernet1/1/2] quit

On Router B, configure a default route to subnet 192.168.0.0/24, specifying the next hop address as 20.20.20.1. (Details not shown.)

Verifying the configuration

# Verify that the portal configuration has taken effect.

[RouterA] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Layer3

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 20.20.20.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

# After the user passes authentication, use the following command to display information about the portal user.

[RouterA] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 8.8.8.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: N/A

CAR: N/A

Configuring extended direct portal authentication

Network requirements

As shown in Figure 19, the host is directly connected to the router (the access device). The host is assigned a public IP address either manually or through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure extended direct portal authentication. If the host fails security check after passing identity authentication, it can access only subnet 192.168.0.0/24. After passing security check, the host can access other network resources.

Figure 19 Network diagram

Configuration prerequisites

· Configure IP addresses for the host, router, and servers as shown in Figure 19 and make sure they can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

Configuration procedure

Perform the following tasks on the router.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.112

[Router-radius-rs1] primary accounting 192.168.0.112

[Router-radius-rs1] key accounting simple radius

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] user-name-format without-domain

# Enable RADIUS session control.

[Router] radius session-control enable

# Specify a session-control client with IP address 192.168.0.113 and shared key 12345 in plain text.

[Router] radius session-control client ip 192.168.0.113 key simple 12345

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

[Router] domain default enable dm1

3. Configure ACL 3000 as the isolation ACL and ACL 3001 as the security ACL.

[Router] acl advanced 3000

[Router-acl-ipv4-adv-3000] rule permit ip destination 192.168.0.0 0.0.0.255

[Router-acl-ipv4-adv-3000] rule deny ip

[Router-acl-ipv4-adv-3000] quit

[Router] acl advanced 3001

[Router-acl-ipv4-adv-3001] rule permit ip

[Router-acl-ipv4-adv-3001] quit

NOTE:

Make sure you specify ACL 3000 as the isolation ACL and ACL 3001 as the security ACL on the security policy server.

4. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable direct portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method direct

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 2.2.2.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 2.2.2.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Router] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Direct

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 2.2.2.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

Before passing portal authentication, a user that uses the H3C iNode client can access only the authentication page http://192.168.0.111:8080/portal. All Web requests from the user will be redirected to the authentication page.

· The user can access the resources permitted by ACL 3000 after passing only identity authentication.

· The user can access network resources permitted by ACL 3001 after passing both identity authentication and security check.

# After the user passes identity authentication and security check, use the following command to display information about the portal user.

[Router] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 2.2.2.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: 3001

CAR: N/A

Configuring extended re-DHCP portal authentication

Network requirements

As shown in Figure 20, the host is directly connected to the router (the access device). The host obtains an IP address through the DHCP server. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure extended re-DHCP portal authentication. Before passing portal authentication, the host is assigned a private IP address. After passing portal identity authentication, the host obtains a public IP address and accepts security check. If the host fails the security check, it can access only subnet 192.168.0.0/24. After passing the security check, the host can access other network resources.

Figure 20 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 20 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· For re-DHCP portal authentication, configure a public address pool (20.20.20.0/24) and a private address pool (10.0.0.0/24) on the DHCP server. (Details not shown.)

· For re-DHCP portal authentication:

¡ The router must be configured as a DHCP relay agent.

¡ The portal-enabled interface must be configured with a primary IP address (a public IP address) and a secondary IP address (a private IP address).

For information about DHCP relay agent configuration, see Layer 3—IP Services Configuration Guide.

Configuration procedure

Perform the following tasks on the router.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.113

[Router-radius-rs1] primary accounting 192.168.0.113

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] key accounting simple radius

[Router-radius-rs1] user-name-format without-domain

# Enable RADIUS session control.

[Router] radius session-control enable

# Specify a session-control client with IP address 192.168.0.114 and shared key 12345 in plain text.

[Router] radius session-control client ip 192.168.0.114 key simple 12345

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

[Router] domain default enable dm1

3. Configure ACL 3000 as the isolation ACL and ACL 3001 as the security ACL.

[Router] acl advanced 3000

[Router-acl-ipv4-adv-3000] rule permit ip destination 192.168.0.0 0.0.0.255

[Router-acl-ipv4-adv-3000] rule deny ip

[Router-acl-ipv4-adv-3000] quit

[Router] acl advanced 3001

[Router-acl-ipv4-adv-3001] rule permit ip

[Router-acl-ipv4-adv-3001] quit

NOTE:

Make sure you specify ACL 3000 as the isolation ACL and ACL 3001 as the security ACL on the security policy server.

4. Configure DHCP relay and authorized ARP:

# Configure DHCP relay.

[Router] dhcp enable

[Router] dhcp relay client-information record

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] ip address 20.20.20.1 255.255.255.0

[Router–GigabitEthernet1/1/2] ip address 10.0.0.1 255.255.255.0 sub

[Router-GigabitEthernet1/1/2] dhcp select relay

[Router-GigabitEthernet1/1/2] dhcp relay server-address 192.168.0.112

# Enable authorized ARP.

[Router-GigabitEthernet1/1/2] arp authorized enable

[Router-GigabitEthernet1/1/2] quit

5. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable re-DHCP portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router-GigabitEthernet1/1/2] portal enable method redhcp

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 20.20.20.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Router] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Redhcp

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 20.20.20.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

· The user can access the resources permitted by ACL 3000 after passing only identity authentication.

· The user can access network resources permitted by ACL 3001 after passing both identity authentication and security check.

# After the user passes identity authentication and security check, use the following command to display information about the portal user.

[Router] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 20.20.20.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: 3001

CAR: N/A

Configuring extended cross-subnet portal authentication

Network requirements

As shown in Figure 21, Router A supports portal authentication. The host accesses Router A through Router B. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure Router A for extended cross-subnet portal authentication. Before passing portal authentication, the host can access only the portal server. After passing portal identity authentication, the host accepts security check. If the host fails the security check it can access only the subnet 192.168.0.0/24. After passing the security check, the host can access other network resources.

Figure 21 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 21 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· Make sure the IP address of the portal device added on the portal server is the IP address (20.20.20.1) of the router's interface connecting the host. The IP address group associated with the portal device is the subnet of the host (8.8.8.0/24).

Configuration procedure

Perform the following tasks on Router A.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<RouterA> system-view

[RouterA] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[RouterA-radius-rs1] primary authentication 192.168.0.112

[RouterA-radius-rs1] primary accounting 192.168.0.112

[RouterA-radius-rs1] key authentication simple radius

[RouterA-radius-rs1] key accounting simple radius

[RouterA-radius-rs1] user-name-format without-domain

# Enable RADIUS session control.

[RouterA] radius session-control enable

# Specify a session-control client with IP address 192.168.0.113 and shared key 12345 in plain text.

[RouterA] radius session-control client ip 192.168.0.113 key simple 12345

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[RouterA] domain dm1

# Configure AAA methods for the ISP domain.

[RouterA-isp-dm1] authentication portal radius-scheme rs1

[RouterA-isp-dm1] authorization portal radius-scheme rs1

[RouterA-isp-dm1] accounting portal radius-scheme rs1

[RouterA-isp-dm1] quit

[RouterA] domain default enable dm1

3. Configure ACL 3000 as the isolation ACL and ACL 3001 as the security ACL.

[RouterA] acl advanced 3000

[RouterA-acl-ipv4-adv-3000] rule permit ip destination 192.168.0.0 0.0.0.255

[RouterA-acl-ipv4-adv-3000] rule deny ip

[RouterA-acl-ipv4-adv-3000] quit

[RouterA] acl advanced 3001

[RouterA-acl-ipv4-adv-3001] rule permit ip

[RouterA-acl-ipv4-adv-3001] quit

NOTE:

Make sure you specify ACL 3000 as the isolation ACL and ACL 3001 as the security ACL on the security policy server.

4. Configure portal authentication:

# Configure a portal authentication server.

[RouterA] portal server newpt

[RouterA-portal-server-newpt] ip 192.168.0.111 key simple portal

[RouterA-portal-server-newpt] port 50100

[RouterA-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[RouterA-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[RouterA-portal-websvr-newpt] quit

# Enable cross-subnet portal authentication on GigabitEthernet 1/1/2.

[RouterA] interface gigabitethernet 1/1/2

[RouterA–GigabitEthernet1/1/2] portal enable method layer3

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[RouterA–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[RouterA–GigabitEthernet1/1/2] portal bas-ip 20.20.20.1

[RouterA–GigabitEthernet1/1/2] quit

On Router B, configure a default route to subnet 192.168.0.0/24, specifying the next hop address as 20.20.20.1. (Details not shown.)

Verifying the configuration

# Verify that the portal configuration has taken effect.

[RouterA] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet 1/1/2

NAS-ID profile: Not configured

Authorization : Strict checking

ACL : Disabled

User profile : Disabled

IPv4:

Portal status: Enabled

Authentication type: Layer3

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: 20.20.20.1

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

· The user can access the resources permitted by ACL 3000 after passing only identity authentication.

· The user can access network resources permitted by ACL 3001 after passing both identity authentication and security check.

# After the user passes identity authentication and security check, use the following command to display information about the portal user.

[RouterA] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: N/A

MAC IP VLAN Interface

0015-e9a6-7cfe 8.8.8.2 -- GigabitEthernet1/1/2

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: 3001

CAR: N/A

Configuring portal server detection and portal user synchronization

Network requirements

As shown in Figure 22, the host is directly connected to the router (the access device). The host is assigned a public IP address either manually or through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication on the router, so the host can access only the portal server before passing the authentication and access other network resources after passing the authentication.

Configure the router to do the following:

· Detect the reachability state of the portal authentication server.

· Send log messages upon state changes.

· Disable portal authentication when the authentication server is unreachable.

· Synchronize portal user information with the portal server periodically.

Figure 22 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 22 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· Configure the portal authentication server. Be sure to enable the server heartbeat function and the user heartbeat function.

· Configure the router (access device) as follows:

¡ Configure direct portal authentication on GigabitEthernet 1/1/2, the interface to which the host is connected.

¡ Configure portal authentication server detection, so that the router can detect the reachability of the portal authentication server by cooperating with the portal server heartbeat function.

¡ Configure portal user synchronization, so that the router can synchronize portal user information with the portal authentication server by cooperating with the portal user heartbeat function.

Configuring the portal authentication server on IMC PLAT 3.20

In this example, the portal server runs on IMC PLAT 3.20-R2602P13 and IMC UAM 3.60-E6301.

1. Configure the portal authentication server:

a. Log in to IMC and click the Service tab.

b. Select Access Service > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 23.

c. Configure the portal server heartbeat interval and user heartbeat interval.

d. Use the default settings for other parameters.

e. Click OK.

Figure 23 Portal authentication server configuration

2. Configure the IP address group:

a. Select Access Service > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.

b. Click Add to open the page as shown in Figure 24.

c. Enter the IP group name.

d. Enter the start IP address and end IP address of the IP group.

Make sure the host IP address (2.2.2.2) is in the IP group.

e. Select a service group.

This example uses the default group Ungrouped.

f. Select Normal from the Action list.

g. Click OK.

Figure 24 Adding an IP address group

3. Add a portal device:

a. Select Access Service > Portal Service Management > Device from the navigation tree to open the portal device configuration page.

b. Click Add to open the page as shown in Figure 25.

c. Enter the device name NAS.

d. Enter the IP address of the router's interface connected to the host.

e. Enter the key, which must be the same as that configured on the router.

f. Set whether to enable IP address reallocation.

This example uses direct portal authentication, and therefore select No from the Reallocate IP list.

g. Set whether to support the portal server heartbeat and user heartbeat functions.

In this example, select Yes for both Support Server Heartbeat and Support User Heartbeat.

h. Click OK.

Figure 25 Adding a portal device

4. Associate the portal device with the IP address group:

a. As shown in Figure 26, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.

Figure 26 Device list

b. Click Add to open the page as shown in Figure 27.

Figure 27 Port group configuration

c. Enter the port group name.

d. Select the configured IP address group.

The IP address used by the user to access the network must be within this IP address group.

e. User default values for other parameters.

f. Click OK.

5. Select Access Service > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the portal authentication server on IMC PLAT 5.0

In this example, the portal server runs on IMC PLAT 5.0(E0101) and IMC UAM 5.0(E0101).

1. Configure the portal authentication server:

a. Log in to IMC and click the Service tab.

b. Select User Access Manager > Portal Service Management > Server from the navigation tree to open the portal server configuration page as shown in Figure 28.

c. Configure the portal server heartbeat interval and user heartbeat interval.

d. Use the default settings for other parameters.

e. Click OK.

Figure 28 Portal authentication server configuration

2. Configure the IP address group:

a. Select User Access Manager > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.

b. Click Add to open the page as shown in Figure 29.

c. Enter the IP group name.

d. Enter the start IP address and end IP address of the IP group.

Make sure the host IP address is in the IP group.

e. Select a service group.

This example uses the default group Ungrouped.

f. Select Normal from the Action list.

g. Click OK.

Figure 29 Adding an IP address group

3. Add a portal device:

a. Select User Access Manager > Portal Service Management > Device from the navigation tree to open the portal device configuration page.

b. Click Add to open the page as shown in Figure 30.

c. Enter the device name NAS.

d. Enter the IP address of the router's interface connected to the host.

e. Enter the key, which must be the same as that configured on the router.

f. Set whether to enable IP address reallocation.

This example uses direct portal authentication, and therefore select No from the Reallocate IP list.

g. Select whether to support server heartbeat and user heartbeat functions.

In this example, select Yes for both Support Server Heartbeat and Support User Heartbeat.

h. Click OK.

Figure 30 Adding a portal device

4. Associate the portal device with the IP address group:

a. As shown in Figure 31, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.

b. Click Add to open the page as shown in Figure 32.

c. Enter the port group name.

d. Select the configured IP address group.

The IP address used by the user to access the network must be within this IP address group.

e. Use the default settings for other parameters.

f. Click OK.

Figure 31 Device list

Figure 32 Adding a port group

5. Select User Access Manager > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the router

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.112

[Router-radius-rs1] primary accounting 192.168.0.112

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] key accounting simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[Router-radius-rs1] user-name-format without-domain

[Router-radius-rs1] quit

# Enable RADIUS session control.

[Router] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

[Router] domain default enable dm1

3. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

# Configure reachability detection of the portal authentication server: set the server detection interval to 40 seconds, and send log messages upon reachability status changes.

[Router-portal-server-newpt] server-detect timeout 40 log

NOTE:

The value of timeout must be greater than or equal to the portal server heartbeat interval.

# Configure portal user synchronization with the portal authentication server, and set the synchronization detection interval to 600 seconds.

[Router-portal-server-newpt] user-sync timeout 600

[Router-portal-server-newpt] quit

NOTE:

The value of timeout must be greater than or equal to the portal user heartbeat interval.

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable direct portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method direct

# Enable portal fail-permit for the portal authentication server newpt.

[Router–GigabitEthernet1/1/2] portal fail-permit server newpt

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 2.2.2.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 2.2.2.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Use the following command to display information about the portal authentication server.

[Router] display portal server newpt

Portal server: newpt

Type : IMC

IP : 192.168.0.111

VPN instance : Not configured

Port : 50100

Server Detection : Timeout 40s Action: log

User synchronization : Timeout 600s

Status : Up

The Up status of the portal authentication server indicates that the portal authentication server is reachable. If the access device detects that the portal authentication server is unreachable, the Status field in the command output displays Down. The access device generates a server unreachable log "Portal server newpt turns down from up." and disables portal authentication on the access interface, so the host can access the external network without authentication.

Configuring cross-subnet portal authentication for MPLS L3VPNs

Network requirements

As shown in Figure 33, the PE device Router A provides portal authentication for the host in VPN 1. A portal server in VPN 3 acts as the portal authentication server, portal Web server, and RADIUS server.

Configure cross-subnet portal authentication on Router A, so the host can access network resources after passing identity authentication.

Figure 33 Network diagram

Configuration prerequisites

· Before enabling portal authentication, configure MPLS L3VPN and specify VPN targets for VPN 1 and VPN 3 so that VPN 1 and VPN 3 can communicate with each other. This example describes only the access authentication configuration on the user-side PE. For information about MPLS L3VPN configurations, see MPLS Configuration Guide.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

Configuration procedure

Perform the following tasks on Router A.

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<RouterA> system-view

[RouterA] radius scheme rs1

# For the RADIUS scheme, specify the VPN instance that is bound to the interface connected to the portal/RADIUS server. This example uses VPN instance vpn3.

[RouterA-radius-rs1] vpn-instance vpn3

NOTE:

For the VPN instance information, see the MPLS L3VPN configuration on Router A.

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[RouterA-radius-rs1] primary authentication 192.168.0.111

[RouterA-radius-rs1] primary accounting 192.168.0.111

[RouterA-radius-rs1] key accounting simple radius

[RouterA-radius-rs1] key authentication simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[RouterA-radius-rs1] user-name-format without-domain

# Specify the source IP address for RADIUS packets to be sent as 3.3.0.3. This address must be the same as that of the portal device specified on the portal authentication server to avoid authentication failures.

[RouterA-radius-rs1] nas-ip 3.3.0.3

[RouterA-radius-rs1] quit

# Enable RADIUS session control.

[RouterA] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[RouterA] domain dm1

# Configure AAA methods for the ISP domain.

[RouterA-isp-dm1] authentication portal radius-scheme rs1

[RouterA-isp-dm1] authorization portal radius-scheme rs1

[RouterA-isp-dm1] accounting portal radius-scheme rs1

[RouterA-isp-dm1] quit

[RouterA] domain default enable dm1

3. Configure portal authentication:

# Configure a portal authentication server.

[RouterA] portal server newpt

[RouterA-portal-server-newpt] ip 192.168.0.111 vpn-instance vpn3 key simple portal

[RouterA-portal-server-newpt] port 50100

[RouterA-portal-server-newpt] quit

# Configure a portal Web server.

[RouterA] portal web-server newpt

[RouterA-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[RouterA-portal-websvr-newpt] vpn-instance vpn3

[RouterA-portal-websvr-newpt] quit

# Enable cross-subnet portal authentication on GigabitEthernet 1/1/1.

[RouterA] interface gigabitethernet 1/1/1

[RouterA–GigabitEthernet1/1/1] portal enable method layer3

# Reference the portal Web server newpt on GigabitEthernet 1/1/1.

[RouterA–GigabitEthernet1/1/1] portal apply web-server newpt

# Configure the BAS-IP as 3.3.0.3 for portal packets sent from GigabitEthernet 1/1/1 to the portal authentication server.

[RouterA–GigabitEthernet1/1/1] portal bas-ip 3.3.0.3

[RouterA–GigabitEthernet1/1/1] quit

Verifying the configuration

# Verify the portal configuration by executing the display portal interface command. (Details not shown.)

# After the user passes authentication, execute the display portal user command to display the portal user information.

[RouterA] display portal user all

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: vpn3

MAC IP VLAN Interface

0000-0000-0000 3.3.0.1 -- GigabitEthernet1/1/1

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL: N/A

CAR: N/A

Configuring direct portal authentication with a preauthentication domain

Network requirements

As shown in Figure 34, the host is directly connected to the router (the access device). The host is assigned a public IP address through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication, so the host can access only subnet 192.168.0.0/24 before passing the authentication and access other network resources after passing the authentication.

Figure 34 Network diagram

Configuration prerequisites

· Configure IP addresses for the host, router, and servers as shown in Figure 34 and make sure they can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

Configuration procedure

Perform the following tasks on the router.

1. Configure a preauthentication IP address pool:

# Configure DHCP address pool pre to assign IP addresses and other configuration parameters to clients on subnet 2.2.2.0/24.

<Router> system-view

[Router] dhcp server ip-pool pre

[Router-dhcp-pool-pre] gateway-list 2.2.2.1

[Router-dhcp-pool-pre] network 2.2.2.0 24

[Router-dhcp-pool-pre] quit

# Enable the DHCP server on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] dhcp select server

[Router–GigabitEthernet1/1/2] quit

2. Configure a preauthentication domain:

# Create an ISP domain named abc and enter its view.

[Router] domain abc

# Specify authorization ACL 3010 in the domain.

[Router-isp-abc] authorization-attribute acl 3010

[Router-isp-abc] quit

# Configure a rule to permit access to the subnet 192.168.0.0/24.

[Router] acl advanced 3010

[Router-acl-ipv4-adv-3010] rule 1 permit ip destination 192.168.0.0 24

[Router-acl-ipv4-adv-3010] quit

# Configure preauthentication domain abc on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal pre-auth domain abc

[Router–GigabitEthernet1/1/2] quit

3. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable direct portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method direct

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 2.2.2.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 2.2.2.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify the portal configuration by executing the display portal interface command. (Details not shown.)

# Display information about preauthentication portal users.

[Router] display portal user pre-auth interface gigabitethernet 1/1/2

MAC IP VLAN Interface

0015-e9a6-7cfe 2.2.2.4 -- GigabitEthernet1/1/2

State: Online

VPN instance: --

Authorization information:

DHCP IP pool: N/A

User profile: N/A

ACL number: 3010

Inbound CAR: N/A

Outbound CAR: N/A

Configuring re-DHCP portal authentication with a preauthentication domain

Network requirements

As shown in Figure 35, the host is directly connected to the router (the access device). The host obtains an IP address through the DHCP server. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure re-DHCP portal authentication. Before passing the authentication, the host is assigned a private IP address and can access only the subnet 192.168.0.0/24. After passing the authentication, the host gets a public IP address and can access other network resources.

Figure 35 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the router and servers as shown in Figure 35 and make sure the host, router, and servers can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· For re-DHCP portal authentication, configure a public address pool (20.20.20.0/24) and a private address pool (10.0.0.0/24) on the DHCP server. (Details not shown.)

· For re-DHCP portal authentication:

¡ The router must be configured as a DHCP relay agent.

¡ The portal-enabled interface must be configured with a primary IP address (a public IP address) and a secondary IP address (a private IP address).

For information about DHCP relay agent configuration, see Layer 3—IP Services Configuration Guide.

· If you have configured a preauthentication IP address pool on portal-enabled interfaces, configure a DHCP relay address pool with the same name on the device. For the DHCP relay address pool, specify the subnet address where the unauthenticated users reside (with the export-router keyword specified) and the DHCP server address.

Configuration procedure

Perform the following tasks on the router.

1. Configure a preauthentication domain:

# Create an ISP domain named abc and enter its view.

<Router> system-view

[Router] domain abc

# Specify authorization ACL 3010 in the domain.

[Router-isp-abc] authorization-attribute acl 3010

[Router-isp-abc] quit

# Configure a rule to permit access to the subnet 192.168.0.0/24.

[Router] acl advanced 3010

[Router-acl-ipv4-adv-3010] rule 1 permit ip destination 192.168.0.0 24

[Router-acl-ipv4-adv-3010] quit

# Configure preauthentication domain abc on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal pre-auth domain abc

[Router–GigabitEthernet1/1/2] quit

2. Configure DHCP relay and authorized ARP.

# Configure DHCP relay.

[Router] dhcp enable

[Router] dhcp relay client-information record

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] ip address 20.20.20.1 255.255.255.0

[Router–GigabitEthernet1/1/2] ip address 10.0.0.1 255.255.255.0 sub

[Router-GigabitEthernet1/1/2] dhcp select relay

[Router-GigabitEthernet1/1/2] dhcp relay server-address 192.168.0.112

# Enable authorized ARP.

[Router-GigabitEthernet1/1/2] arp authorized enable

[Router-GigabitEthernet1/1/2] quit

3. Configure portal authentication:

# Configure a portal authentication server.

[Router] portal server newpt

[Router-portal-server-newpt] ip 192.168.0.111 key simple portal

[Router-portal-server-newpt] port 50100

[Router-portal-server-newpt] quit

# Configure a portal Web server.

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://192.168.0.111:8080/portal

[Router-portal-websvr-newpt] quit

# Enable re-DHCP portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method redhcp

# Reference the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

# Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/1/2 to the portal authentication server.

[Router–GigabitEthernet1/1/2] portal bas-ip 20.20.20.1

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify the portal configuration by executing the display portal interface command. (Details not shown.)

# Display information about preauthentication portal users.

[Router] display portal user pre-auth interface gigabitethernet 1/1/2

MAC IP VLAN Interface

0015-e9a6-7cfe 10.10.10.4 -- GigabitEthernet1/1/2

State: Online

VPN instance: --

DHCP IP pool: N/A

User profile: N/A

ACL number: 3010

Inbound CAR: N/A

Outbound CAR: N/A

Configuring direct portal authentication using the local portal Web server

Network requirements

As shown in Figure 36, the host is directly connected to the router (the access device). The host is assigned a public IP address either manually or through DHCP. The router acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication on the router. Before a user passes portal authentication, the user can access only the local portal Web server. After passing portal authentication, the user can access other network resources.

Figure 36 Network diagram

Configuration prerequisites and guidelines

· Configure IP addresses for the host, router, and server as shown in Figure 36 and make sure they can reach each other.

· Configure the RADIUS server correctly to provide authentication and accounting functions.

· Customize the authentication pages, compress them to a file, and upload the file to the root directory of the storage medium of the router.

Configuration procedure

1. Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Router> system-view

[Router] radius scheme rs1

# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

[Router-radius-rs1] primary authentication 192.168.0.112

[Router-radius-rs1] primary accounting 192.168.0.112

[Router-radius-rs1] key authentication simple radius

[Router-radius-rs1] key accounting simple radius

# Exclude the ISP domain name from the username sent to the RADIUS server.

[Router-radius-rs1] user-name-format without-domain

[Router-radius-rs1] quit

# Enable RADIUS session control.

[Router] radius session-control enable

2. Configure an authentication domain:

# Create an ISP domain named dm1 and enter its view.

[Router] domain dm1

# Configure AAA methods for the ISP domain.

[Router-isp-dm1] authentication portal radius-scheme rs1

[Router-isp-dm1] authorization portal radius-scheme rs1

[Router-isp-dm1] accounting portal radius-scheme rs1

[Router-isp-dm1] quit

[Router] domain default enable dm1

3. Configure portal authentication:

# Create a local portal Web server. Use HTTP to exchange authentication information with clients.

[Router] portal local-web-server http

# Specify file abc.zip as the default authentication page file for local portal authentication. (Make sure the file exist under the root directory of the router.)

[Router–portal-local-websvr-http] default-logon-page abc.zip

# Set the HTTP service listening port number to 2331 for the local portal Web server.

[Router–portal-local-webserver-http] tcp-port 2331

[Router–portal-local-websvr-http] quit

# Configure the portal Web server name as newpt and URL as the IP address of the portal authentication-enabled interface or a loopback interface (except 127.0.0.1).

[Router] portal web-server newpt

[Router-portal-websvr-newpt] url http://2.2.2.1:2331/portal

[Router-portal-websvr-newpt] quit

# Enable direct portal authentication on GigabitEthernet 1/1/2.

[Router] interface gigabitethernet 1/1/2

[Router–GigabitEthernet1/1/2] portal enable method direct

# Specify the portal Web server newpt on GigabitEthernet 1/1/2.

[Router–GigabitEthernet1/1/2] portal apply web-server newpt

[Router–GigabitEthernet1/1/2] quit

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Router] display portal interface gigabitethernet 1/1/2

Portal information of GigabitEthernet1/1/2

Authorization Strict checking

ACL Disabled

User profile Disabled

IPv4:

Portal status: Enabled

Authentication type: Direct

Portal Web server: newpt(active)

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ip: Not configured

User Detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Mask

Destination authenticate subnet:

IP address Mask

IPv6:

Portal status: Disabled

Authentication type: Disabled

Portal Web server: Not configured

Secondary portal Web server: Not configured

Authentication domain: Not configured

Pre-auth domain: Not configured

User-dhcp-only: Disabled

Pre-auth IP pool: Not configured

Max portal users: Not configured

Bas-ipv6: Not configured

User detection: Not configured

Action for server detection:

Server type Server name Action

-- -- --

Layer3 source network:

IP address Prefix length

Destination authenticate subnet:

IP address Prefix length

A user can perform portal authentication through a Web page. Before passing the authentication, the user can access only the authentication page http://2.2.2.1:2331/portal and all Web requests will be redirected to the authentication page. After passing the authentication, the user can access other network resources.

# After the user passes authentication, use the following command to display information about the portal user.

[Router] display portal user interface gigabitethernet 1/1/2

Total portal users: 1

Username: abc

Portal server: newpt

State: Online

VPN instance: --

MAC IP VLAN Interface

0015-e9a6-7cfe 2.2.2.2 -- GigabitEthernet1/1/2

Authorization information:

IP pool: N/A

User profile: N/A

ACL: N/A

CAR: N/A

Troubleshooting portal

No portal authentication page is pushed for users

Symptom

When a user is redirected to the IMC portal authentication server, no portal authentication page or error message is prompted for the user. The login page is blank.

Analysis

The key configured on the portal access device and that configured on the portal authentication server are inconsistent. As a result, packet verification fails, and the portal authentication server refuses to push the authentication page.

Solution

Use the display portal server command on the access device to check whether a key is configured for the portal authentication server.

· If no key is configured, configure the right key.

· If a key is configured, use the ip or ipv6 command in the portal authentication server view to correct the key, or correct the key configured for the access device on the portal authentication server.

Cannot log out portal users on the access device

Symptom

You cannot use the portal delete-user command on the access device to log out a portal user, but the portal user can log out by clicking the Disconnect button on the portal authentication client.

Analysis

When you execute the portal delete-user command on the access device to log out a user, the access device sends an unsolicited logout notification message to the portal authentication server. The destination port number in the logout notification is the listening port number of the portal authentication server configured on the access device. If this listening port number is not the actual listening port number configured on the server, the server cannot receive the notification. As a result, the server does not log out the user.

When a user uses the Disconnect button on the authentication client to log out, the portal authentication server sends an unsolicited logout request message to the access device. The access device uses the source port in the logout request as the destination port in the logout ACK message. As a result, the portal authentication server can definitely receive the logout ACK message and log out the user.

Solution

1. Use the display portal server command to display the listening port of the portal authentication server configured on the access device.

2. Use the portal server command in system view to change the listening port number to the actual listening port of the portal authentication server.

Cannot log out portal users on the RADIUS server

Symptom

The access device uses the H3C IMC server as the RADIUS server to perform identity authentication for portal users. You cannot log out the portal users on the RADIUS server.

Analysis

The H3C IMC server uses session control packets to send disconnection requests to the access device. On the access device, the listening UDP port for session control packets is disabled by default. Therefore, the access device cannot receive the portal user logout requests from the RADIUS server.

Solution

On the access device, execute the radius session-control enable command in system view to enable the RADIUS session control function.

Users logged out by the access device still exist on the portal authentication server

Symptom

After you log out a portal user on the access device, the user still exists on the portal authentication server.

Analysis

When you execute the portal delete-user command on the access device to log out a user, the access device sends an unsolicited logout notification to the portal authentication server. If the BAS-IP or BAS-IPv6 address carried in the logout notification is different from the portal device IP address specified on the portal authentication server, the portal authentication server discards the logout notification. When sending of the logout notifications times out, the access device logs out the user. However, the portal authentication server does not receive the logout notification successfully, and therefore it regards the user is still online.

Solution

Configure the BAS-IP or BAS-IPv6 attribute on the interface enabled with portal authentication. Make sure the attribute value is the same as the portal device IP address specified on the portal authentication server.

Re-DHCP portal authenticated users cannot log in successfully

Symptom

The device performs re-DHCP portal authentication for users. A user enters the correct username and password, and the client successfully obtains the private and public IP addresses. However, the authentication result for the user is failure.

Analysis

When the access device detects that the client IP address is changed, it sends an unsolicited portal packet to notify of the IP change to the portal authentication server. The portal authentication server notifies of the authentication success only after it receives the IP change notification from both the access device and the client.

If the BAS-IP or BAS-IPv6 address carried in the portal notification packet is different from the portal device IP address specified on the portal authentication server, the portal authentication server discards the portal notification packet. As a result, the portal authentication server considers that the user has failed the authentication.

11-Security Configuration Guide

Configuring portal authentication

Authentication client

Access device

Portal authentication server

Portal Web server

AAA server

Security policy server

Client and local portal Web server interaction protocols

Portal authentication modes

Direct authentication

Re-DHCP authentication

Cross-subnet authentication

Portal support for EAP

Direct authentication/cross-subnet authentication process (with CHAP/PAP authentication)

Re-DHCP authentication process (with CHAP/PAP authentication)

Portal filtering rules

Configuration prerequisites

Configuring a portal Web server

Configuring a portal-free rule

Configuring an authentication source subnet

Specifying a portal authentication domain

Configuring portal detection features

Configuring online detection of portal users

Configuring the portal fail-permit feature

Specifying a format for the NAS-Port-Id attribute

Disabling traffic accounting for portal users

Configuring Web redirect

Configuring the local portal Web server feature

Customizing authentication pages

File name rules

Page request rules

Post request attribute rules

Page file compression and saving rules

Editing a third-party authentication button on the logon page

Editing a third-party authentication page

Configuring a third-party authentication server

Configuring the QQ authentication server

Configuring the email authentication server

Network requirements

Configuration prerequisites

Configuring the portal authentication server on IMC PLAT 3.20

Configuring the portal authentication server on IMC PLAT 5.0

Configuring the router

Verifying the configuration

Configuring re-DHCP portal authentication

Network requirements

Configuration prerequisites and guidelines

Configuration procedure

Verifying the configuration

Configuring cross-subnet portal authentication

Network requirements

Configuration prerequisites and guidelines

Configuration procedure

Verifying the configuration

Network requirements

Configuration prerequisites

Configuration procedure

Verifying the configuration

Configuring extended re-DHCP portal authentication

Network requirements

Configuration prerequisites and guidelines

Configuration procedure

Verifying the configuration

Configuring extended cross-subnet portal authentication

Network requirements

Configuration prerequisites and guidelines

Configuration procedure

Verifying the configuration

Network requirements

Configuration prerequisites and guidelines

Configuring the portal authentication server on IMC PLAT 3.20

Configuring the portal authentication server on IMC PLAT 5.0

Configuring the router

Verifying the configuration

Network requirements

Configuration prerequisites

Configuration procedure

Verifying the configuration

Network requirements