137
•
The interface is not added to any port aggregation group.
•
The portal server referenced by the interface already exists.
•
Layer 2 portal authentication is not enabled on any ports.
Follow these guidelines when you enable Layer 3 portal authentication:
•
You cannot enable portal authentication on a Layer 3 interface in a port aggregation group. If an
interface is enabled with portal authentication, you cannot add it to a port aggregation group.
•
The destination port number that the device uses for sending unsolicited packets to the portal server
must be the same as the port number that the remote portal server actually uses.
•
Cross-subnet authentication mode (
portal
server
server-name
method layer3
) does not require
Layer 3 forwarding devices between the access device and the authentication clients. However, if
Layer 3 forwarding devices exist between the authentication client and the access device, you must
select the cross-subnet portal authentication mode.
•
In re-DHCP authentication mode, a client can use a public IP address to send packets before
passing portal authentication. However, responses to the packets are restricted.
•
An IPv6 portal server does not support the re-DHCP portal authentication mode.
•
You can enable both an IPv4 portal server and an IPv6 portal server for Layer 3 portal
authentication on an interface, but you cannot enable two IPv4 or two IPv6 portal servers on the
interface.
To enable Layer 3 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.
Enable Layer 3 portal
authentication on the
interface.
portal
server
server-name
method
{
direct
|
layer3
|
redhcp
}
Not enabled by default.
NOTE:
The portal server and its parameters can be deleted or modified only when the portal server is not
referenced by any interface.
Controlling access of portal users
Configuring a portal-free rule
A portal-free rule allows specified users to access specified external websites without portal
authentication.
The matching items for a portal-free rule include the source and destination IP address, TCP/UDP port
number, source MAC address, inbound interface, and VLAN. Packets matching a portal-free rule will not
trigger portal authentication, so that users sending the packets can directly access the specified external
websites.
For Layer 2 portal authentication, you can configure only a portal-free rule that is from any source
address to any or a specified destination address. If you configure a portal-free rule that is from any