Re: [tcpdump-workers] pcap: forcing pcap_loop() failures

2006-08-16 Thread Gianluca Varenni
I would probably use pcap_next_ex instead of pcap_loop (pcap_next_ex is available on recent versions of libpcap, let's say at least for the last 2-3 years). If you use pcap_next_ex you basically create your own capture loop, and so you can break it whenever you want. GV - Original Messag

Re: [tcpdump-workers] pcap: forcing pcap_loop() failures

2006-08-16 Thread Michael Tuexen
Why not use the 'any' device on Linux? I'm not sure if it will be supported in 2.6.20, but in recent kernels it is :-) Best regards Michael On Aug 16, 2006, at 8:15 PM, Richard H. wrote: Level: pcaplib novice OS: Linux 2.6.20 I've been running a pcaplib app that reads continually from a

[tcpdump-workers] pcap: forcing pcap_loop() failures

2006-08-16 Thread Richard H.
Level: pcaplib novice OS: Linux 2.6.20 I've been running a pcaplib app that reads continually from a network switch port and processes a well-defined application protocol. Let's say the network interface it reads from is 'eth0'. I need to augment this app to handle the failover to a differ