Mac OS X v10.5, 10.6: How to capture a packet trace

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Mac OS X v10.5, 10.6: How to capture a packet trace
# 1  
Old 01-13-2010
Mac OS X v10.5, 10.6: How to capture a packet trace

In this advanced article, learn how to capture a packet trace; for example, you may be asked to do this when troubleshooting a network connectivity issue. These steps use Terminal and the the tcpdump command; if you are not familiar with using the Terminal, you may want to use for third-party software that can perform a packet trace instead.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
TRACE(1)						    BSD General Commands Manual 						  TRACE(1)

NAME
trace -- configure and record kernel trace events SYNOPSIS
trace -h trace -i [-b numbufs] trace -g trace -d [-a pid | -x pid] trace -r trace -n trace -e [-c class [-p class] [-s subclass]] [-a pid | -x pid] [-k code | -k code | -k code | -k code] trace -E [-c class [-p class] [-s subclass]] [-a pid | -x pid] [-k code | -k code | -k code | -k code] executable_path [optional args to executable] trace -t [-R rawfile] [-o OutputFilename] [-N] [ExtraCodeFilename1 ExtraCodeFilename2 ...] DESCRIPTION
The trace command allows developers to initialize and configure the kernel trace subsystem. Trace events can be recorded to an in-memory buf- fer, or logged directly to a file. Raw data files can later be decoded to a plaintext format. SEE ALSO
fs_usage(1), sc_usage(1), latency(1), top(1) Mac OS X October 28, 2010 Mac OS X