Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protocol Violation: Not-a-first segmented message received in normal mode #23

Open
mdavidsaver opened this issue Oct 11, 2018 · 1 comment
Assignees
Labels

Comments

@mdavidsaver
Copy link
Member

@shengb reports

when monitoring a big waveform data, for example 3840x2160 image, got error from p2p shell:
2018-10-10T11:32:06.256 Protocol Violation: Not-a-first segmented message received in normal mode from the client at ../../src/remote/codec.cpp:210: 10.10.5.243:5075, disconnecting...

originally mdavidsaver#1

@mdavidsaver mdavidsaver self-assigned this Oct 11, 2018
@mdavidsaver
Copy link
Member Author

mdavidsaver commented Oct 11, 2018

A first pass analysis of a packet capture provided by @shengb shows that a large image payload is triggering the PVA message segmentation logic, which neither the PVA packet dissector nor I understand. This includes the question of why this logic is being triggered when the pixel array is 0x7e9000 bytes (~8MB).

Anyway, this doesn't appear to be the sort of issue that P2P could cause by itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant