The host accesses Switch A through Switch B.
•
•
A RADIUS server serves as the authentication/accounting server.
Figure 52 Network diagram
Configuration procedure
When configuring cross-subnet portal authentication, follow these guidelines:
•
Configure IP addresses for the host, switches, and servers as shown in
can reach each other.
Configure the RADIUS server properly to provide authentication and accounting functions for users.
•
Make sure the IP address of the portal device added on the portal server is the IP address of the
•
interface connecting users (20.20.20.1 in this example), and the IP address group associated with
the portal device is the network segment where the users reside (8.8.8.0/24 in this example).
Perform the following configuration to configure cross-subnet portal authentication on Switch A:
1.
Configure a RADIUS scheme:
# Create a RADIUS scheme named rs1 and enter its view.
<SwitchA> system-view
[SwitchA] radius scheme rs1
# Set the server type for the RADIUS scheme. When using the IMC server, set it to extended.
[SwitchA-radius-rs1] server-type extended
# Specify the primary authentication server and primary accounting server, and configure the keys
for communication with the servers.
[SwitchA-radius-rs1] primary authentication 192.168.0.112
[SwitchA-radius-rs1] primary accounting 192.168.0.112
[SwitchA-radius-rs1] key authentication simple radius
[SwitchA-radius-rs1] key accounting simple radius
# Specify that the ISP domain name should not be included in the username sent to the RADIUS
server.
[SwitchA-radius-rs1] user-name-format without-domain
[SwitchA-radius-rs1] quit
Configure an authentication domain:
2.
# Create an ISP domain named dm1 and enter its view.
[SwitchA] domain dm1
# Configure AAA methods for the ISP domain.
[SwitchA-isp-dm1] authentication portal radius-scheme rs1
161
Figure 52
and make sure they