I was using wireshark 1.6.12 and decoding AIROPEEK package ok. After upgrading to 1.8.4, that option is gone from "Decode As..." option. Am I missing something here? asked 05 Dec '12, 15:09 dbdiep |
One Answer:
Airopeek was ambiguous. There's the capture file format and UDP transported traffic. Therefore this last one was renamed PEEKREMOTE. See this revision of the change. answered 04 Jan '13, 15:08 Jaap ♦ And the capture file format isn't "AiroPeek" - WildPackets' own terms for their two capture file formats, both of which have been used by versions of EtherPeek, TokenPeek, and AiroPeek, are "Peek classic" and "Peek tagged". The UDP-transported traffic, as the revision notes, is not unique to AiroPeek, so the protocol was renamed. (05 Jan '13, 14:28) Guy Harris ♦♦ |
I have the same question... Can anyone please answer? Thanks!
I don't have an "airopeek" capture file at hand to test with. Could you post one on www.cloudshark.org and paste the link to the file here to analyse?