osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Clean up the references to ChUserTable. 

The references read like

	This table is handled by an Section 11.7, "User Table" with the
	following fields.

which looked a little weird.

Change-Id: I4ae9af48e7edf75aa0c7708614f4a11696db9ee1
Reviewed-on: https://code.wireshark.org/review/29530
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2018-09-09 21:25:18 -07:00
parent cba7dfb40b
commit 7ce18dc465
1 changed files with 23 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
docbook/wsug_src/WSUG_chapter_customize.asciidoc
View File

@ -828,9 +828,9 @@ or (ip.src == $2 and ip.dst == $1 and tcp.srcport == $4 and tcp.dstport == $3)
_$$${tcp_conv:10.1.1.2;10.1.1.3;1200;1400}$$_ instead of typing the whole
filter.
Display Filter Macros can be managed with a <<ChUserTable>> by selecting
menu:Analyze[Display Filter Macros] from the menu. The User Table has the
following fields
Display Filter Macros can be managed with a user table, as described in
<<ChUserTable>>, by selecting menu:Analyze[Display Filter Macros] from
the menu. The User Table has the following fields:
Name::
The name of the macro.
@ -844,7 +844,8 @@ The replacement text for the macro it uses $1, $2, $3, ... as the input argument
Wireshark uses this table to map ESS Security Category attributes to textual representations. The values to put in this table are usually found in a link:$$http://www.xmlspif.org/$$[XML SPIF], which is used for defining security labels.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
Tag Set::
An Object Identifier representing the Category Tag Set.
@ -867,7 +868,8 @@ link:https://dev.maxmind.com/geoip/geoip2/downloadable/[available at no
cost], while others require a licensing fee. See
link:http://www.maxmind.com/[the MaxMind web site] for more information.
This table is handled by an <<ChUserTable>> with the following fields.
The configuration for the MaxMind database is a user table, as described
in <<ChUserTable>>, with the following fields:
Database pathname::
This specifies a directory containing MaxMind data files. Any files
@ -895,7 +897,8 @@ IKEv2 packets with this feature. If you want to decrypt IKEv1 packets or ESP
packets, use Log Filename setting under ISAKMP protocol preference or settings
under ESP protocol preference respectively.
This table is handled by an <<ChUserTable>> with the following fields.
This is handled by a user table, as described in <<ChUserTable>>,
with the following fields:
Initiator’s SPI::
Initiator’s SPI of the IKE_SA. This field takes hexadecimal string without
@ -950,7 +953,8 @@ defined X.400 extension). It also allows the user to override the name and
syntax of Object Identifiers that Wireshark does know about (e.g. changing the
name “id-at-countryName” to just “c”).
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
OID::
The string representation of the Object Identifier e.g. “2.5.4.6”.
@ -971,7 +975,8 @@ Wireshark uses this table to map a presentation context identifier to a given
object identifier when the capture does not contain a PRES package with a
presentation context definition list for the conversation.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
Context Id::
An Integer representing the presentation context identifier for which this
@ -988,7 +993,8 @@ protocol that is carried over this association.
Wireshark uses this table to map specific protocols to a certain DPC/SSN
combination for SCCP.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
Network Indicator::
An Integer representing the network indicator for which this association is
@ -1033,7 +1039,8 @@ Wireshark uses this table to map specific-trap values to user defined
descriptions in a Trap PDU. The description is shown in the packet details
specific-trap element.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
Enterprise OID::
The object identifier representing the object generating the trap.
@ -1053,7 +1060,8 @@ The description to show in the packet details.
Wireshark uses this table to verify authentication and to decrypt encrypted
SNMPv3 packets.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
Engine ID::
If given this entry will be used only for packets whose engine id is this. This
@ -1093,7 +1101,8 @@ various protocols that are used by a certain interface. Wireshark doesn’t read
these stk files, it uses a table that helps it identify which lowest layer
protocol to use.
Stk file to protocol matching is handled by an <<ChUserTable>> with the following fields.
Stk file to protocol matching is handled by a user table, as described
in <<ChUserTable>>, with the following fields:
Match string::
A partial match for an stk filename, the first match wins, so if you have a
@ -1113,7 +1122,8 @@ sscop:nbap, ...)
When a pcap file uses one of the user DLTs (147 to 162) wireshark uses this
table to know which protocol(s) to use for each user DLT.
This table is handled by an <<ChUserTable>> with the following fields.
This table is a user table, as described in <<ChUserTable>>, with the
following fields:
DLT::
One of the user dlts.