aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors
AgeCommit message (Collapse)AuthorFilesLines
2023-02-28RTPS: make a function staticMartin Mathieson1-0/+1
2023-02-28UDS: cleanup structureDr. Lars Völker1-82/+39
Remove ETTs that do not match the standard.
2023-02-27[Automatic update for 2023-02-26]Gerald Combs1-5/+2279
Update manuf, services enterprise numbers, translations, and other items.
2023-02-27ppp: Reset conversation elements between each frame in raw HDLC streamJohn Thacker1-0/+24
When breaking up a raw HDLC byte stream into frames, each frame should be treated separately, much like it were a new frame in an ordinary capture file. That means that many of the elements in the big packet_info struct should be reset for each new frame. In particular, the "most recent conversation" information stored in conv_elements and conv_addr_port_endpoints should be reset. This is not that different to how multiple PDUs should be handled in some other protocols (DVB-S2, TCP, etc.). When a frame contains protocol layers A, B, then C, we should distinguish between "C is contained within B within A" and "C and B are consecutive PDUs both contained within A." Unfotunately, it's difficult to handle this in a general way, as we don't know when calling the dissector for a PDU whether another PDU will follow or not. If something is the last PDU, we don't want to reset the last addresses/ports/conversation, so that we can access them for display purposes, conversation filters, the related packets line, follow stream, etc., many of which use find_conversation_pinfo Fix #18278.
2023-02-26UDS: fix WDBI assertDr. Lars Völker1-7/+10
2023-02-26UDS: Fixing dissector bugs (tvb_bytes_to_str_punct with 0 length)Dr. Lars Völker1-9/+12
This patch fixes 3 bugs where tvb_bytes_to_str_punct length was not checked. Fixes: #18865
2023-02-26ORAN FH CUS: Add section extension type 2Martin Mathieson1-1/+192
2023-02-25NR-RRC: Fix assign instead of comparisonJohn Thacker2-8/+8
This is mean to use the value to select the correct field length. Fix Coverity CID 1517107, 1517124, 1517136, 1517164, 1517184, 1517195.
2023-02-25Fix item length in ASN.1 templates tooJohn Thacker2-2/+2
Some of the item length changes in !9655 needed to be done with the ASN.1 templates so that they don't get lost on ASN.1 regeneration. Fixup ed8ee831fda2df69657af95dc34a3ea6b3ef4c88
2023-02-25ORAN FH CUS: add section extensions 16, 17, 18, 21Martin Mathieson1-5/+117
2023-02-25Change some `wmem_packet_scope()` to `pinfo->pool`David Perry18-265/+266
As requested [here][1] by @eapache, help with removing calls to `wmem_packet_scope()` in favour of references to `pinfo->pool`. * Plugins chosen semi-randomly. * When a calling function already has a `pinfo` argument, use that. * Remove `_U_` from its signature if it was there. * If a function seems narrowly focused on getting and (possibly) returning memory, change the function signature to take a `wmem_allocator_t *`. * If it seems more focused on packet-based operations, pass in a `packet_info *` instead and use `pinfo->pool` within. * If there are several functions defined with the same call signature, add `pinfo _U_` to the argument list of similar functions in order to maintain clarity/symmetry. [1]: https://www.wireshark.org/lists/wireshark-dev/202107/msg00052.html
2023-02-24TECMP: Changing voltage from string to doubleDr. Lars Völker1-3/+4
2023-02-24ORAN FH CUS: Add ext20Martin Mathieson1-4/+122
2023-02-24UDS: Fixing names of RDTCI subfunctions 0x0b-0x0eDr. Lars Völker1-2/+6
This fixes the dissection of RDTCI subfunction. Fixes: #18873
2023-02-24fix conflictAlexis La Goutte2-2/+2
2023-02-24PTP: Fix wrap around issue in PTP analysis codeDr. Lars Völker1-19/+34
The PTP analysis code did not support very long traces, in which the PTP seqid wrapped around (~2.27 hours with 125ms intervals). This is fixed by ensuring that PTP messages are only matched, if less than 60s apart. Fixes: #18872
2023-02-24Fix more warnings from tools/check_typed_item_calls.pyMartin Mathieson13-113/+114
2023-02-24protobuf: fix typoAlexis La Goutte1-1/+1
mssage => message
2023-02-24protobuf: Fix Clang Warning AnalyzerAlexis La Goutte1-2/+1
line 764: Value stored to 'subtree' is never read
2023-02-23TECMP: Fix voltage representation in vendor dataDr. Lars Völker1-1/+1
Fixes: #18871
2023-02-23TLS: use macros for GREASE checksDavid Perry1-7/+16
The tests in `packet-tls-utils.c` for GREASE values aren't strictly correct, in that they would falsely ignore a value such as 0x1a2a. Create a macro to replace this test, which also serves to document the intent of the test to future developers. Also create a macro for the reserved values of QUIC transport parameters which serve a similar function as GREASE.
2023-02-22file-pcapng-darwin: fix Dead Store found by Clang AnalyzerAlexis La Goutte1-1/+0
2023-02-22Fix Wi-SUN LBS-IE dissectorMathis Marion1-1/+1
2023-02-22RTPS: Improving support queries dissectionismaelrti1-52/+161
- Added topic name (tq) suffix in the column information. - Added topic query kind field dissection - Added filter for last and intermediate DATA_SESSION submessages
2023-02-22CIP: Improve connection analysisDylan Ulis2-27/+82
2023-02-21RDMnet: Bug FixesJim Schaettle1-0/+2
- Endpoint List Get Response - Endpoint Responders Get Response
2023-02-21BBLog: Add support for PRU eventsMichael Tuexen2-3/+75
While there, fix also the reporting of unknown types or events of timers.
2023-02-21file-pcapng: fix might be clobbered by ‘longjmp’ or ‘vfork’ ↵Joakim Karlsson1-1/+1
[-Werror=clobbered]
2023-02-21Diameter 3GPP: update some Rx related AVPsPascal Quantin1-7/+131
2023-02-21BBLog: Update event typesMichael Tuexen1-2/+6
2023-02-21BBLog: Improve handling of timer eventsMichael Tuexen2-2/+45
2023-02-20gmr1_rr: try to explain the 0x100 hack.Guy Harris1-3/+67
I leave it to those more familiar with the protocol to explain this better or in more detail and, if possible, to come up with a better way of doing this.
2023-02-21RSVP: Add missing S2L_SUB_LSP filter.Martin Stigge1-0/+13
Now S2L_SUB_LSP objects shows up as "rsvp.s2l_sub_lsp" instead of "rsvp.obj_unknown".
2023-02-20BBLog: Prepare for event type specifc info columnMichael Tuexen1-1/+16
While there, improve the handling of unknown event types.
2023-02-20BBLog: Display BBLog information for IN/OUT eventsMichael Tuexen1-2/+631
2023-02-20ieee80211: Fix Short SSID encodingsJosh Schmelzle1-2/+2
Change ENC_NA to ENC_LITTLE_ENDIAN for following Short SSID items: - hf_ieee80211_ff_fils_discovery_short_ssid - hf_ieee80211_short_ssid
2023-02-20Check that value_string values fit into field widthMartin Mathieson13-21/+25
2023-02-19USBLL: End transfer reassembly on STALLTomasz Moń1-57/+231
Some classes, most notably Mass Storage, use STALL (instead of ZLP) to prematurely end transfer. Finish reassembly when dissecting STALL. For IN transfers ending reassembly is pretty straightforward and resembles ZLP packet. For OUT transfers the reassembled URB is opposite direction than the STALL handshake itself and last data packet may not be part of reassembled URB. The last OUT data packet is part of reassembled URB only if packet was acknowledged with NYET before endpoint was STALLed.
2023-02-19bblog: show textual errno valuesMichael Tuexen2-1/+210
2023-02-19bblog: improve TCP state namesMichael Tuexen1-7/+7
Use the names from RFC 9293 for consistency.
2023-02-19RTPS: Restore timestamp present flagJohn Thacker1-1/+1
Fix: Unused href entry: epan/dissectors/packet-rtps.c: hf_rtps_flag_timestamp_present created from e93f42350400687800262925839fb14f40ab234b
2023-02-19btlmp: Fix order of name offset and length fieldsGulshan Singh1-2/+2
According to the Bluetooth Core Specification v5.3, Volume 2, Part C, Section 5.1, the Name_Offset parameter of the LMP_NAME_RES PDU should be at offset 2 in the payload and Name_Length should be at offset 3.
2023-02-16ORAN FH CUS: support section extension type 13Martin Mathieson1-28/+115
2023-02-16MySQL: LOCAL INFILEDaniël van Eeden1-10/+70
2023-02-16packet-netlink-net_dm: try to guess the payload typeLaurent Fasnacht1-6/+30
The kernel unfortunately doesn't indicate which payload type it is. In particular, it might be an Ethernet packet or an IP one, depending on how the SKB has been generated. We work around this issue by guessing if the packet contains the EtherType at the right offset to be an Ethernet packet, and decode accordingly the payload.
2023-02-16packet-netlink-net_dm: add support for NET_DM_ATTR_REASONLaurent Fasnacht1-0/+12
2023-02-15ORAN FH CUS: Fix filter from previous commit.Martin Mathieson1-59/+47
2023-02-15JDWP: Update dissector up to Java 19Eugène Adell1-0/+25
2023-02-15ORAN FH CUS: Handle section extension 19Martin Mathieson1-47/+244
2023-02-15TCP: Don't clear REASSEMBLE_ENTIRE_SEGMENT if we didn't completeJohn Thacker1-1/+1
If MSP_FLAGS_REASSEMBLE_ENTIRE_SEGMENT is set (because the dissector asked for one more segment) but the new segment didn't result in a completed reassembly (because it overlapped and didn't add new data), don't clear the REASSEMBLE_ENTIRE_SEGMENT flag. Related to #18411
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-21 06:30:07 +0000