Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Edit (27.03.19): I believe I wasn't bringing my point across very well. It's about Wireshark build 3.1.0rc0-190-g41c566b4. The file in question is "epan/dissectors/packet-its.c"

The code reads as if all the dissectors were implemented. Though I can only recognize the lowest level of those ITS messages when running said build. Since I am new to dissector development I have no clue as to why it isn't working.

Anybody know what's wrong with the code? Is there an issue tracker where I could follow certain dissectors?

Thanks

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Edit (27.03.19): I believe I wasn't bringing my point across very well. It's about Wireshark build 3.1.0rc0-190-g41c566b4. The file in question is "epan/dissectors/packet-its.c"

The code reads as if all the dissectors were implemented. Though I can only recognize the lowest level of those ITS messages when running said build. Since I am new to dissector development I have no clue as to why it isn't working.

Anybody Does anybody know what's wrong with the code? Is there an issue tracker where I could follow certain dissectors?

Thanks

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Edit (27.03.19): I believe I wasn't bringing my point across very well. It's about Wireshark build 3.1.0rc0-190-g41c566b4. The file in question is "epan/dissectors/packet-its.c"

The code reads as if all the dissectors were implemented. Though I can only recognize the lowest level of those ITS messages when running said build. Since I am new to dissector development I have no clue as to why it isn't working.

My idea was to implement them myself using an ASN.1 compiler for wireshark (which name I forgot). When I noticed that there already were all the necessary ASN.1 definitions present. A look in the code surprised me with lots of DENM and CAM references. Though they wouldn't appear in the build.

Does anybody know what's wrong with the code? Is there an issue tracker where I could follow certain dissectors?

Thanks

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Edit (27.03.19): I believe I wasn't bringing my point across very well. It's about Wireshark build 3.1.0rc0-190-g41c566b4. The file in question is "epan/dissectors/packet-its.c"

The code reads as if all the dissectors were implemented. Though I can only recognize the lowest level of those ITS messages when running said build. Since I am new to dissector development I have no clue as to why it isn't working.

My idea was to implement them myself using an ASN.1 compiler for wireshark (which name I forgot). When I noticed that there already were all the necessary ASN.1 definitions present. A look in the code surprised me with lots of DENM and CAM (between other) references. Though they wouldn't appear in the build.

Does anybody know what's wrong with the code? Is there an issue tracker where I could follow certain dissectors?

Thanks

Why aren't ITS messages supported yet?

Hi there!

Hopefully someone can help me.

In the development builds I can dissect ITS messages to see the message id, which protocol is used (eg. 2 for CAM).

But I cannot see further than that. Higher protocols aren't supported and the data remains a pile of rubbish.

When looking in the source code I would find that there is at least intended support for CAM and DENM.

So my question is: What's the hold up? Why isn't it working yet?

Best regards

PS: I tried several builds on two machines and no configuration could dissect said messages properly.

Edit (27.03.19): I believe I wasn't bringing my point across very well. It's about Wireshark build 3.1.0rc0-190-g41c566b4. The file in question is "epan/dissectors/packet-its.c"

The code reads as if all the dissectors were implemented. Though I can only recognize the lowest level of those ITS messages when running said build. Since I am new to dissector development I have no clue as to why it isn't working.

My idea was to implement them myself using an ASN.1 compiler for wireshark (which name I forgot). When I noticed that there already were all the necessary ASN.1 definitions present. A look in the code surprised me with lots of DENM and CAM (between other) references. Though they wouldn't appear in the build.

Does anybody know what's wrong with the code? Is there an issue tracker where I could follow certain dissectors?

Thanks

Edit (28.03.19): I thank Anders for clearing things up during the exchange of comments. Though while my original question wasn't answered, I'm satisfied with the result. Therefore I close this question.