James Walker writes: > Tcpdump is a common packet sniffer that runs under the command line. > It allows the user to intercept and display TCP/IP and other packets > being transmitted or received over a network to which the computer is > attached. Tcpdump works on most Unix-like OS, and uses libpcap library > to capture packets.
What's the point? tcpdump is enough like snoop that it seems to me that there's not a great reason to do this. Instead, it'd be much nicer to see wireshark integrated (which includes a command line tool that's more powerful than either tcpdump *or* snoop), and also have snoop yanked from the product. The time spent here could be better spent elsewhere. > /usr/bin/tcpdump Uncommitted Executable binary file If this just _has to_ be integrated, I think it belongs in /usr/sbin, just like snoop. It's administrative in nature. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
