[Remy Leone <remy.leone@xxxxxxxx>]

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 10:35 GMT+02:00 Jaap Keuter <jaap.keuter@xxxxxxxxx>:

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 2017, at 09:27, Remy Leone <remy.leone@xxxxxxxx> wrote:
>
> 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 interface or named pipe without troubles for a long time.
>
> Was there any change lately that would have caused that? I got the stable version of Wireshark installed through ubuntu repository/ppa. My user id also belongs to the wireshark group and I can sniff without root priviledges. Could the hanging be caused by that? Is that a classical problem?
>
> Best regards
>
> Rémy
>

> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe