Hi,
Expected, yes. Linux's packet capture mechanism doesn't have the timeouts
that the WinPcap driver, BPF, etc. do.
I thought (and i have a programm running with this) that you can use the
to_ms value in pcap_open_live() to set such a timeout. The value won't be
interpreted by some OS'ses
If pcap_breakloop() is called in a signal handler, and the signal in
question isn't set up to restart system calls, that should
let the loop terminate cleanly. If it's not called in a signal
handler, i.e. if there's no signal that was delivered to the process,
that won't help.
Can I
On Jun 24, 2006, at 10:50 PM, Richard Hansen wrote:
I have one thread that sits in pcap_loop() and another thread that
calls pcap_breakloop() when it is time to shut down. My code works
well on Windows (WinPcap 3.1).
Well, sort of. I suspect that pcap_breakloop() doesn't *immediately*
Hi all,
I have one thread that sits in pcap_loop() and another thread that calls
pcap_breakloop() when it is time to shut down. My code works well on Windows
(WinPcap 3.1). On Linux (libpcap 0.9.4, kernel 2.6.16) the pcap_loop() doesn't
return after calling pcap_breakloop() until another