Wireshark-bugs: [Wireshark-bugs] [Bug 2859] HomePlug Dissector bug Warning
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 8 Sep 2008 23:21:18 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2859





--- Comment #4 from Jaap Keuter <jaap.keuter@xxxxxxxxx>  2008-09-08 23:21:16 PDT ---
These are the references used to write the dissector code with, so there should
be no surprises. The question is, does the device generating this frame adhere
to the same spec?

The repair you described is indeed the way to go. Still, doing that doesn't
seem to give a useful result either. This is what you get:

Frame 1 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: HewlettP_6a:ff:95, Dst: Broadcast
HomePlug protocol
    MAC Control Field: 2
        Reserved
        .000 0010 = Number of MAC Data Entries: 2
    MAC Management Entry Header
        000. .... = MAC Entry Version: 0
        ...0 0100 = MAC Entry Type: Unknown (0x04)
    MAC Management Entry Length: 9
    Data: 011079D0D0B9E6CD0E
    MAC Management Entry Header
        000. .... = MAC Entry Version: 0
        ...1 1111 = MAC Entry Type: Unknown (0x1f)
    MAC Management Entry Length: 3
    Data: 588601

And then 29 bytes remain (padding to 60?). 


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