| Bug ID |
9167
|
| Summary |
Non standard RTPS dissection over TCP
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Current SVN HEAD.
--
In packet-rtps.c there is code to support dissecting RTPS over TCP. How this
works is not yet standardised. There are several proposals currently under
evaluation at the OMG. The dissector has been modified to assume a 4 byte
packet
length is added to the RTPS header when sent over TCP. As this mechanism is non
standard I think it should be removed from the dissector until the standard is
agreed.
We (PrismTech) have proposed supporting TCP with an additional sub-message
type. I am supporting this with our own custom patch to the dissector, until
the TCP support mechanism is agreed think everyone (implementing RTPS over TCP)
should take the same approach.
The existing TCP support (search for "is_tcp" in the code - two occurrences)
should either be removed or modified to depend on the vendor code of whoever
is supporting TCP in this way.
You are receiving this mail because:
- You are watching all bug changes.
