[Winpcap-bugs] HAVE_REMOTE counter-intuitively needed

[Gianluca Varenni]

Well, the reason behind that is that pcap_open() is a specific extension to the usual pcap_open_live() supporting (among other things) remote capture. So you need to have the remote capabilities enabled to use that API. And that's the reason why there are two copies of the pktdump_ex sample, one in the examples_pcap (not using pcap_open and the remote extensions, and working on unix as well), and one in examples-remote (using pcap_open and all the other remote capture extensions).

In any case I can add a comment at the beginning of every sample in the examples-remote folder stating that HAVE_REMOTE (as well as WPCAP) should be defined in order to compile such samples.

Have a nice day
GV


----- Original Message ----- 
  From: YG 
  To: winpcap-bugs at winpcap.org 
  Sent: Friday, August 03, 2007 8:36 PM
  Subject: [Winpcap-bugs] HAVE_REMOTE counter-intuitively needed


  When compiling the developer's example pktdump_ex.c I found that the definition of PCAP_SRC_IF_STRING was in the remote-ext.h header, which required the HAVE_REMOTE preprocessor directive.  Not intuitive for an introductory sniffing example why esoteric remote capture capabilities are needed.  Suggest explicitly stating in example code that HAVE_REMOTE needs to be defined. 



------------------------------------------------------------------------------


  _______________________________________________
  Winpcap-bugs mailing list
  Winpcap-bugs at winpcap.org
  https://www.winpcap.org/mailman/listinfo/winpcap-bugs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-bugs/attachments/20070809/28f7513f/attachment.htm