Study guide

PPP Authentication: PAP and CHAP

Huawei Certified ICT Associate - Datacom HCIA-Datacom H12-811 V1.0

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About HCIA-Datacom H12-811 V1.0 Study Strategies and Exam Logistics

2 Chapter 1: Network Models and Ethernet Fundamentals

OSI and TCP/IP Models Ethernet Technology and MAC Addressing Data Forwarding and Campus Network Lifecycle

3 Chapter 2: IPv4 Addressing and Transport Protocols

IPv4 Addressing and Subnetting ARP and ICMP TCP and UDP Principles Common Ports and Application Protocols

4 Chapter 3: Huawei VRP Basics and Device Management

VRP CLI Views and Core Commands Configuration Save, Reset, and File System SSH, Telnet, and Console Access Display Commands and Basic Troubleshooting

5 Chapter 4: Ethernet Switching and VLANs

Switch Forwarding and MAC Address Tables VLAN Concepts and Segmentation Access, Trunk, and Hybrid Link Types VLANIF and Inter-VLAN Routing

6 Chapter 5: STP, RSTP/MSTP, and Link Aggregation

STP Concepts and Election RSTP and MSTP Eth-Trunk Static and LACP Stacking Basics for Campus Switches

7 Chapter 6: IP Routing Fundamentals

RIB, FIB, and Forwarding Decisions Static and Default Routes on VRP Route Preference and Longest Match Floating Static Routes and Blackhole Routes

8 Chapter 7: OSPF Fundamentals

OSPF Areas and Router Types Neighbor States and Adjacency LSA Types and LSDB DR/BDR Election and VRP OSPF Configuration

9 Chapter 8: ACLs and AAA

Basic and Advanced ACLs traffic-filter Application and Matching Order AAA with Local, RADIUS, and HWTACACS

10 Chapter 9: DHCP, NAT, and Network Services

DHCP Server, Relay, and Snooping NAT, Easy IP, and NAT Server FTP, TFTP, DNS, NTP, HTTP Basics

11 Chapter 10: WLAN Basics

WLAN Architecture: AC, AP, and Fit Mode CAPWAP Tunnels and Forwarding Modes WPA2, WPA3, and WLAN Security Basics Basic WLAN Configuration Concepts

12 Chapter 11: WAN Basics

WAN Concepts and Encapsulation PPP Authentication: PAP and CHAP PPPoE Basics and Client Configuration

13 Chapter 12: IPv6 Fundamentals

IPv6 Address Types and Format Neighbor Discovery and ICMPv6 Stateful and Stateless DHCPv6 IPv6 Static Routes on VRP

14 Chapter 13: SDN and NFV Fundamentals

SDN and NFV Fundamentals

15 Chapter 14: Network Management and O&M

Network Management, O&M, and Automation Basics

PPP Authentication: PAP and CHAP

Key Takeaways Explain This Topic AI

PPP authentication occurs after successful LCP negotiation when peers agree that authentication is required.

PAP is a two-way exchange that sends the password in plaintext across the link—simple but weak against eavesdropping.

CHAP is a three-way challenge-response handshake that avoids sending the password in cleartext and can re-challenge periodically.

On Huawei VRP, authentication mode is selected under the PPP-capable interface (for example ppp authentication-mode chap or pap) with local or AAA credentials.

  • Exam trap: prefer CHAP when the stem emphasizes security; PAP is not “more compatible so always better.”
  • Last updated: July 2026

PPP Authentication: PAP and CHAP

Quick Answer: After LCP agrees that authentication is required, PPP can run PAP or CHAP . PAP is a two-way exchange that sends the password in plaintext . CHAP is a three-way challenge-response method that does not put the password on the wire and is the more secure default choice on exams. On Huawei VRP, set ppp authentication-mode on the interface and supply matching local or AAA credentials.

Authentication is the middle act of the PPP play. If you skip it in design when the ISP requires it, the session never reaches NCP. If you pick the wrong method or mismatched secrets, LCP may look fine while the link still fails to pass IP. HCIA-Datacom tests the mechanics , security comparison , and configuration intent more than exotic multiprotocol edge cases.

Where authentication sits in the PPP lifecycle

Physical / lower-layer media is available (serial up, PPPoE session progressing, and so on).

LCP opens, negotiates options, and—if configured—includes the authentication protocol option.

Authentication runs to completion (success or failure).

On success, NCP (for IPv4, IPCP ) negotiates network parameters and IP can flow.

Either peer can require the other to authenticate, depending on design (ISP authenticates the customer; enterprise may authenticate a remote peer). For branch Internet, the common pattern is: ISP authenticates the customer CPE with a username and password provisioned on the account.

PAP: Password Authentication Protocol

PAP is intentionally simple.

Two-way exchange (conceptual)

  • Step Direction Content
  • 1 Authenticatee → Authenticator Username and password (cleartext in the protocol)
  • 2 Authenticator → Authenticatee Accept or reject

That is why PAP is called a two-way handshake: credentials go out, result comes back. There is no cryptographic challenge.

Strengths and weaknesses

  • Aspect PAP behavior
  • Implementation complexity Low
  • Password on the wire Yes—plaintext
  • Protection against replay/eavesdropping Poor on an untrusted link
  • Re-challenge during the session Not the CHAP-style periodic model
  • When it still appears Legacy ISP gear, lab simplicity, or stems that explicitly demand PAP

Exam wording: If the question says the password is transmitted in cleartext, or asks which method is less secure, the answer is PAP .

