QLOG is not consistent with what is captured in Wireshark

[tnta2612]

Hi,

I’ve identified an inconsistency between the .qlog files generated by aioquic (client) and what is captured in Wireshark.

When you look at the sequence diagram generated from the .qlog file, it shows that the client first sends a datagram containing a 0-RTT request, then receives a datagram from the (picoquic) server, sends another datagram, and subsequently receives multiple datagrams from the server.

However, in Wireshark, the order of events differs. The client first sends a 0-RTT datagram requesting a resource, then receives multiple datagrams from the server (containing the resource), and only after receiving all the data does the client send its second datagram.

So, in the .qlog sequence, we have:

1. Datagram sent
2. Datagram received
3. Datagram sent
4. Multiple datagrams received

Whereas in Wireshark, the order is:

1. Datagram sent
2. Multiple datagrams received
3. Second datagram sent

These sequences don’t match. Could someone confirm whether this is a bug in the .qlog files generated by aioquic, or if I might be missing something?

Thanks.