hi!
during some tests I have seen some (possible) misbehaviour of the
sigcomp dissector: it cannot decompress a type 1 message (state access)
which is actually decompressed by one of the peers. it seems to have to do
with state management. (there are 3 nodes using sigcomp in the network
where the
PROTECTED] För cco
Skickat: den 22 november 2006 22:17
Till: wireshark-dev@wireshark.org
Ämne: [Wireshark-dev] is sigcomp dissector maintained?
hi!
during some tests I have seen some (possible) misbehaviour of the
sigcomp dissector: it cannot decompress a type 1 message (state access)
which is actually
On Wed, Nov 22, 2006 at 11:08:51PM +0100, Anders Broman wrote:
Hi,
If the corresponding type 2 message with the bytecode isn't in the trace
Wireshark can't decode the message.
cristian: the sigcomp message which creates the state is also captured
and decompressed by ethereal.
If you still
On Wed, Nov 22, 2006 at 11:08:51PM +0100, Anders Broman wrote:
Hi,
If the corresponding type 2 message with the bytecode isn't in the trace
Wireshark can't decode the message.
If you still think there is a problem we'd need the trace to be able to
locate the problem.
cristian: hi anders.
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För cco
Skickat: den 23 november 2006 00:18
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] is sigcomp dissector maintained?
cristian: hi anders. some more questions:
1. is wireshark always
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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
