On Apr 15, 2017, at 7:10 PM, Andrew Lunn <and...@lunn.ch> wrote: > Do you think this is a kernel problem, libpcap problem, or an > application problem?
An application problem. See my response on netdev; the timeout (which is provided by the kernel's capture mechanism, in most cases) is to make sure packets don't stay stuck in the kernel's packet buffer for an indefinite period of time, it's *not* to make sure a thread capturing packets doesn't stay blocked for an indefinite period of time. Whether the timer goes off even if no packets have arrived is platform-dependent; code capturing packets should neither depend on it doing so or on it not doing so.
