Re: tshark buffered packet dissection -- no realtime output?

[Guy Harris <guy () alum mit edu>]

On Jan 13, 2018, at 12:45 AM, Ralph Schmieder <ralph.schmieder () inka de> 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.
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe