Dear wireshark developers,
the other problem I have with MATE is that for some protocols/dissectors
I don't seem to be able to extract wireshark fields into MATE attributes.
Like in the last e-mail, I'm again working with the following MATE config
https://git.osmocom.org/wireshark-mate/tree/osmocom.mate
This time, I'm looking at MGCP traces. The MATE config states:
---
Pdu mgcp_pdu Proto mgcp Transport udp/ip {
Extract ip_addr From ip.addr;
Extract port From udp.port;
Extract mgcp_rsp_code From mgcp.rsp.rspcode;
Extract mgcp_verb From mgcp.req.verb;
Extract mgcp_endpoint From mgcp.req.endpoint;
Extract mgcp_conn_id From mgcp.param.connectionid;
Extract mgcp_spec_endp_id From mgcp.param.specificendpointid;
};
---
For some strnge reason, none of the mgcp.* fields are ever passed into MATE
attributes.
Attached is again a pcap file for your reference. In none of those
packets, MATE extracts the named fields as attributes. I've checked the
field names several times, and they are correct. Why are they not added
to 'mgcp_pdu Attributes'?
Like the previous topic, I'm not reporting this as a bug as of yet, as
I'm not sure it is a bug or I'm stimply not able to use MATE as
expected.
Thanks in advance.
Regards,
Harald
--
- Harald Welte <laforge@xxxxxxxxxxxx> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Attachment:
mgcp.pcap
Description: application/vnd.tcpdump.pcap
Attachment:
mgcp.png
Description: PNG image
