Now, one other nice thing that I can do,
I'm just going to remove this display filter,
another nice thing that Wireshark does for me is that
allows me to filter on a single QUIC stream.
So over here, in my information,
we remember that QUIC support streams almost like lanes on a highway,
right?
So here, I can see that here's the STREAM setup.
I have STREAM(2), STREAM(6), I have, in the opposite direction,
I have STREAM(3).
So if I just want to filter on a single stream,
first, I can see what streams are active,
so here, I've got STREAM(0), there's some data coming across.
If I come down, I also see STREAM(4) has some stuff.
So let's go ahead and right‑click one of these streams.
Let's just take a look at packet number 4.
I'm going to right‑click, and if I come down here to Follow,
that will allow me to filter on the QUIC stream itself.
So if I click that, now just like Follow TCP Stream,
it'll first extract any clear text out of that stream that it can,
and it'll put it all together for me here in the stream data.
And for right now, I'm just going to come down here to Close.
What I want to do is come back here to my display filter,
and here, I can see the filter that Wireshark set for me,
quic.connection.number eq 0, so it's just the first QUIC connection in the trace,
and then I see quic.stream and stream_id eq 0,
so this is where I could change that to 4,
5, 6, any of the streams that are in this QUIC connection.
Now, you'll notice in this trace file, I have a filter here set on STREAM(0).
But I also see other stream data in certain packets.
So, for example, in packet 28,
if I select that and I come down to my detail view,
I also have other streams here.
It's not just STREAM(0).
So this QUIC packet, it has 3 streams, and here,
I have Stream ID: 7, Stream ID: 11, but I also see Stream ID: 0.
So if a QUIC packet contains any information for Stream
ID: 0, that will be displayed. Now, why is this useful?
Because now,
instead of just looking at Packet Number, I also can come over here
and start to look at my delta times, and this might be where I start
to see my network round trip. I see a request that might have gone out
to the server, I'm looking at responses and how long that took to come
back on that stream,
and that will give me a better measurement of something
more like an application transaction.
So right now, with the Wireshark analyzer,
those are just a few things that we can look at in a QUIC stream.
As QUIC continues to mature,
I'm sure we're going to start to see more features within Wireshark, so
maybe things like specific HTTP/3 options or features, and even more with
the ability to graph QUIC streams, and so on.
But now, at least, even without the session key,
we can still see our network round‑trip time, and with the session key,
we can take a look at our packet numbers to see where packet loss happens along the stream.