DHCP IP pool: N/A
Session group profile: N/A
ACL: N/A
CAR: N/A
Configuring re-DHCP portal authentication
Network requirements
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. After passing the authentication, the host gets a public IP address and can
access Internet resources.
Figure 62 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).
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.
Figure
62, the host is directly connected to the router (the access device). The host
GE2/0/2
20.20.20.1/24
GE2/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
167
Figure 62
and make sure the