pcap Timestamps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hello there,
you have made a great code.
I found a few bugs
1-st one is - when using tshark and log USB traffic to a file and then tshark quits, there is still a python process that runs on the background and have to kill it manually
2-nd one is - timestamps of packets are completely wrong ? everything starts from 0:00:00 . I know that Beagle starts from 0:00:00 when used but we can always set a local timestamp not the one from the beagle ? I do not know how to set timestamp to be set in the pcap files locally instead of getting timestamp from beagle ? Any suggestion ? look at the code , found --ts but cannot figure out how to modify your python script so that it creates timestamp in pcap file according to computer running the tshark
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Python script used with tshark for USB capture and the handling of the --ts option. Reproduce both the lingering Python process after tshark exits and the pcap timestamps starting at 0:00:00. Done means the process exits cleanly and the pcap records use the requested local computer timestamp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100