Wireshark-users: Re: [Wireshark-users] tshark buffered packet dissection -- no realtime output?
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Sat, 13 Jan 2018 18:34:34 -0800
On Jan 13, 2018, at 12:45 AM, Ralph Schmieder <ralph.schmieder@xxxxxxx> wrote:

> But no, it's the same result. In fact, I used that option in curl (and also tried with stdbuf -o0). Would have been surprised if the results were different since the "-i -" does deliver the packets in / close-to real-time which seems to proof that the issue is not buffering in curl but in tshark.

Yes, it's buffering in tshark, but it's *input* buffering, not *output* buffering, so it has the same behavior as if curl were buffering *its* output in 4096-byte chunks.