-
Notifications
You must be signed in to change notification settings - Fork 82
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
Replay the packet flow #47
Comments
A working version of this feature is now merged to the Note the following changes to the requested features:
|
The following changes have been made:
|
Now, the replay feature is separated into a panel. The panel has:
The above changes have been merged into the |
This is great. I have been testing it, and it works very well. I am also thinking about adding an export button, so we can export the recorded tcpdump data to a pcap file. This way, we can load it to Wireshark to look at the data more closely. If this is too complicated to implement, you can leave it. |
Here is another suggestion: sometimes, there are multiple simultaneous flows in the events, and they interleave with one another, making it difficult to see which one is which. If we can somehow separate these flows using different colors, that will be great. We can simply use the source and destination IP addresses to roughly identify a flow, and then assign a color to it. This is not a very urgent feature. I am just documenting the thought here. (added) We can just added a Map data structure to the implementation, using src IP and dst IP as the key, while the value will be the color. For each event to be visualized, just look up the color from the Map; if the key does not exists, just add a new entry. So, this does not seem be complicated. |
When we visualize the packet flow, sometimes things happen too fast, and it is very difficult to see the actual flow. I am thinking about the following recording features:
This does not seem to be difficult to implement, what do you think?
The text was updated successfully, but these errors were encountered: