On 05/02/2013 05:49 PM, Alexis La Goutte wrote:
> On Thu, May 2, 2013 at 4:41 PM, Anders Broman
> mailto:anders.bro...@ericsson.com>> wrote:
>
> Hi,
> Disclaimer: Without looking at the code.
>
> +1
>
>
> Couldn't the "LISO Data" dissector check the destination port and
> call LIS
s
>
> -Original Message-
> From: wireshark-dev-boun...@wireshark.org [mailto:
> wireshark-dev-boun...@wireshark.org] On Behalf Of Lori Jakab
> Sent: den 2 maj 2013 16:10
> To: wireshark-dev@wireshark.org
> Subject: [Wireshark-dev] Conflict between LISP control and LISP da
reshark.org] On Behalf Of Lori Jakab
Sent: den 2 maj 2013 16:10
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] Conflict between LISP control and LISP data dissectors
Hi,
There is a special "LISP Control" packet type, where the UDP source port is the
one registered for "LISP
Hi,
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 Contro
