Revision history [back]

Hello, I ran into an issue that in case if my protobuf message has 'repeated fixed32' on the end, this field could not be parsed correctly with Wireshark protobuf dissector, it shows 'Malformed packet' for the last byte, despite it also has 4 bytes.

If it has only one byte - it shows 'Malformed packet' for this single byte. I don't have this problem if change 'repeated fixed32' to 'bytes', but it is not suitable for me as a workaround.

Do you have any advices or maybe it is a real bug?

e.g. I meet this in a simple messages like

message Response
{
    repeated fixed32             Id = 1;
}

or bigger messages like:

message My_Cmd
{
    fixed32             field1 = 1;
    fixed32             field2 = 2;
    fixed32            field3 = 3;
    fixed32            payloadSize = 4;
    repeated fixed32 payload = 5;
}

Hello, I ran into an issue that in case if my protobuf message has 'repeated fixed32' on the end, this field could not be parsed correctly with Wireshark protobuf dissector, it shows 'Malformed packet' for the last byte, despite it also has 4 bytes.

If it has only one byte - it shows 'Malformed packet' for this single byte. I don't have this problem if change 'repeated fixed32' to 'bytes', but it is not suitable for me as a workaround.

Do you have any advices or maybe it is a real bug?

e.g. I meet this in a simple messages like

message Response
{
    repeated fixed32             Id = 1;
}

or bigger messages like:

message My_Cmd
{
    fixed32             field1   ![image description](http://)field1 = 1;
    fixed32              field2 = 2;
    fixed32             field3 = 3;
    fixed32             payloadSize = 4;
    repeated fixed32 payload = 5;
}

Hello, I ran into an issue that in case if my protobuf message has 'repeated fixed32' on the end, this field could not be parsed correctly with Wireshark protobuf dissector, it shows 'Malformed packet' for the last byte, despite it also has 4 bytes.

If it has only one byte - it shows 'Malformed packet' for this single byte. I don't have this problem if change 'repeated fixed32' to 'bytes', but it is not suitable for me as a workaround.

Do you have any advices or maybe it is a real bug?

e.g. I meet this in a simple messages like

message Response
{
    repeated fixed32             Id = 1;
}

or bigger messages like:

message My_Cmd
{
    fixed32               ![image description](http://)field1 field1 = 1;
    fixed32               field2 = 2;
    fixed32               field3 = 3;
    fixed32               payloadSize = 4;
    repeated fixed32 payload = 5;
}

Hello, I ran into an issue that in case if my protobuf message has 'repeated fixed32' on the end, this field could not be parsed correctly with Wireshark protobuf dissector, it shows 'Malformed packet' for the last byte, despite it also has 4 bytes.

If it has only one byte - it shows 'Malformed packet' for this single byte. I don't have this problem if change 'repeated fixed32' to 'bytes', but it is not suitable for me as a workaround.

Do you have any advices or maybe it is a real bug?

I'm using Wireshark ver 4.0.7 for Windows 64 bit

e.g. I meet this in a simple messages like

message Response
{
    repeated fixed32             Id = 1;
}

or bigger messages like:

message My_Cmd
{
    fixed32               field1 = 1;
    fixed32               field2 = 2;
    fixed32               field3 = 3;
    fixed32               payloadSize = 4;
    repeated fixed32 payload = 5;
}

Hello, I ran into an issue that in case if my protobuf message has 'repeated fixed32' on the end, this field could not be parsed correctly with Wireshark protobuf dissector, it shows 'Malformed packet' for the last byte, despite it also has 4 bytes.

If it has only one byte - it shows 'Malformed packet' for this single byte. I don't have this problem if change 'repeated fixed32' to 'bytes', but it is not suitable for me as a workaround.

Do you have any advices or maybe it is a real bug?

I'm using Wireshark ver 4.0.7 for Windows 64 bit

e.g. I meet this in a simple messages like

message Response
{
    repeated fixed32             Id = 1;
}

or bigger messages like:

message My_Cmd
{
    fixed32               field1 = 1;
    fixed32               field2 = 2;
    fixed32               field3 = 3;
    fixed32               payloadSize = 4;
    repeated fixed32 payload = 5;
}