CHAP: Challenge Handshake Authentication Protocol

CHAP improves security by never sending the shared secret as plaintext password bytes in the authentication messages.

Three-way challenge-response (conceptual)

  • Step Name What happens
  • 1 Challenge Authenticator sends a random challenge (and identity) to the peer

2 Response Peer computes a one-way hash over the challenge, secret, and related fields; returns the hash (not the raw password)

3 Success/Failure Authenticator performs the same hash with its copy of the secret and accepts or rejects

Because the challenge is unpredictable, a captured response is not reusable as a static password later in the same way a sniffed PAP password is. CHAP can also re-challenge during a live session so a compromised session start is harder to ride indefinitely—exam materials often mention periodic re-authentication as a CHAP advantage.

Strengths and weaknesses

  • Aspect CHAP behavior
  • Password on the wire No (hash response)
  • Handshake shape Three-way
  • Security relative to PAP Stronger for HCIA comparison questions
  • Shared secret requirement Both sides need the matching secret/password material
  • Complexity Higher than PAP

Exam wording: “challenge-response,” “three-way,” “more secure,” or “password not sent in plaintext” → CHAP .

Side-by-side comparison table

  • Topic PAP CHAP
  • Full name Password Authentication Protocol Challenge Handshake Authentication Protocol
  • Message pattern Two-way Three-way
  • Credential exposure Password sent in clear Hash of challenge + secret
  • Typical exam preference when security is the goal Avoid Prefer
  • Failure effect PPP auth fails; NCP/IP do not come up cleanly Same operational outcome on failure
  • Huawei mode keyword (concept) pap chap

Do not invent a third “better than CHAP” PPP password method on HCIA unless the stem explicitly introduces another technology. The tested pair is PAP vs CHAP .

Huawei VRP configuration concepts (HCIA level)

Exact syntax can vary slightly by platform and software train, but the conceptual knobs are stable:

  • 1) Choose authentication mode on the PPP interface
  • Under the interface that runs PPP (serial example conceptually): [Huawei] interface Serial0/0/0
  • [Huawei-Serial0/0/0] link-protocol ppp
  • [Huawei-Serial0/0/0] ppp authentication-mode chap
  • Or for PAP: [Huawei-Serial0/0/0] ppp authentication-mode pap

Some designs use chap pap style fallback ordering when both are offered; know that mode selection must match what the peer demands . If the ISP requires CHAP only, configuring PAP alone will not pass authentication.

2) Provide the local user or AAA credentials

The authenticator needs a username/password database entry that matches what the peer sends (PAP) or uses as the CHAP secret material. On associate-level labs this is often a local user : [Huawei] aaa

  • [Huawei-aaa] local-user branch01 password irreversible-cipher StrongP@ssw0rd
  • [Huawei-aaa] local-user branch01 service-type ppp

(Service-type and password form can differ by version; the exam idea is: user exists, password matches, PPP service allowed .)

When the Huawei device is the client authenticating to an ISP, you configure the call-out credentials on the interface or dialer (username/password for PAP/CHAP client role). In PPPoE edge designs (next section), those credentials ride the dialer/PPP client.

3) Authentication direction roles

  • Role Meaning
  • Authenticator Challenges or receives credentials and accepts/rejects
  • Authenticatee (peer) Proves identity

Misreading the role causes “I set a local user but I am the client to the ISP” confusion. For ISP Internet access, the ISP is usually the authenticator ; your router supplies the account the ISP already created.

  • Verification and failure patterns
  • Useful mental checks (command families, not a full CLI encyclopedia): [Huawei] display interface Serial0/0/0
  • [Huawei] display ppp interface Serial0/0/0

Interpret symptoms against the phase model:

  • Symptom Likely layer
  • Physical down Cable, carrier, admin shutdown
  • LCP not open Encapsulation mismatch, LCP option disagreement

Auth fail messages / repeated retries Wrong mode (PAP vs CHAP), bad username/password, user not permitted for PPP

Auth OK but no IP NCP/IPCP or addressing/route issue after auth

Exam trap: A wrong password is an authentication failure, not proof that OSPF is broken on the LAN. Fix the secret and mode before redesigning the campus.

Security guidance for the exam (and real life)

Prefer CHAP when the question allows either and highlights security.

Treat PAP as legacy or explicitly required only.

Remember that CHAP still depends on secret strength and protection of the device config—hashing the password on the wire does not help if display current-configuration is world-readable without AAA control.

PPPoE does not replace PAP/CHAP; it carries PPP, so the same auth choice still matters.

Common H12-811 traps

  • Trap stem Correct thinking
  • “Which sends password in plaintext?” PAP
  • “Which uses challenge-response?” CHAP
  • “Two-way vs three-way” PAP two-way; CHAP three-way
  • “Most secure PPP auth among PAP/CHAP” CHAP
  • Auth configured but IP still missing Check NCP/IPCP and routes after auth success
  • Mode mismatch Both ends must agree on PAP vs CHAP
  • Practice goals before PPPoE

Draw PAP’s two messages and CHAP’s three messages from memory.

Given a stem that says “password not transmitted,” select CHAP without hesitation.

On a mental Huawei serial PPP interface, state where ppp authentication-mode is set and why a local user needs PPP service permission when acting as authenticator.

Map “auth failed” vs “no IP address” to different PPP phases.

With PAP and CHAP clear, the next section places the same PPP session on top of Ethernet broadband using PPPoE , including discovery stages and Huawei dialer/client ideas.