On Apr 15, 2017, at 7:10 PM, Andrew Lunn 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 do
On Sat, Apr 15, 2017 at 06:45:36PM -0400, Sowmini Varadhan wrote:
> On (04/15/17 21:40), Andrew Lunn wrote:
> >
> > In my case, lan3 is up and idle, there are no packets flying around to
> > be captured. So i would expect pcap_next_ex() to exit once a second,
> > with a return value of 0. But it i
