| Bug ID |
8627
|
| Summary |
LISP control packet incorrectly identified as LISP data based when UDP source port is 4341
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.0
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.11.0 (SVN Rev 49143 from /trunk)
Copyright 1998-2013 Gerald Combs <[email protected]> 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 (64-bit) with GTK+ 3.4.4, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.32.4, with libpcap, with libz 1.2.7, with POSIX capabilities (Linux),
with libnl 3, without SMI, without c-ares, without ADNS, with Lua 5.1, without
Python, with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, without AirPcap.
Running on Linux 3.8.11-gentoo, with locale en_US.UTF-8, with libpcap version
1.3.0, with libz 1.2.7, GnuTLS 2.12.23, Gcrypt 1.5.0.
Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
Built using gcc 4.6.3.
--
There is a special "LISP Control" packet type, where the UDP source port is the
one registered for "LISP Data" and the UDP destination port is "LISP Control"
(4341 and 4342 respectively). Wireshark dissects this packet as "LISP Data"
which leads to incorrect dissection. While "LISP Control" can have the port
number 4342 as both source and destination, for "LISP Data" 4341 is always the
destination port.
You are receiving this mail because:
- You are watching all bug changes.