Wireshark mailing list archives

Re: Request for a Wireshark Update to support TEAP traffic analysis.


From: Alexis La Goutte <alexis.lagoutte () gmail com>
Date: Sat, 8 Feb 2020 16:42:49 +0100

Hi Nikhil,

can you create a bug on BugTracker and attach the pcap ? it will look for
add TEAP support

Cheers

On Fri, Feb 7, 2020 at 4:33 PM Nikhil Jadhav <Njadhav () securview com> wrote:

Hello Developers,



I am working on Cisco ISE and I find the Wireshark tool very beneficial to
analyze different packets. So Cheers to all your hard work!!!

I am using Windows 10 (Insider Preview Build with TEAP support) endpoint
 with the latest version of Wireshark running (Version 3.2.1
(v3.2.1-0-gbf38a67724d0)).

Currently there is a new TEAP protocol (Tunneled EAP protocol - RFC 7170)
, and we tried to analyze the TEAP traffic on Wireshark but Wireshark shows
the Code-Type in EAP as ‘Unknown’ instead of ‘TEAP’ even though it
identifies the code as 55. Also, could you please let me know if there be
way to analyze the TEAP traffic by adding certificate to Wireshark.



Kindly please have a look at the attached Wireshark screenshots of TEAP
Traffic and PEAP traffic so as to have a better comparison and
understanding of the issue.

Hope to see this issue resolved soon!



Regards,

*Nikhil Jadhav*

Network Security Engineer

(o): 732.393.7767 | (m): 813.317.5118

200 Metroplex Drive Edison NJ, 08817

<http://www.securview.com/>


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org
?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: