This section provides an example for configuring RADIUS server authentication on Internet access users when a FW works as an egress gateway.
An enterprise has deployed a FW as the egress gateway to connect the intranet to the Internet, as shown in Figure 1. Details are as follows:
The user management and authentication mechanisms of the FW must identify IP addresses on the intranet as users to implement user-specific behavior control and permission assignment. Requirements are as follows:
This example describes only how to configure user management and authentication.
Item |
Data |
Description |
|---|---|---|
R&D employee |
Group User |
Add the R&D employee to group research. You can repeat the operations in this example to configure multiple user accounts. |
Marketing employee |
Group User |
Add the marketing employee to group marketing. You can repeat the operations in this example to configure multiple user accounts. |
Parent group of new users |
After being authenticated, the users go online as temporary users and use the rights of the specified user group. |
|
RADIUS server |
On the FW, set the parameters for communicating with a RADIUS server. The parameters on the FW must be consistent with those on the RADIUS server. |
|
Authentication domain |
The net1 authentication domain is used during authentication. |
|
Authentication policy |
The R&D employee and marketing employee can access network resources only after being authenticated by a FW. |
The following example describes how to configure interface GigabitEthernet 0/0/3. You can configure other interfaces based on the networking diagram.
Zone |
trust |
|---|---|
IP Address |
10.3.0.1/24 |


>Click Detect. In the dialog box that is displayed, click OK and enter the user name and password that are configured on the RADIUS server. Click Start Checking to check the connectivity to the RADIUS server.
The parameters on the FW must be consistent with those on the RADIUS server.
In this example, because the user name on the RADIUS server contains @, Include Authentication Domain must be selected so that the user name sent by the FW to the RADIUS server contains the name of the authentication domain.
Name |
auth_policy_service |
|---|---|
Source Zone |
trust |
Source Address/Region |
10.3.0.0/24 |
Action |
Portal authentication |
Portal Authentication Template |
Disable |

The authentication domain must be the same as the string following the at sign (@) in the user name on the RADIUS server.
The user groups and users in the net1 authentication domain are imported through the CSV file on the previous step. The newuser user group accommodates new users.

# sysname FW # radius-server template auth_server_radius radius-server shared-key cipher %$%$73pu<+^]XV9mn=*qd}_,r3*!%$%$ radius-server authentication 10.2.0.50 1645 radius-server user-name domain-included # interface GigabitEthernet0/0/1 ip address 1.1.1.1 255.255.255.0 # interface GigabitEthernet0/0/2 ip address 10.2.0.1 255.255.255.0 # interface GigabitEthernet0/0/3 ip address 10.3.0.1 255.255.255.0 # firewall zone trust add interface GigabitEthernet0/0/3 # firewall zone untrust add interface GigabitEthernet0/0/1 # firewall zone dmz add interface GigabitEthernet0/0/2 # aaa authentication-scheme radius authentication-mode radius # domain net1 authentication-scheme radius radius-server auth_server_radius service-type internetaccess internet-access mode password new-user add-temporary group /net1/newuser # auth-policy rule name auth_policy_service source-zone trust source-address 10.3.0.0 24 action auth # security-policy rule name policy_local_01 source-zone trust destination-zone local source-address 10.3.0.0 24 service protocol tcp destination-port 8887 action permit rule name policy_local_02 source-zone local destination-zone dmz destination-address 10.2.0.50 32 action permit rule name policy_sec_02 source-zone trust source-address 10.3.0.0 24 destination-zone untrust action permit rule name policy_sec_03 source-zone trust source-address 10.3.0.0 24 destination-zone dmz action permit # The following configuration is used to perform a one-time operation and not stored in the configuration profile. user-manage user-import demo.csv auto-create-group override user-manage group /default/newuser test-aaa testname testpassword radius-template auth_server_radius