Configuring extended cross-subnet portal authentication

Network requirements

As shown in Figure 71, Router A supports portal authentication. The host accesses Router A through Router B. 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 Router A for extended cross-subnet portal authentication. Before passing portal authentication, the host can access only the portal server. After passing portal identity authentication, the host accepts security check. If the host fails the security check it can access only the subnet 192.168.0.0/24. After passing the security check, the host can access other network resources.

Figure 64: Network diagram

Configuration prerequisites and guidelines

Configuration procedure

Perform the following tasks on Router A.

  1. Configure a RADIUS scheme:

    # Create a RADIUS scheme named rs1 and enter its view.

    <RouterA> system-view
    [RouterA] radius scheme rs1
    

    # Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

    [RouterA-radius-rs1] primary authentication 192.168.0.112
    [RouterA-radius-rs1] primary accounting 192.168.0.112
    [RouterA-radius-rs1] key authentication simple radius
    [RouterA-radius-rs1] key accounting simple radius
    [RouterA-radius-rs1] user-name-format without-domain
    

    # Enable RADIUS session control.

    [RouterA] radius session-control enable
    

    # Specify a session-control client with IP address 192.168.0.113 and shared key 12345 in plain text.

    [RouterA] radius session-control client ip 192.168.0.113 key simple 12345
    
  2. Configure an authentication domain:

    # Create an ISP domain named dm1 and enter its view.

    [RouterA] domain dm1
    

    # Configure AAA methods for the ISP domain.

    [RouterA-isp-dm1] authentication portal radius-scheme rs1
    [RouterA-isp-dm1] authorization portal radius-scheme rs1
    [RouterA-isp-dm1] accounting portal radius-scheme rs1
    [RouterA-isp-dm1] quit
    

    # Configure domain dm1 as the default ISP domain. If a user enters the username without the ISP domain name at login, the authentication and accounting methods of the default domain are used for the user.

    [RouterA] domain default enable dm1
    
  3. Configure ACL 3000 as the isolation ACL and ACL 3001 as the security ACL.

    [RouterA] acl advanced 3000
    [RouterA-acl-ipv4-adv-3000] rule permit ip destination 192.168.0.0 0.0.0.255
    [RouterA-acl-ipv4-adv-3000] rule deny ip
    [RouterA-acl-ipv4-adv-3000] quit
    [RouterA] acl advanced 3001
    [RouterA-acl-ipv4-adv-3001] rule permit ip
    [RouterA-acl-ipv4-adv-3001] quit
    

    [NOTE: ]

    NOTE:

    Make sure you specify ACL 3000 as the isolation ACL and ACL 3001 as the security ACL on the security policy server.


  4. Configure portal authentication:

    # Configure a portal authentication server.

    [RouterA] portal server newpt
    [RouterA-portal-server-newpt] ip 192.168.0.111 key simple portal
    [RouterA-portal-server-newpt] port 50100
    [RouterA-portal-server-newpt] quit
    

    # Configure a portal Web server.

    [Router] portal web-server newpt
    [RouterA-portal-websvr-newpt] url http://192.168.0.111:8080/portal
    [RouterA-portal-websvr-newpt] quit
    

    # Enable cross-subnet portal authentication on GigabitEthernet 1/0/2.

    [RouterA] interface gigabitethernet 1/0/2
    [RouterA–GigabitEthernet1/0/2] portal enable method layer3
    

    # Reference the portal Web server newpt on GigabitEthernet 1/0/2.

    [RouterA–GigabitEthernet1/0/2] portal apply web-server newpt
    

    # Configure the BAS-IP as 20.20.20.1 for portal packets sent from GigabitEthernet 1/0/2 to the portal authentication server.

    [RouterA–GigabitEthernet1/0/2] portal bas-ip 20.20.20.1
    [RouterA–GigabitEthernet1/0/2] quit
    

On Router B, configure a default route to subnet 192.168.0.0/24, specifying the next hop address as 20.20.20.1. (Details not shown.)

Verifying the configuration

# Verify that the portal configuration has taken effect.

[RouterA] display portal interface gigabitethernet 1/0/2
 Portal information of GigabitEthernet 1/0/2
     NAS-ID profile: Not configured
     VSRP instance : Not configured
     VSRP state    : N/A
     Authorization : Strict checking 
     ACL           : Disabled
     User profile  : Disabled
 IPv4:
     Portal status: Enabled
     Authentication type: Layer3
     Portal Web server: newpt(active)
     Secondary portal Web server: Not configured
     Authentication domain: Not configured
     Pre-auth domain: Not configured
     User-dhcp-only: Disabled
     Pre-auth IP pool: Not configured
     Max portal users: Not configured
     Bas-ip: 20.20.20.1
     User detection:  Not configured
     Action for server detection:
         Server type    Server name                        Action 
         --             --                                 -- 
     Layer3 source network:
         IP address               Mask

     Destination authenticate subnet:
         IP address               Mask
IPv6:
     Portal status: Disabled
     Authentication type: Disabled
     Portal Web server: Not configured
     Secondary portal Web server: Not configured
     Authentication domain: Not configured
     Pre-auth domain: Not configured
     User-dhcp-only: Disabled
     Pre-auth IP pool: Not configured
     Max portal users: Not configured
     Bas-ipv6: Not configured
     User detection: Not configured
     Action for server detection:
         Server type    Server name                        Action
         --             --                                 --
     Layer3 source network:
         IP address                                        Prefix length

     Destination authenticate subnet: 
         IP address                                        Prefix length 

Before passing portal authentication, a user that uses the HPE iNode client can access only the authentication page http://192.168.0.111:8080/portal. All Web requests from the user are redirected to the authentication page.

# After the user passes identity authentication and security check, use the following command to display information about the portal user.

[RouterA] display portal user interface gigabitethernet 1/0/2
Total portal users: 1
Username: abc
  Portal server: newpt
  State: Online
  VPN instance: N/A
  MAC                IP                 VLAN   Interface
  0015-e9a6-7cfe     8.8.8.2            --     GigabitEthernet1/0/2
  Authorization information:
    DHCP IP pool: N/A
    User profile: N/A
    ACL: 3001
    CAR: N/A