Revision history [back]

Dear Wireshark Community,

We are trying to show detailed expert information for goose packet. We expect to see:

1) where is the error field 2) what is the error field 3) why it is treated as an error

The following picture shows an example

This is a goose packet and it is malformed because the length of the field "numDataSetEntries" is 0 (the highlight part).

The reason is correctly shown (achieved (2)).

We also want to show the absolute index of the highlight field to automate our the analysis process. I have read that tvb_raw_offset might do the job, any hint for using it?

I am also wondering if it is possible to show the tag part in our case, since I think the only error part is the length field.

Thanks for reading my question!

Best Regards,

Ke Wang

Dear Wireshark Community,

We are trying to show detailed expert information for goose packet. We expect to see:

1) where is the error field 2) what is the error field 3) why it is treated as an error

The following picture shows an example

Imgur

This is a goose packet and it is malformed because the length of the field "numDataSetEntries" is 0 (the highlight part).

The reason is correctly shown (achieved (2)).

We also want to show the absolute index of the highlight field to automate our the analysis process. I have read that tvb_raw_offset might do the job, any hint for using it?

I am also wondering if it is possible to show the tag part in our case, since I think the only error part is the length field.

Thanks for reading my question!

Best Regards,

Ke Wang

Dear Wireshark Community,

We are trying to show detailed expert information for goose packet. We expect to see:

1) where is the error field 2) what is the error field 3) why it is treated as an error

The following picture shows an example

Imgur

This is a goose packet and it is malformed because the length of the field "numDataSetEntries" is 0 (the highlight part).

The reason is correctly shown (achieved (2)).

We also want to show the absolute index of the highlight field to automate our the analysis process. I have read that tvb_raw_offset might do the job, any hint for using it?

I am also wondering if it is possible to show the tag part in our case, since I think the only error part is the length field.

Thanks for reading my question!

Best Regards,

Ke Wang

Dear Wireshark Community,

This problem is an extension of issue on the gitlab

We are trying to show detailed expert information for goose packet. We expect to see:

1) where is the error field 2) what is the error field 3) why it is treated as an error

The following picture shows an example

This is a goose packet and it is malformed because the length of the field "numDataSetEntries" is 0 (the highlight part).

The reason is correctly shown (achieved (2)).

We also want to show the absolute index of the highlight field to automate our the analysis process. I have read that tvb_raw_offset might do the job, any hint for using it?

I am also wondering if it is possible to show the tag part in our case, since I think the only error part is the length field.

Thanks for reading my question!

Best Regards,

Ke Wang

Dear Wireshark Community,

This problem is an extension of issue on the gitlab

We are trying to show detailed expert information for goose packet. We expect to see:

1) where is the error field 2) what is the error field 3) why it is treated as an error

The following picture shows an example

This is a goose packet and it is malformed because the length of the field "numDataSetEntries" is 0 (the highlight part).

The reason is correctly shown (achieved (2)).

We also want to show the absolute index of the highlight field to automate our the analysis process. I have read that tvb_raw_offset might do the job, any hint for using it?

I am also wondering if it is possible to show the tag part in our case, since I think the only error part is the length field.

Thanks for reading my question!

Best Regards,

Ke Wang