Re: [tcpdump-workers] libpcap on Mac Os X 10.6 Snow Leopard

2010-02-10 Thread Marco De Angelis
Guy Harris alum.mit.edu> writes: > Your code snippet shows pcap_dispatch() being called at the > beginning of a "loop forever" loop, so I presume you're not > doing a select() to wait for packets to arrive (that has a problem > in older versions of *BSD and still has a problem in OS X). So the

Re: [tcpdump-workers] libpcap on Mac Os X 10.6 Snow Leopard

2010-02-10 Thread Marco De Angelis
Carter Bullard qosient.com> writes: > > Hey Marco, > This may help you if you are not doing it. It seemed to help me on > Snow Leopard. Carter, thank you so much! It works nicely with this addition. I understand that BIOCIMMEDIATE changes the behaviour and avoids buffering, therefore I will

Re: [tcpdump-workers] libpcap on Mac Os X 10.6 Snow Leopard

2010-02-10 Thread Guy Harris
On Feb 9, 2010, at 2:15 AM, Marco De Angelis wrote: > I made an interesting test. > By collecting pcap_stats() after every call to pcap_dispatch and > printing the pcap_stat values out, I could verify that the packets > are received. > E.g. if I filter for ICMP packets, by launching "ping" com

Re: [tcpdump-workers] pcap_inject()

2010-02-10 Thread Guy Harris
On Feb 9, 2010, at 10:20 PM, Frank W. Miller wrote: > I'm getting the feeling that pcap_inject() isn't well supported? I guess it's a question of which code we're talking about in the code path to the hardware. pcap_inject() - like the rest of libpcap - is implemented atop an underlying mecha