Re: capture and inject device capabilities in libpcap

[Michael Richardson <mcr () sandelman ca>]

Denis Ovsienko <denis () ovsienko info> wrote:
    > One complication here is that in some cases libpcap may not be aware of
    > a device capability until it gets an error from the OS (as is the case
    > with PCAP_ERROR_CAPTURE_NOTSUP in pcap-linux.c), so pcap_findalldevs()
    > would not be able to set "this device can capture" and "this device can

Are there any operating systems can provide this info?
Maybe this becomes an upstream (Kernel) request.

    > inject" flags reliably.  So it seems to make more sense to declare what
    > would certainly *not* work, such as:

    > PCAP_IF_NO_CAPTURE -- capture is guaranteed not to work
    > PCAP_IF_NO_INJECT -- inject is guaranteed not to work

Yeah, that sounds reasonable for now.

_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers () lists tcpdump org
To unsubscribe send an email to tcpdump-workers-leave () lists tcpdump org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s