Sake Blok, a Wireshark/Ethereal devotee since 1999, works as a Research & Development Engineer for ion-ip in the Netherlands (http://www.ionip.com) . His company provides solutions to customers who want to deliver their applications to users in a fast, secure, efficient and scalable manner. Sake\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'s main focus is to take new products for a spin in their test environment, design custom solutions for customers and troubleshoot the problems customers might encounter while using ion-ip solutions. Two years ago (2006), Sake started to add the functionality he was missing to Wireshark. He also started to fix Wireshark-bugs that were reported on Bugzilla. This work on Wireshark resulted in an invitation from Gerald Combs to join the Wireshark Core Development Team in 2007.

1. Controlling tsharks displaying behavior October 2008

8. Use a time format of your choice (2) $ tshark -r client.cap -R http -tad 4 2008-09-23 22:31:59.249141 192.168.1.46 -> 192.168.1.20 HTTP G 6 2008-09-23 22:31:59.270476 192.168.1.20 -> 192.168.1.46 HTTP H $ $ tshark -r client.cap -R http -ta 4 22:31:59.249141 192.168.1.46 -> 192.168.1.20 HTTP GET / HTTP/1 6 22:31:59.270476 192.168.1.20 -> 192.168.1.46 HTTP HTTP/1.1 200 $ $ tshark -r client.cap -R http -tr 4 0.002689 192.168.1.46 -> 192.168.1.20 HTTP GET / HTTP/1.0 6 0.024024 192.168.1.20 -> 192.168.1.46 HTTP HTTP/1.1 200 OK $ $ tshark -r client.cap -R http -td 4 0.000589 192.168.1.46 -> 192.168.1.20 HTTP GET / HTTP/1.0 6 0.019966 192.168.1.20 -> 192.168.1.46 HTTP HTTP/1.1 200 OK $ $ tshark -r client.cap -R http -tdd 4 0.002689 192.168.1.46 -> 192.168.1.20 HTTP GET / HTTP/1.0 6 0.021335 192.168.1.20 -> 192.168.1.46 HTTP HTTP/1.1 200 OK $