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

Bug in live version: Trace containing two connections are missmapped #5

Open
janrueth opened this issue Mar 24, 2020 · 4 comments
Open

Comments

@janrueth
Copy link

Describe the bug
It seems that QVIS does not properly handle two connections in the same trace.
A second connection seems to be mapped to the first connection and, e.g., initial frames are interpreted as retransmission (see attached screenshot). It also lacks all answers from the second connection.

To Reproduce

Expected behavior
Not mixing up two connections into one sequence. I suggest having a connection drop down menu that allows selecting a connection from a trace.

Screenshots
image

@rmarx
Copy link
Member

rmarx commented Mar 24, 2020

Hello Jan,

Thanks for reporting. This (and the other issue) are more issues with our pcap2qlog tool than qvis itself, but when using qvis directly from quictracker that's of course abstracted out for the end user.

This one especially seems like a weird one, so having a reproducible source will definitely come in handy, thanks!

@janrueth
Copy link
Author

Hi Robin,

ah okay that was not obvious to me.
Do you want me to file the bug report with pcap2qlog?

@rmarx
Copy link
Member

rmarx commented Mar 24, 2020

Hello Jan,

No, sorry that wasn't clear. I mainly wanted to make it clear that if you have a "proper" qlog (e.g., exported from an implementation directly) instead of a transformed pcap, that qvis itself should handle that just fine (in case you want to test or use qvis in alternate ways).

Since I'm the primary maintainer across all these projects, it doesn't really matter where the issues are filed atm :)

@janrueth
Copy link
Author

ah, got it!

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

No branches or pull requests

2 participants