You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had been noodling around the idea of visualizing a QUIC connection similar how qvis does it, but based on a network trace (pcap). My strawman was reading a pcap file, using tshark to parse the packets/frames, and then visualizing things based off that. However, I quickly realized I would need to implement quite a bit of machinery to properly manage the connection state. Almost like a proper QUIC stack...
So that made me wonder whether we could drive a neqo connection by feeding it captured IP payloads from a pcap file, and have it generate a qlog for us, which we then could visualize with the normal qlog tools. Packet I/O and time are (mostly) already not part of neqo, which helps a lot.
We could also compare the packets that neqo generates in response to being fed pcap payloads against what the pcap recorded as a response. Might be useful for regression testing, etc.
The text was updated successfully, but these errors were encountered:
I had been noodling around the idea of visualizing a QUIC connection similar how
qvis
does it, but based on a network trace (pcap). My strawman was reading a pcap file, usingtshark
to parse the packets/frames, and then visualizing things based off that. However, I quickly realized I would need to implement quite a bit of machinery to properly manage the connection state. Almost like a proper QUIC stack...So that made me wonder whether we could drive a neqo connection by feeding it captured IP payloads from a pcap file, and have it generate a qlog for us, which we then could visualize with the normal qlog tools. Packet I/O and time are (mostly) already not part of neqo, which helps a lot.
We could also compare the packets that neqo generates in response to being fed pcap payloads against what the pcap recorded as a response. Might be useful for regression testing, etc.
The text was updated successfully, but these errors were encountered: