No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Appendix

Appendix

This section describes PPPoE packets.

PPPoE Packet Format

A PPPoE packet is a PPP packet encapsulated in an Ethernet frame. Figure 8-7 shows the format of a PPPoE packet.

Figure 8-7  PPPoE packet format

The following table describes each field in a PPPoE packet.

Table 8-1  Description of each field in a PPPoE packet

Field

Length

Description

Destination_Address

48 bits

An Ethernet unicast destination address or Ethernet broadcast address 0xFFFFFFFF.
  • For a Discovery packet, the value is a unicast or broadcast address. When the client sends the packet to search for the server, the value is a broadcast address. When the client has discovered the server, the value is a unicast address.

  • At the Session stage, the value must be the unicast address determined by the PPPoE server and client at the Discovery stage.

Source_Address

48 bits

Ethernet MAC address of the source device.

Ethernet_Type

16 bits

Stage of PPPoE dial-up.

  • The value 0x8863 indicates the Discovery or Terminate stage.

  • The value 0x8864 indicates the Session stage.

VER

4 bits

PPPoE version number. This field has a fixed value of 0x01.

Type

4 bits

PPPoE type. This field has a fixed value of 0x01.

Code

8 bits

PPPoE packet type.
  • 0x00: indicates session data.
  • 0x09: indicates PADI packets.
  • 0x07: indicates PADO packets.
  • 0x19: indicates PADR packets.
  • 0x65: indicates PADS packets.
  • 0xa7: indicates PADT packets.

For details about PPPoE packets, see PPPoE Packet Type.

Session_ID

16 bits

An unsigned number in network byte order.

The value is fixed for a given PPPoE session and defines a PPPoE session along with Ethernet Source_address and Destination_address.

The value 0xFFFF is reserved.

Length

16 bits

Length of the PPPoE payload, excluding the length of the Ethernet header and PPPoE header.

Tag_Type

16 bits

Network byte order.

Tag_Length

16 bits

Number of bytes in the Tag_Value field. It is an unsigned number in network byte order.

Checksum

16 bits

Checksum. It is used to check the packet validity.

PPPoE Packet Type

Based on the value of the Code field, PPPoE packets are classified into the following types:

  • The value 0x09 indicates PPPoE Active Discovery Initiation (PADI) packets.
  • The value 0x07 indicates PPPoE Active Discovery Offer (PADO) packets.
  • The value 0x19 indicates PPPoE Active Discovery Request (PADR) packets.
  • The value 0x65 indicates PPPoE Active Discovery Session-confirmation (PADS) packets.
  • The value 0x00 indicates session data.
  • The value 0xa7 indicates PPPoE Active Discovery Terminate (PADT) packets.
Discovery Stage

PADI

  • The Code field is set to 0x09.

  • The Session_ID field is set to 0x0000.

  • The Tag_Type field is set to 0x0101 (Service-Name). It is followed by a service name. A PADI packet contains only one tag with Tag_Type being Service-Name, and other tags are optional.

Figure 8-8  Example of a PADI packet

PADO

  • The Code field is set to 0x07.

  • The Session_ID field is set to 0x0000.

  • Different values of the Tag_Type field represent different tag types.

    • When the Tag_Type field is set to 0x0101 (Service-Name), it is followed by a service name.

    • When the Tag_Type field is set to 0x0102 (AC-Name), it is followed by a string that uniquely identifies an access controller (AC).

    A PADO packet contains only one tag with Tag_Type being AC-Name and at least one tag with Tag_Type being Service-Name.

Figure 8-9  Example of a PADO packet

PADR

  • The Code field is set to 0x19.

  • The Session_ID field is set to 0x0000.

  • The Tag_Type field is set to 0x0101 (Service-Name). It is followed by a service name. A PADR packet contains only one tag with Tag_Type being Service-Name, and other tags are optional.

Figure 8-10  Example of a PADR packet

PADS

  • The Code field is set to 0x65.

  • The value of the Session_ID field is that specified at the Discovery stage.

  • Tags are optional.

Figure 8-11  Example of a PADS packet

Session Stage
  • The Ethernet_Type field is set to 0x8864.

  • The Code field is set to 0x00.

  • The value of the Session_ID field is that specified at the Discovery stage.

  • The Tag_Type field contains a PPP frame with the first field being PPP Protocol-ID.

    The following table lists the PPP protocol IDs supported by an AP.
    Table 8-2  PPP protocol code

    Protocol Code

    Protocol Type

    8021

    Internet Protocol Control Protocol

    C021

    Link Control Protocol

    C023

    Password Authentication Protocol

    C223

    Challenge Handshake Authentication Protocol

Figure 8-12  Example of a packet at the Session stage

Terminate Stage

PADT

  • The Code field is set to 0xa7.

  • The value of the Session_ID field is that specified at the Discovery stage.

  • No tag is required in a PADT packet.

Figure 8-13  Example of a PADT packet

Translation
Download
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 117938

Downloads: 309

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next