Configuring IMSI/SN binding authentication

1. Enter system view.

system-view

N/A

2. Enter VT interface view.

interface virtual-template virtual-template-number

By default, no VT interface is created.

3. Enable the LNS to initiate IMSI or SN binding authentication requests.

ppp lcp { imsi | sn } request

By default, the LNS does not initiate IMSI or SN binding authentication requests.

4. (Optional.) Configure the separator for the received authentication information.

ppp user accept-format imsi-sn split splitchart

By default, no separator is configured for the received authentication information.

If no IMSI or SN information is received from the peer during the authentication process, the IMSI or SN information split from the received authentication information is used.

5. (Optional.) Replace the client username with the IMSI or SN information for authentication.

ppp user replace { imsi | sn }

By default, the client username is used for authentication.

1. Enter system view.

system-view

N/A

2. Enter VT interface view.

interface virtual-template virtual-template-number

By default, no VT interface is created.

3. Enable the client to accept the IMSI or SN binding authentication requests from the LNS.

ppp lcp { imsi | sn } accept

By default, the client does not accept IMSI or SN binding authentication requests.

4. (Optional.) Configure the IMSI/SN information on the client.

ppp lcp { imsi | sn } string info

By default, the client automatically obtains the IMSI or SN information from its SIM card.

5. (Optional.) Configure the separator for the sent authentication information.

ppp user attach-format imsi-sn split splitchart

By default, no separator is configured for the sent authentication information.