Hello There,
We have been using Libpcap 1.1.1 heavily and noticed
something of the following nature. It seems that during a packet read,
internal buffer to read each segment is allocated a size of "snap_len"
bytes. This is okay since we do not know how many bytes will arrive so it
>
>
> > What sort of VMware network card are you using? As far as I remember,
> > VMware simulates either a dec21143 based card (vmlance), an Intel e1000
> > card, or something which is more "paravirtualized" and needs a special
> > driver.
> >
> > This might make a big difference...
>
> Hi,
> What sort of VMware network card are you using? As far as I remember,
> VMware simulates either a dec21143 based card (vmlance), an Intel e1000
> card, or something which is more "paravirtualized" and needs a special
> driver.
>
> This might make a big difference...
Hi,
We have tried on
> > If so , how do we configure it from outside so
> > that we can increase it's size also ?
>
> ...it's irrelevant to the problem you're having. The problem is probably
> that
libpcap, and your program,
> aren't reading packets fast enough, so, given that the socket buffer has a
finite size,
I forgot to mention, we do set a filter (Host IP and TCP Port) on libpcap.
thanks again,
best regards,
Vikram
On Tue, Jan 12, 2010 at 3:08 PM, Vikram Roopchand <
vikram.roopch...@j-interop.org> wrote:
> Hello There,
> This is similar in nature to
> http://ar
Hello There,
This is similar in nature to
http://article.gmane.org/gmane.network.tcpdump.devel/4256 posting (which is
unfortunately unsolved). We are using jnetpcap which is a wrapper over
libpcap. Mark Bednarczyk posted the original query (4256).
-
