The authentication trigger-condition command configures the packet types that can trigger MAC address authentication.
The undo authentication trigger-condition command restores the default configuration.
By default, DHCP/ARP/DHCPv6/ND packets can trigger MAC address authentication.
authentication trigger-condition { dhcp | arp | dhcpv6 | nd | any-l2-packet } *
undo authentication trigger-condition [ dhcp | arp | dhcpv6 | nd | any-l2-packet ] *
Parameter | Description | Value |
---|---|---|
dhcp |
Triggers MAC address authentication through DHCP packets. |
- |
arp |
Triggers MAC address authentication through ARP packets. |
- |
dhcpv6 |
Triggers MAC address authentication through DHCPv6 packets. |
- |
nd |
Triggers MAC address authentication through ND packets. |
- |
any-l2-packet |
Triggers MAC address authentication through any packets. For multicast packets, the corresponding protocol needs to be enabled, otherwise MAC authentication cannot be triggered. |
- |
Usage Scenario
After MAC address authentication is enabled, the device can trigger MAC address authentication on users by default when receiving DHCP/ARP/DHCPv6/ND packets. Based on user information on the actual network, the administrator can adjust the packet types that can trigger MAC address authentication. For example, if all users on a network dynamically obtain IPv4 addresses, the device can be configured to trigger MAC address authentication only through DHCP packets. This prevents the device from continuously sending ARP packets to trigger MAC address authentication when static IPv4 addresses are configured for unauthorized users on the network, and reduces device CPU occupation.
If a static IPv4 address is configured for a client, MAC address authentication cannot be triggered because they do not exchange DHCP or ARP packets. You can run the authentication trigger-condition any-l2-packet command to trigger MAC address authentication through any packets. To prevent unauthorized users from occupying user entries on the device maliciously, you are advised to configure the function of triggering MAC address authentication through any packets on the access device, and run the authentication mode max-user max-user-number command in the authentication profile view to configure the maximum number of access users allowed on an interface. The recommended value is 10.
Precautions
MAC address authentication configured on a VLANIF interface can be triggered by ARP or ND packets.
This function takes effect only for users who go online after this function is successfully configured.
There is a situation that you should notice. A device is configured to trigger MAC address authentication through DHCP packets and DHCP options are used as the user names for MAC address authentication (for the configuration of user names in MAC address authentication, see mac-authen username). If the authentication server delivers Huawei extended RADIUS attribute HW-Forwarding-VLAN (No. 26-161) to the device, the user packet must carry double VLAN tags and the outer VLAN ID cannot be the same as the ID of HW-Forwarding-VLAN; otherwise, the delivered attribute cannot take effect.
Only wired users support MAC address authentication triggered by DHCP/ARP/DHCPv6/ND/any packets. For wireless users, MAC address authentication is triggered by association packets.
After the authentication trigger-condition { dhcp | dhcpv6 | nd } * command is run, static users cannot go online.
In a policy association scenario, MAC address authentication can only be triggered by DHCP or ARP or DHCPv6 or ND packets.