QUIC-IETF Filter can't display ack_range
Hi, I have found that wireshark has supported QUIC-IETF analyse. So, I made a test to see if it worked.
And I use ngtcp2 to do quic traffic, the quic-version is quic-draft-27, and record sslkeylogfile, dump flow into pcap file. You can look up to ngtcp2 by refering https://github.com/ngtcp2/ngtcp2
Finally, with wireshark-3.2.3, and configure TLS decrypt pre-master key,I have displayed quic field successfully, for example, it show ack_delay, but it can't print ack_range filed where I find is supported in https://www.wireshark.org/docs/dfref/...
so, my question is why the wireshark can't display ack_range field.
Hope for your reply.
Is
quic.ack.ack_range_count> 0 ?sorry but I can't upload an image, there is the text copy from wireshark below.
It is really strange that both the largest_ack and first_ack_range > 0 , but there is no ack_range
Frame 19: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst: 00:00:00_00:00:00 (00:00:00:00:00:00) Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1 User Datagram Protocol, Src Port: 60867, Dst Port: 443 Source Port: 60867 Destination Port: 443 Length: 60 Checksum: 0xfe4f [unverified] [Checksum Status: Unverified] [Stream index: 0] [Timestamps] QUIC IETF QUIC Connection information [Connection Number: 0] [Packet Length: 52] QUIC Short Header DCID=9af84a6705b6b5b4ebb7bd46724255ead4b2 PKN=1 0... .... = Header Form: Short Header (0) .1.. .... = Fixed Bit: True ..0. .... = Spin Bit: False ...0 0... = Reserved: 0 .... .0 ...(more)
Have you looked through the quic 27 draft?
fine, It my confuse with IETF QUIC, thank you for your reply.