[tcpdump-workers] Re: capture and inject device capabilities in libpcap

2024-12-01 Thread Denis Ovsienko
On Mon, 18 Nov 2024 12:30:22 -0800 Guy Harris wrote: > On Nov 18, 2024, at 11:54 AM, Denis Ovsienko > wrote: > > > The current approach in libpcap is such that an application at some > > point tries to activate a device, and if the device does not support > > capturing packets, pcap_activate()

[tcpdump-workers] Re: capture and inject device capabilities in libpcap

2024-11-18 Thread Guy Harris
On Nov 18, 2024, at 12:15 PM, Michael Richardson wrote: > Denis Ovsienko 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_findall

[tcpdump-workers] Re: capture and inject device capabilities in libpcap

2024-11-18 Thread Guy Harris
On Nov 18, 2024, at 11:54 AM, Denis Ovsienko wrote: > The current approach in libpcap is such that an application at some > point tries to activate a device, and if the device does not support > capturing packets, pcap_activate() fails with the > PCAP_ERROR_CAPTURE_NOTSUP error code. One drawbac

[tcpdump-workers] Re: capture and inject device capabilities in libpcap

2024-11-18 Thread Michael Richardson
Denis Ovsienko 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