Thanks, this'll be interesting. One of my first go-tos in Wireshark is finding the interesting hosts I'm looking for, then using the built-in Follow TCP Stream to go deeper.
I wonder if tcpflow would make this easier, or maybe just different, by effectively pre-slicing the capture into sessions.
`tshark` (from wireshark) sounds like a similar tool with pretty good protocol support (IIRC, it has been a long time since I've used it).
By example:
https://hackertarget.com/tshark-tutorial-and-filter-examples...
I've been using tcpick for a similar purpose to see if a HTTP request is reaching and not blocked elsewhere and to see the raw communication to check on headers.
Re:Getting Started with NMAP
by whatbackup on Monday December 19, 2022 @02:55AM
(#34049608)
Not too familiar with tcpflow, thanks for your short write-up. Going to check it out.
Re:Getting Started with NMAP
by jamal-kumar on Monday December 19, 2022 @02:21PM
(#34056372)
Flow analysis is such an essential skill that I'm surprised more people aren't on that tip. It's just so useful
What does it do?
It can reassemble TCP packets back into the FULL body of the original message sent. e.g. if you make a HTTP GET request, it will show you the full text in a file stamped with the time, source and dest ips and port.
Things I've found it REALLY useful for:
- migrating a data center
- for some reason, connection works fine on the old DC but seems to time out in weird ways in the new DC
- No one can figure it out
- I suggest using tcpflow
- Turn out there was a setting in the new DC network hardware that was truncating larger packets and the authorization message was just over the threshold
People always say "yeah, but Wireshark" which is true, that's a good tool too. That being said, there is just something about seeing the "raw" text of a message sent by a machine over the wire and being able to see it in text from the command line.
https://github.com/simsong/tcpflow