From: Cloves Pereira Costa Jr <cloves.costa@m2sys.com.br>
To: sveina@gmail.com
Cc: Linux Net ML <linux-net@vger.kernel.org>,
Linux-Admin ML <linux-admin@vger.kernel.org>
Subject: Re: Dropped packets - tcpdump
Date: Wed, 06 Feb 2008 19:03:22 +0000 [thread overview]
Message-ID: <1202324603.5984.50.camel@wtprcwbti01002> (raw)
In-Reply-To: <221b53ab0802061042x281d8287j61d620bf85e4c09e@mail.gmail.com>
Hi...
My machine is a DELL PowerEdge 2500 with 2 CPU PIII 1 GHz, 2 GB RAM, 250
GB HD SCSI... This configuration is slow?
One more question, the fact that tcpdump drop the packets don't imply
that theese packets are being dropped also in the comunication?
[]s
Cloves
Em Qua, 2008-02-06 Ã s 19:42 +0100, Svein Ove Aas escreveu:
> On Feb 6, 2008 1:07 PM, Cloves Pereira Costa Jr
> <cloves.costa@m2sys.com.br> wrote:
> > Hi all...
> >
> > Anyone knows if there is some way to log the dropped packets in tcpdump?
> > I already search in google for it but didn't find anything...
>
> The reason they're dropped in the first place is that your system is
> too slow to do.. whatever you're doing with them, in realtime, and not
> dropping packets would result in an infinitely growing buffer.
>
> I don't know how you might configure the size of that buffer (a larger
> one /would/ quite possibly help), but if you dump to disk using the -w
> (and -s 0?) parameter, that might help.
>
> Otherwise, get a faster machine. ;)
>
next prev parent reply other threads:[~2008-02-06 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 12:07 Dropped packets - tcpdump Cloves Pereira Costa Jr
2008-02-06 18:42 ` Svein Ove Aas
2008-02-06 19:03 ` Cloves Pereira Costa Jr [this message]
2008-02-08 17:17 ` Svein Ove Aas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202324603.5984.50.camel@wtprcwbti01002 \
--to=cloves.costa@m2sys.com.br \
--cc=linux-admin@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=sveina@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).