|
Wireshark won't search on windows 10 when I hit control+f. I then type in datr have string and packet details selected. I hit find and it won't search. The find box just sits there. Anyone know why? |
This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
You have a trillion packets.
You need to see four of them.
Riverbed Technology lets you seamlessly move between packets and flows for comprehensive monitoring, analysis and troubleshooting.
Riverbed is Wireshark's primary sponsor and provides our funding.
Question tags:
question asked: 28 Aug '15, 15:25
question was seen: 2,929 times
last updated: 29 Aug '15, 10:33
Related questions
powered by OSQA
You have direction set to 'up'. Does changing it to 'down' helps? Are you sure you have a packet that contains the 'datr' string? I do not have any search issue on my Windows 10 PC when running Wireshark 1.12.7.
Thanks Pascal,
I ended up trying http.cookie contains datr in the filter box and that worked. I couldn't find any cookies so I probably have something setup wrong not sure.