Example: Configuring Re-Dhcp Portal Authentication With A Preauthentication Policy - H3C SR8800-F Configuration Manual

State: Online
VPN instance: N/A
Authorization information:
DHCP IP pool: N/A
User profile: N/A
Session group profile: N/A
ACL: 3010
Inbound CAR: N/A
Outbound CAR: N/A
Inbound priority: N/A
Outbound priority: N/A
Example: Configuring re-DHCP portal authentication with a
preauthentication policy
Network configuration
As shown in
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 128 Network diagram
Host
Automatically obtains
an IP address
Configuration prerequisites and guidelines
•
Configure IP addresses for the router and servers as shown in
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).
Figure 128, the host is directly connected to the router (the access device). The host
GE1/0/2
20.20.20.1/24 GE1/0/1
10.0.0.1/24 sub 192.168.0.100/24
Router
Portal server
192.168.0.111/24
DHCP server
192.168.0.112/24
RADIUS server
192.168.0.113/24
368
Figure 128 and make sure the