User Guide

Files and Folders
216
c0-00-ff-ff-ff-ff TR_broadcast
00.2b.08.93.4b.a1 Freds_machine
The settings from this file are read in at program start and never
written by Wireshark.
manuf Wireshark uses the files listed in Table A.1, “Configuration files
and folders overview” to translate the first three bytes of an Ethernet
address into a manufacturers name. This file has the same format
as the ethers file, except addresses are three bytes long.
An example is:
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 addresses 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.