Example: Configuring Portal Server Detection And Portal User Synchronization - H3C SR8800-F Configuration Manual

Server type
--
Layer3 source network:
IP address
Destination authenticate subnet:
IP address
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 are
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.
[RouterA] display portal user interface gigabitethernet 1/0/2
Total portal users: 1
Username: abc
Portal server: newpt
State: Online
VPN instance: N/A
MAC
0015-e9a6-7cfe
Authorization information:
DHCP IP pool: N/A
User profile: N/A
Session group profile: N/A
ACL: 3001
Inbound CAR: N/A
Outbound CAR: N/A
Inbound priority: N/A
Outbound priority: N/A
Example: Configuring portal server detection and portal user
synchronization
Network configuration
As shown in
assigned a public IP address either manually or through DHCP. A portal server acts as both a portal
authentication
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.
Server name
--
IP
8.8.8.2
Figure 115, the host is directly connected to the router (the access device). The host is
server and a
VLAN Interface
-- GigabitEthernet1/0/2
portal Web server.
356
Action
--
Prefix length
Prefix length
A RADIUS server acts as the