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.

Sign up for GitHub

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

Jump to bottom

PCAP_tools: requests/responses are still not in direct order (under certain circumstances?) #5

Open
Beercow opened this issue Dec 23, 2016 · 2 comments
Open

PCAP_tools: requests/responses are still not in direct order (under certain circumstances?) #5

Beercow opened this issue Dec 23, 2016 · 2 comments
Assignees
@Beercow
Labels
bug WIP

Comments

@Beercow
Copy link
Owner

Beercow commented Dec 23, 2016

2016-12-23_7-55-13
@Beercow Beercow added the bug label Dec 23, 2016
@Beercow Beercow changed the title requests/responses are still not in direct order (under certain circumstances?) PCAP_tools: requests/responses are still not in direct order (under certain circumstances?) Dec 23, 2016
@Beercow Beercow self-assigned this Dec 24, 2016
@Beercow
Copy link
Owner Author

Beercow commented Jan 2, 2017 •
edited
Loading

Appears to be how tcpflow outputs the stream.

@Beercow Beercow added the WIP label Jun 29, 2018
@Beercow
Copy link
Owner Author

Beercow commented Jun 29, 2018

Developing code to eliminate tcpflow as a dependency. Able to order packets correctly. (Not released yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Beercow Beercow

Labels
bug WIP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Beercow