On Jan 10, 2012, at 3:15 PM, Fernando Gont wrote:
> I would expect that if there are no buffers available, pcap_inject() or
> blocks, rather than silently fail.
"Blocks" and "silently fails" aren't the only alternatives; "returns -1 and
sets errno to an error such as ENOBUFS" is a third alterna
On 01/10/2012 07:57 PM, Guy Harris wrote:
>> I'm doing I/O multiplexing with the pcap descriptor, and it turns
>> out that on OpenBSD the underlying descriptor for a pcap_t is never
>> writeable.
>
> I presume from "I'm doing I/O multiplexing" that by "writeable"
> you're referring to "writeable"
On 01/10/2012 05:13 PM, Sam Roberts wrote:
> On Mon, Jan 9, 2012 at 8:49 PM, Fernando Gont wrote:
>> I'm doing I/O multiplexing with the pcap descriptor, and it turns out
>> that on OpenBSD the underlying descriptor for a pcap_t is never writeable.
>> Note: No problems in Linux and FreeBSD -- so f
On Jan 9, 2012, at 8:49 PM, Fernando Gont wrote:
> I'm doing I/O multiplexing with the pcap descriptor, and it turns out
> that on OpenBSD the underlying descriptor for a pcap_t is never writeable.
I presume from "I'm doing I/O multiplexing" that by "writeable" you're
referring to "writeable" a
On Mon, Jan 9, 2012 at 8:49 PM, Fernando Gont wrote:
> I'm doing I/O multiplexing with the pcap descriptor, and it turns out
> that on OpenBSD the underlying descriptor for a pcap_t is never writeable.
> Note: No problems in Linux and FreeBSD -- so far only in OpenBSD.
Are you capturing, or injec
Hi, folks,
I'm doing I/O multiplexing with the pcap descriptor, and it turns out
that on OpenBSD the underlying descriptor for a pcap_t is never writeable.
Note: No problems in Linux and FreeBSD -- so far only in OpenBSD.
Is this the right place to report this? Or should I report this to
OpenBSD
