esrlabs
Parse DLT network-trace prefix for SOME/IP messages
This PR will add information from the DLT network-trace prefix to the resulting SOME/IP information being displayed.
In DLT network-traces for SOME/IP the DLT payload contains of two arguments, where the first argument is a prefix with additional information on the actual SOME/IP message in the the second argument.
For the implementation the prefix will be expected to consist of:
- 4 bytes as IPv4 address
- 2 bytes as udp/tcp port
- 1 byte as protocol type (0 = local, 1 = tcp, 2 = udp)
- 1 byte as message direction (0 = incoming, 1 = outgoing)
- 1, 2 or 4 bytes as SOME/IP instance-id
Requires discussion with @marcmo . In one hand this is not related to Some/IP parser directly and looks like cannot be a part of Some/IP parser; at the same time it's related to DLT parser, but not related to DLT protocol directly; but adding deep parsing operations into chipmunk directly is something, what we didn't do before. Let's discuss it.
@kruss just as a mind. Could it be an optional feature of some of the parsers? Does it make sense?
@kruss just as a mind. Could it be an optional
featureof some of the parsers? Does it make sense?
As it's not related to the protocol specifications of either DLT or SOME/IP it does imo not make sense. Probably this code could be moved to application/apps/indexer/addons in chipmunk?!
Moved the code to parse someip network-trace prefixes to application/apps/indexer/addons/someip-tools