11.22. Protobuf UDP Message Types
Prev | Chapter 11. Customizing Wireshark | Next

## 11.22. Protobuf UDP Message Types

If the payload of UDP on certain ports is Protobuf encoding, Wireshark use this table to know which Protobuf message type should be used to parsing the data on the specified UDP port(s).

The configuration for UDP Port(s) to Protobuf message type maps is a user table, as described in Section 11.7, “User Accessible Tables”, with the following fields:

UDP Ports
  The range of UDP ports. The format may be "8000" or "8000,8008-8088,9080".
Message Type
  The Protobuf message type as which the data on the specified udp port(s) should be parsed. The message type is allowed to be empty, that means let Protobuf to dissect the data on specified UDP ports as normal wire type without precise definitions.

Tips: You can create your own dissector to call Protobuf dissector. If your dissector is written in C language, you can pass the message type to Protobuf dissector by `data` parameter of call_dissector_with_data() function. If your dissector is written in Lua, you can pass the message type to Protobuf dissector by `pinfo.private["pb_msg_type"]`. The format of `data` and `pinfo.private["pb_msg_type"]` is

        "message," message_type_name

For example:

        message,helloworld.HelloRequest

the `helloworld` is package name, `HelloRequest` is message type.

Prev | Up | Next
11.21. Protobuf Search Paths | Home | Chapter 12. MATE