The amount of resources Wireshark needs depends on your environment and on the size of the capture file you are analyzing. The values below should be fine for small to medium-sized capture files no mor than a few hundred MB. Larger capture files will require more memory and disk space.
|Busy networks mean large captures|
Working with a busy network can easily produce huge capture files. Capturing on a gigabit or even 100 megabit network can produce hundreds of megabytes of capture data in a short time. A fast processor, lots of memory and disk space is always a good idea.
If Wireshark runs out of memory it will crash. See http://wiki.wireshark.org/KnownBugs/OutOfMemory for details and workarounds.
Although Wireshark captures packets using a separate process the main interface is single-threaded and won’t benefit much from multi-core systems.
A supported network card for capturing
Older versions of Windows which are outside Microsoft’s extended lifecycle support window are no longer supported. It is often difficult or impossible to support these systems due to circumstances beyond our control, such as third party libraries on which we depend or due to necessary features that are only present in newer versions of Windows (such as hardened security or memory management).
Wireshark 1.10 was the last release branch to officially support Windows XP. Wireshark 1.2 was the last branch to support Windows 2000. See the Wireshark release lifecycle page for more details.
Wireshark currently runs on most UNIX platforms. The system requirements should be comparable to the Windows values listed above.
Binary packages are available for most Unices and Linux distributions including the following platforms:
If a binary package is not available for your platform you can download the source and try to build it. Please report your experiences to wireshark-dev[AT]wireshark.org.