58Usage guidelinesTo perform local authentication of a user, the device matches the actual user attributes with theconfigured binding attributes. If the user has a non-matching attribute or lacks a required attribute,the user will fail authentication.Binding attribute check takes effect on all access services. Configure the binding attributes for a userbased on the access services and make sure the device can obtain all attributes to be checked fromthe user's packet. For example, you can configure an IP address binding for an 802.1X user,because 802.1X authentication can include the user's IP address in the packet. However, you cannotconfigure IP address bindings for MAC authentication users, because MAC authentication does notuse IP addresses.The binding interface type must meet the requirements of the local user. Configure the bindinginterface based on the service type of the user.• If the user is an 802.1X user, specify the 802.1X-enabled Layer 2 Ethernet interface throughwhich the user accesses the device.• If the user is a MAC authentication user, specify the MAC authentication-enabled Layer 2Ethernet interface through which the user accesses the device.• If the user is a portal user, specify the portal-enabled interface through which the user accessesthe device. Specify the Layer 2 Ethernet interface if portal is enabled on a VLAN interface andthe portal roaming enable command is not configured.Examples# Bind IP address 3.3.3.3 with network access user abc. system-view[Sysname] local-user abc class network[Sysname-luser-network-abc] bind-attribute ip 3.3.3.3Related commandsdisplay local-usercompanyUse company to specify the company of a local guest.Use undo company to restore the default.Syntaxcompany company-nameundo companyDefaultNo company is specified for a local guest.ViewsLocal guest viewPredefined user rolesnetwork-adminParameterscompany-name: Specifies the company name, a case-sensitive string of 1 to 255 characters.Examples# Specify company yyy for local guest abc. system-view
