Hello,
I've stumbled upon the following problem with master branch of Wireshark:
After a while (around 10 minutes) Wireshark (master) hangs when it's
sniffing on a tun interface or a named pipe.
On the other side, when I use the last stable version of Wireshark (2.2.6)
I can sniff on the same inte
Hi,
You could inspect the bug database, but as far as I know this is not a known
issue.
Your setup seems rather normal, so that should not be cause for any problems.
If you could investigate further into tun / named pipe capture behaviour that
could be interesting.
Thanks,
Jaap
> On 23 May 2
I'm not sure about where to start investigating this issue. Where does the
critical operation happen when wireshark/tshark is sniffing? I suppose that
this is a problem of blocking read/write that is not happening properly but
I'm not sure about how to get started to investigate this.
2017-05-23 1
