ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] is sigcomp dissector maintained?

From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Thu, 23 Nov 2006 08:05:39 +0100

-----Ursprungligt meddelande-----
Från: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Anders Broman
Skickat: den 23 november 2006 07:45
Till: 'Developer support list for Wireshark'
Ämne: Re: [Wireshark-dev] is sigcomp dissector maintained?


>>3. I am not an wireshark developer and I cannot figure out if
>>showing exactly which sigcomp message from the trace has caused a NACK
>>would 
>>be feasable. (when a lot of NACKs are there it is really difficult to
>>figure out which message has caused it)

>Briefly going back to the RFC it looks like that would involve doing a
>SHA-1 of the message and keep a list of that and the frame number.

With a trace with some Messages and their NACK:s that might be
fairly quick to implement.
BR
Anders
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev