HP VPN Firewall Appliances Access Control Configuration Guide

170
Figure 122 Network diagram
Configuration prerequisites and guidelines
• Configure IP addresses for the firewall and servers as shown in Figure 122 and make sure the host,
firewall, and servers can reach each other.
• Configure the RADIUS server correctly to provide authentication and accounting functions for users.
• For re-DHCP portal authentication, configure a public address pool (20.20.20.0/24, in this
example) and a private address pool (10.0.0.0/24, in this example) on the DHCP server. (Details
not shown.)
• For re-DHCP portal authentication, the firewall must be configured as a DHCP relay agent and 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 Network Management Configuration Guide.
• Make sure the IP address of the portal device added on the portal server is the public IP address of
the interface connecting users (20.20.20.1 in this example), the private IP address range for the IP
address group associated with the portal device is the private network segment where the users
reside (10.0.0.0/24 in this example), and the public IP address range for the IP address group is
the public network segment 20.20.20.0/24.
Configuration procedure
1. Configure a RADIUS scheme:
# Create a RADIUS scheme named rs1, and enter its view.
<Firewall> system-view
[Firewall] radius scheme rs1
# Set the server type for the RADIUS scheme. When using the IMC server, set the server type to
extended.
[Firewall-radius-rs1] server-type extended
# Specify the primary authentication server and primary accounting server, and configure the keys
for communication with the servers.
[Firewall-radius-rs1] primary authentication 192.168.0.113
[Firewall-radius-rs1] primary accounting 192.168.0.113
[Firewall-radius-rs1] key authentication radius
[Firewall-radius-rs1] key accounting radius