On Jan 16, 2012, at 2:20 PM, Fernando Gont wrote:
> Both on Linux and on BSDs, each time a packet is received, select()
> returns readable (without waiting for the entire buffer to fill up). --
> my understanding is that you were expecting select() to block till the
> buffer filled up, or when th
Hi, Guy,
On 01/16/2012 05:25 PM, Guy Harris wrote:
>>> If you have a system where select() works as it should, i.e.:
>> []
>>> select() will block until either
>>>
>>> 1) a bufferful of packets arrives
>>>
>>> or
>>>
>>> 2) the timer, started when the select() is done, expires,
>>> regardle
On Jan 16, 2012, at 6:58 AM, Fernando Gont wrote:
> On 01/15/2012 08:56 PM, Guy Harris wrote:
>>> For my current app, it's probably just "annoying" (although no big
>>> deal). However, I was mostly concern about performance problems in
>>> other applications. Put another way, if there's nothing
On Jan 16, 2012, at 5:55 AM, Shalom Kramer wrote:
> But I seem not to be able to filter by the underlying tcp properties. For
> instance:
>
> *tcpdump ** -r http_over_ipv6_with_options.pcap* *"ip6 protochain \tcp and
> port 80"
>
> *Will return only the packets without the optional IPv6 headers
On 01/15/2012 08:56 PM, Guy Harris wrote:
>> For my current app, it's probably just "annoying" (although no big
>> deal). However, I was mostly concern about performance problems in
>> other applications. Put another way, if there's nothing that an app
>> can do without a packet being read, there'
I checked out the new 1.2.1 release and yes, it's working.
Thanks!
But I seem not to be able to filter by the underlying tcp properties. For
instance:
*tcpdump ** -r http_over_ipv6_with_options.pcap* *"ip6 protochain \tcp and
port 80"
*Will return only the packets without the optional IPv6 heade
