167
[Switch-Vlan-interface100] dhcp relay server-select 0
[Switch-Vlan-interface100] dhcp relay address-check enable
# Enable re-DHCP portal authentication on the interface connecting the host.
[Switch–Vlan-interface100] portal server newpt method redhcp
[Switch–Vlan-interface100] quit
Configuring cross-subnet portal authentication with extended
functions
Network requirements
As shown in Figure 55:
• Switch A is configured for cross-subnet extended portal authentication. If the host fails security check
after passing identity authentication, the host can access only subnet 192.168.0.0/24. After
passing security check, the host can access Internet resources.
• The host accesses Switch A through Switch B.
• A RADIUS server serves as the authentication/accounting server.
Figure 55 Network diagram
Configuration procedure
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).
Configure IP addresses for the host, switches, and servers as shown in Figure 55 and mak
e sure that they
can reach each other.
Configure the RADIUS server properly to provide authentication and accounting functions for users.
Configure Switch A:
1. Configure a RADIUS scheme:
# Create a RADIUS scheme named rs1 and enter its view.
<SwitchA> system-view
[SwitchA] radius scheme rs1
To Next Page
Loading...
Need help?
General