Wireshark-bugs: [Wireshark-bugs] [Bug 3113] New: wireshark doesn't decode DSL Forum TR-101 PPPoE

Date: Fri, 12 Dec 2008 03:17:21 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3113

           Summary: wireshark doesn't decode DSL Forum TR-101 PPPoE tags
           Product: Wireshark
           Version: 1.0.5
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: stefan.puiu@xxxxxxxxx


Created an attachment (id=2552)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2552)
PPPoE capture with TR-101 options

Build Information:
Version 1.0.5 (SVN Rev 26954)
--
Load the attached configuration and check the PADI messages (or PADR). If you
check the bytes, notice there's a void 'service name' option (0x0101 for
tag_type, 0x0000 for the tag_length) which wireshark doesn't mention, then a
vendor-specific tag and then a set of TR-101 suboptions. The vendor-id is
displayed correctly (0x00000de9 - DSL Forum), then there's a blob called
'vendor unspecified'. 

The main issue I was going to point out is the lack of support for decoding the
suboptions (so this is more of a feature request). I also think that the
vendor-specific tag is decoded in a somewhat counter intuitive way - the
display might suggest there are two tags, vendor-id and vendor-unspecified,
when in fact there's only one. 

The lack of service-name is something else. I have an old wireshark-0.99.6a
which displays it, so it looks like a regression as far as I can tell. 

TR-101 can be found here:
http://www.broadband-forum.org/technical/download/TR-101.pdf

The format for suboptions is appendix A, page 96.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.