153
{
If the client is configured to obtain an IP address automatically through DHCP, the user
obtains an address from the specified IP address pool.
{
If the client is configured with a static IP address, the user uses the static IP address.
However, if the interface does not have an IP address, users using static IP addresses
cannot pass authentication.
•
If the interface has an IP address but no preauthentication IP pool specified, the user uses the
static IP address or the IP address obtained from a DHCP server.
•
If the interface has no IP address or preauthentication IP pool specified, the user cannot
perform portal authentication.
After the user passes portal authentication, the AAA server authorizes an IP address pool for
re-assigning an IP address to the user. If no authorized IP address pool is deployed, the user
continues using the previous IP address.
If the portal user does not perform authentication or fails to pass authentication, the assigned IP
address is still retained.
When you specify a preauthentication IP address pool, follow these guidelines and restrictions:
•
This configuration takes effect only when the direct IPv4 portal authentication is enabled on the
interface.
•
Make sure the specified IP address pool exists and is complete. Otherwise, the user cannot
obtain the IP address and cannot perform portal authentication.
To specify an IP address pool before portal authentication:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Specify a preauthentication
IP address pool for portal
users.
portal
[
ipv6
]
pre-auth ip-pool
pool-name
By default, no preauthentication
IP address pool is specified on an
interface.
Enabling strict-checking on portal authorization information
The strict checking mode allows a portal user to stay online only when the authorized information for
the user is successfully deployed on the interface.
You can enable strict checking on authorized ACLs, authorized user profiles, or both. If you enable
both ACL checking and user profile checking, the user will be logged out if either checking fails.
An ACL/user profile checking fails when the authorized ACL/user profile does not exist on the device
or the ACL/user profile fails to be deployed.
To enable strict-checking on portal authorization information:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Enable strict checking
mode on portal
authorization
information.
portal authorization
{
acl
|
user-profile
}
strict-checking
By default, the strict checking mode
is disabled. In this case, the portal
users stay online even when the
authorized ACLs or user profiles do
not exist or fail to be deployed.
Содержание FlexFabric 5940 SERIES
Страница 251: ...238 ...