Bug ID |
11190
|
Summary |
Unexpected warning in OSPF Traffic Engineering LSA
|
Product |
Wireshark
|
Version |
1.5.x (Experimental)
|
Hardware |
x86
|
OS |
Mac OS X 10.10
|
Status |
UNCONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 13605 [details]
OSPF TE LSA
Build Information:
Wireshark 1.99.6-340-gc3c8316 (v1.99.6rc0-340-gc3c8316 from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.3, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, with AirPcap.
Running on Mac OS X 10.10.3, build 14D136 (Darwin 14.3.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Attached is properly formatted pcap file with OSPF udpate containing MPLS
Traffic Engineering LSA, defined in RFC 3639, Section 2.2. That LSA contains
Router Address TLV, defined in section 2.4.1, using format form 2.3.2.
Wireshark fires warning:
MPLS Traffic Engineering LSA
[Expert Info (Warn/Malformed): Trying to fetch an IPv4 address
with length 8]
[Trying to fetch an IPv4 address with length 8]
[Severity level: Warn]
[Group: Malformed]
Router Address: 0.1.0.4 (0.1.0.4)
TLV Type: 1 - Router Address
TLV Length: 4
MPLS/TE Router ID: 172.16.0.22 (172.16.0.22)
Although the packet is correct. I.e. length field of Router Address TLV is
correctly set to '00 04' (bytes 0x60-0x61)
You are receiving this mail because:
- You are watching all bug changes.