139
To configure an authentication source subnet:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Configure an authentication
source subnet.
portal auth-network
{
ipv4-network-address
{
mask-length
|
mask
} |
ipv6
ipv6-network-address
prefix
-length
}
Optional.
By default, the source IPv4 subnet
is 0.0.0.0/0, and the source IPv6
subnet is ::/0, meaning that users
from any IPv4 or IPv6 subnet must
pass portal authentication to
access network resources.
You can configure multiple
authentication source subnets by
executing the
portal auth-network
command repeatedly.
NOTE:
Configuration of authentication source subnets applies to only cross-subnet authentication. In direct
authentication mode, the authentication source subnet is 0.0.0.0/0. In re-DHCP authentication mode, the
authentication source subnet of an interface is the subnet to which the private IP address of the interface
belongs.
Setting the maximum number of online portal users
You can use this feature to control the total number of online portal users in the system.
If the maximum number of online portal users to be set is less than that of the current online portal users,
the limit can be set successfully and does not impact the online portal users, but the system does not allow
new portal users to log on until the number drops down below the limit.
To set the maximum number of online portal users allowed in the system:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Set the maximum number of
online portal users.
portal
max-user
max-number
3000 by default.
NOTE:
The maximum number of online portal users the switch actually assigns depends on the ACL resources on
the switch.
Specifying an authentication domain for portal users
After you specify an authentication domain for portal users on an interface, the device uses the
authentication domain for authentication, authorization, and accounting (AAA) of all portal users on the
interface, ignoring the domain names carried in the usernames. This allows you to specify different
authentication domains for different interfaces as needed.