The following are relevant settings for a local user database directly assigned to PPPoE node:
Host identification parameters (user name only)
Username
Password
Address
DNS servers (under DHCP options)
NBNS servers (under DHCP options)
Identification (ESM) strings
Incoming PPPoE connections are always authenticated through the PPPoE tree in the local user database.
The match list for a local user database that is assigned directly to the PPPoE node under the group interface is always user-name, independent of the match list setting in the database.
For username matching, the incoming username (user[@domain]) is always first converted to a user and a domain entity by splitting it on the first @-sign. If the no-domain parameter to the username is specified, the user component should be equal to the specific username, if the domain-only portion of the username is specified, the domain entity should be equal to the specified username and if no extra parameters are provided, the user and domain components are concatenated again and compared to the specific username.
The option number for the identification strings is not used if the local user database is assigned directly to the PPPoE node (it is only necessary if it is connected to a local DHCP server). Any valid value may be chosen in this case (if omitted, the default value chosen is 254).
If a pool name is specified for the address, this pool name is sent to the DHCP server in a vendor-specific sub-option of Option 82 to indicate from which pool the server should take the address. If the gi-address option is specified for the address, this is interpreted as if no address was provided.