Wireshark-bugs: [Wireshark-bugs] [Bug 3082] New: OSPF Dissector Does Not Decode or Display Neigh
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 24 Nov 2008 12:28:28 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3082

           Summary: OSPF Dissector Does Not Decode or Display Neighbor IP
                    Addresses
           Product: Wireshark
           Version: 1.0.4
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: Jim@xxxxxxxxxxxxxxxxx


Created an attachment (id=2518)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2518)
Wireshark capture file with ten OSPF Hello packets

Build Information:
Version 1.0.4 (SVN Rev 26501)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804

--
In some OSPF Hello packets, Wireshark does not display the IP addresses of all
the OSPF neighbors that are listed in the packet. See the attached file,
"ospf-hello.pcap", which is a capture file consisting of 10 OSPF Hello packets.

In Wireshark, highlight the first packet. In the Packet Details pane, expand
"Open Shortest Path First". Underneath that, expand "OSPF Hello Packet". The
last item under that heading is "Active Neighbor: 11.0.0.1". Highlight that
line. In the Packet Bytes pane, bytes 0x004e through 0x0051 will be
highlighted. Now highlight the next item in the Packet Details list, "OSPF LLS
Data Block". This will highlight bytes 0x0062 through 0x0085. Bytes 0x0052
through 0x0061 are skipped. The raw data is in the Packet Bytes pane, but those
bytes are not decoded and displayed in the Packet Details pane.

If this same file is loaded into Microsoft Network Monitor 3.2, it decodes and
displays the IP addresses of all 14 OSPF neighbors, beginning with 11.0.0.1 and
including 13 others.


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