> last year (may and november ?) I already reported about this problem with > pcap > and linux 3.0.x kernels. I did not follow the problem > in depth, however I previously found out that > the pcap method used to send packets by ToDevice > (pcap_inject, not sure but I think so) seems not to be > existing anymore. Therefore, ToDevice (which default method is actually > PCAP) > simply stucks and sends nothing. What I found confusing is that > at the ./configure stage, since pcap_inject is not found within > the pcap library, it is substituted by a dummy method (which does > nothing) and the compilation goes on as if everything was fine. > This can be misleading, and some messages from the stdout > would be helpful, since the problem can then be determined only > by examining the (long) configure.log file.
I don't have this problem when built the latest libpcap and linux 3.6. I'm still using pcap_inject(). I think the behavior you describe occurs when you pass a bad libpcap path to ./configure. _______________________________________________ click mailing list click@amsterdam.lcs.mit.edu https://amsterdam.lcs.mit.edu/mailman/listinfo/click
