Wireshark-bugs: [Wireshark-bugs] [Bug 1455] New: LLDPDU MAC-PHY TLV PMD Auto-Neg field is being

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 20 Mar 2007 18:47:56 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1455

           Summary: LLDPDU MAC-PHY TLV PMD Auto-Neg field is being analyzed
                    incorrectly
           Product: Wireshark
           Version: 0.99.5
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jhilman@xxxxxxxxxxxx
                CC: jhilman@xxxxxxxxxxxx


Build Information:
Version 0.99.5 (SVN Rev 20677)
--
When capturing a single LLDPDU with the Wireshark product, and the MAC-PHY TLV
enabled for Tx from the DUT, I'm capturing data which shows that the PMD
Auto-Negotiation Advertised Capability field with a value of 0x0136, or 0000
0001 0011 0110.  According to the table outlined in RFC3636 (pg.41), the
advertised capibilities should be as follows:

           bOther(0),        -- other or unknown
   this--> b10baseT(1),      -- 10BASE-T  half duplex mode
   this--> b10baseTFD(2),    -- 10BASE-T  full duplex mode
           b100baseT4(3),    -- 100BASE-T4
   this--> b100baseTX(4),    -- 100BASE-TX half duplex mode
   this--> b100baseTXFD(5),  -- 100BASE-TX full duplex mode
           b100baseT2(6),    -- 100BASE-T2 half duplex mode
           b100baseT2FD(7),  -- 100BASE-T2 full duplex mode
   this--> bfdxPause(8),     -- PAUSE for full-duplex links
           bfdxAPause(9),    -- Asymmetric PAUSE for full-duplex
                             --     links
           bfdxSPause(10),   -- Symmetric PAUSE for full-duplex
                             --     links
           bfdxBPause(11),   -- Asymmetric and Symmetric PAUSE for
                             --     full-duplex links
           b1000baseX(12),   -- 1000BASE-X, -LX, -SX, -CX half
                                 --     duplex mode
           b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
                             --     duplex mode
           b1000baseT(14),   -- 1000BASE-T half duplex mode
           b1000baseTFD(15)  -- 1000BASE-T full duplex mode

However, Wireshark is showing:

           bOther(0),        -- other or unknown
           b10baseT(1),      -- 10BASE-T  half duplex mode
           b10baseTFD(2),    -- 10BASE-T  full duplex mode
           b100baseT4(3),    -- 100BASE-T4
           b100baseTX(4),    -- 100BASE-TX half duplex mode
           b100baseTXFD(5),  -- 100BASE-TX full duplex mode
           b100baseT2(6),    -- 100BASE-T2 half duplex mode
   this--> b100baseT2FD(7),  -- 100BASE-T2 full duplex mode
           bfdxPause(8),     -- PAUSE for full-duplex links
   this--> bfdxAPause(9),    -- Asymmetric PAUSE for full-duplex
                             --     links
   this--> bfdxSPause(10),   -- Symmetric PAUSE for full-duplex
                             --     links
           bfdxBPause(11),   -- Asymmetric and Symmetric PAUSE for
                             --     full-duplex links
           b1000baseX(12),   -- 1000BASE-X, -LX, -SX, -CX half
                             --     duplex mode
   this--> b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
                             --     duplex mode
   this--> b1000baseT(14),   -- 1000BASE-T half duplex mode
           b1000baseTFD(15)  -- 1000BASE-T full duplex mode

This would be: 0110 0110 1000 0000 or 0x6680


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