User Guide

Files and Folders
206
An example is:
# Comments must be prepended by the # sign!
192.168.0.0/24 ws_test_network
A partially matched name will be printed as "subnet-
name.remaining-address". For example, "192.168.0.1" under the
subnet above would be printed as "ws_test_network.1"; if the mask
length above had been 16 rather than 24, the printed address would
be "ws_test_network.0.1".
The settings from this file are read in at program start and never
written by Wireshark.
ipxnets Wireshark uses the files listed in Table A.1, “Configuration files
and folders overview” to translate IPX network numbers into
names.
An example is:
C0.A8.2C.00 HR
c0-a8-1c-00 CEO
00:00:BE:EF IT_Server1
110f FileServer3
The settings from this file are read in at program start and never
written by Wireshark.
plugins folder Wireshark searches for plugins in the directories listed in Table A.1,
“Configuration files and folders overview”. They are searched in
the order listed.
temp folder If you start a new capture and don't specify a filename for it,
Wireshark uses this directory to store that file; see Section 4.8,
“Capture files and file modes”.
A.2.1. Protocol help configuration
Wireshark can use configuration files to create context-sensitive menu items for protocol detail items
which will load help URLs in your web browser.
To create a protocol help file, create a folder named "protocol_help" in either the personal or global
configuration folders. Then create a text file with the extension ".ini" in the "protocol_help" folder. The
file must contain key-value pairs with the following sections:
[database] Mandatory. This contains initialization information for the help file. The
following keys must be defined:
source Source name, e.g. "HyperGlobalMegaMart".
version Must be "1".
location General URL for help items. Variables can be substituted using
the [location data] section below.