You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wireshark reports Entity State PDUs as malformed #11
I am creating Entity State PDUs using in the following manner:
{code}
// Serialize PDU to a big-endian stream
DataOutputStream dataOutputStream = new DataOutputStream(Endian.Big);
Pdu.MarshalAutoLengthSet(dataOutputStream);
// Send bytes
broadcastClient.Send(dataOutputStream.ConvertToBytes())
{code}
Wireshark is reporting that the packets are malformed. I have attached Wireshark packet capture screen shot images. I did notice the Capabilities parameters do not appear in the screenshots. It appears that the MarshalAutoLengthSet is not computing the length properly (143 bytes vs 144 bytes).
@owenfunkhouser I am not aware of a fix for this yet. If you are interested in submitting a PR yes please do. I'll provide a review and help with the merge.
I never got around to fixing it as it did not have any negative effects on our models. I have left this position and no longer am working on simulations and have no access to the code. I did create a DLL that handles both DIS 6 and DIS 7 versions.
I'm using the pdu.ArticulationParameters[i].ParameterValue that doesn't seem to match up with wireshark. I've compared it with other programs too and they seem to agree with wireshark's value. Is there some kind of trick to convert this number in OpenDIS? I thought that was a 64 bit value but it comes out as a double on OpenDIS. Is the 32 other bits just maybe screwing up my numbers?
Wireshark dispalys numbers like -1.5 while I get a number more like -.19
Activity
leif81 commentedon Oct 5, 2021
Thankyou for the report @bamamarc
Are you able and interested in submitting a pull request with a fix?
owenfunkhouser commentedon May 27, 2022
Has a fix been created for this? Otherwise, I will work to create a pull request for this bug as it is affecting a project that I am working.
leif81 commentedon May 28, 2022
@owenfunkhouser I am not aware of a fix for this yet. If you are interested in submitting a PR yes please do. I'll provide a review and help with the merge.
bamamarc commentedon May 30, 2022
I never got around to fixing it as it did not have any negative effects on our models. I have left this position and no longer am working on simulations and have no access to the code. I did create a DLL that handles both DIS 6 and DIS 7 versions.
Schreck425 commentedon Feb 13, 2023
Sorry I don't now where else to ask this.
I'm using the pdu.ArticulationParameters[i].ParameterValue that doesn't seem to match up with wireshark. I've compared it with other programs too and they seem to agree with wireshark's value. Is there some kind of trick to convert this number in OpenDIS? I thought that was a 64 bit value but it comes out as a double on OpenDIS. Is the 32 other bits just maybe screwing up my numbers?
Wireshark dispalys numbers like -1.5 while I get a number more like -.19