User Guide

00:00:01 Xerox # XEROX CORPORATION
The settings from this file are read in at program start and
never written by Wireshark.
hosts Wireshark uses the files listed in Table A.1, “Configuration
files and folders overview” to translate IPv4 and IPv6 ad-
dresses into names.
This file has the same format as the usual /etc/hosts file on
Unix systems.
An example is:
# Comments must be prepended by the # sign!
192.168.0.1 homeserver
The settings from this file are read in at program start and
never written by Wireshark.
services Wireshark uses the files listed in Table A.1, “Configuration
files and folders overview” to translate port numbers into
names.
An example is:
mydns 5045/udp # My own Domain Name Server
mydns 5045/tcp # My own Domain Name Server
The settings from this file are read in at program start and
never written by Wireshark.
subnets Wireshark uses the files listed in Table A.1, “Configuration
files and folders overview” to translate an IPv4 address into a
subnet name. If no exact match from the hosts file or from
DNS is found, Wireshark will attempt a partial match for the
subnet of the address.
Each line of this file consists of an IPv4 address, a subnet
mask length separated only by a '/' and a name separated by
whitespace. While the address must be a full IPv4 address,
any values beyond the mask length are subsequently ignored.
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.
Files and Folders
238