Revision history [back]

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 not can't print ack_range where I find is supported in https://www.wireshark.org/docs/dfref/q/quic.html

so, my question is why the wireshark can't display ack_range field.

Hope for your reply.

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 not can't print ack_range filed where I find is supported in https://www.wireshark.org/docs/dfref/q/quic.html

so, my question is why the wireshark can't display ack_range field.

Hope for your reply.