Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] hi,can you give me some help about PPPoE packets?

From: "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
Date: Wed, 16 Jun 2010 12:51:42 -0400

The latest version of Wireshark does not exhibit this problem.  I suggest you upgrade from 1.2.9 to 1.4rc1 or wait until the official 1.4 release comes out which should be very soon.

- Chris

 

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of LIU Wei O
Sent: Wednesday, June 16, 2010 1:34 AM
To: ethereal-users@xxxxxxxxxxxx; wireshark-users@xxxxxxxxxxxxx; info@xxxxxxxxxxxx
Subject: [Wireshark-users] hi
can you give me some help about PPPoE packets?

 

Hi,dear shark,

  I have a question about ‘PPPoE payload length’.

  As we know In RFC 2516,It defined the Length field’ :

 

The LENGTH field is sixteen bits. The value, in network byte order,

indicates the length of the PPPoE payload. It does not include the

length of the Ethernet or PPPoE headers.

 

 

You can refer to the packet that be captured in SNI(service network interface) in the annex,you can find that

In dscovery stage ,the payload length is right ,however in session stage ,wireshark judge it has some error because it

think the ‘payload length’ should contain the pads and CRC.

 

incongruous operation mechanism between dscovery stage and session stage in the PPPoE.

 

Now we use the R1.2.9,when will the issue be delivered?

 

Best regards

                                    Yours

                                                                               Wei liu

 

Liuwei

***I am here,but also there.***

 

CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and 
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.