On Feb 6, 2014, at 8:13 AM, Michal Sekletar wrote:
> Activated refers to pcap_t handle. Before you can do capture on the device
> you have to have handle and after that capture parameters are set and finally
> handle is marked as activated. So it doesn't refer to status of the device in
> OS.
Y
On Thu, Feb 06, 2014 at 02:36:10AM -0800, Hei Chan wrote:
> Hi,
>
> Thanks for your reply.
>
> I forgot to mention my OS -- CentOS 6.5.
>
> Now, I look at the word "activated", and I am a bit confused.
>
> Does it refer to a device that is enabled in the OS? Or does it refer to a
> device that
Hi,
Thanks for your reply.
I forgot to mention my OS -- CentOS 6.5.
Now, I look at the word "activated", and I am a bit confused.
Does it refer to a device that is enabled in the OS? Or does it refer to a
device that is "activated" by pcap_*() such that even a device is enabled in
the OS but
On Feb 6, 2014, at 12:19 AM, Hei Chan wrote:
> When I call pcap_set_buffer_size() on an actively using/running NIC, it gives
> me an error:
> can't perform operation on activated capture
>
> Is there a way to change the pcap capture buffer size without deactivating it?
On at least some platf
Hi,
When I call pcap_set_buffer_size() on an actively using/running NIC, it gives
me an error:
can't perform operation on activated capture
Is there a way to change the pcap capture buffer size without deactivating it?
How does this buffer different from SO_RCVBUF? It seems like SO_RCVBUF do
