This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Hi!

I can't seem to get Windows Wireshark x64 2.01 to accomplish what this article suggests we do:

http://community.arubanetworks.com/t5/Controller-Based-WLANs/How-can-we-see-the-packets-tunneled-inside-the-GRE-tunnel/ta-p/184910

They suggest a decodeas change to have Wireshark decode this GRE traffic properly. I can't seem to configure this in the GUI, nor convince Wireshark to load a "decodeas" file..

Related to this, there has been some discussions about decoding Aruba-created GRE types.. how is that going in the 2.0 codebase?

Thanks!

asked 03 May '16, 13:14

OldMonkey's gravatar image

OldMonkey
6112
accept rate: 0%

I'm afraid it is not related to GRE directly but to the protocol ID indicated in the GRE header which you need to associate to the proper Ethertype dissector. Can you share (means: publish, login-free, somewhere like at Cloudshark, Dropbox, Google Drive, ..., and edit your Question with a link to it) a capture with at least a single packet like that so that we could have a look practically?

(03 May '16, 13:56) sindy
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×16
×3

question asked: 03 May '16, 13:14

question was seen: 1,254 times

last updated: 03 May '16, 13:56

p​o​w​e​r​e​d by O​S​Q​A