Sniffing network to generate a pcap file in CLI mode on a remote host and open it via local Wireshark ( GUI ).

tcpdump -v -i <INTERFACE> -s 0 -w /tmp/sniff.pcap port <PORT> # On the remote side
Then hit ^C to stop, get the file by scp, and you can now use wireshark like this : wireshark /tmp/sniff.pcap If you have tshark on remote host, you could use that : wireshark -k -i <(ssh -l root <REMOTE HOST> tshark -w - not tcp port 22) The last snippet comes from http://wiki.wireshark.org/CaptureSetup/Pipes
Sample Output
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
265 packets captured
265 packets received by filter
0 packets dropped by kernel

5
By: sputnick
2009-12-17 22:08:30

6 Alternatives + Submit Alt

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: