From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cloves Pereira Costa Jr Subject: Re: Dropped packets - tcpdump Date: Wed, 06 Feb 2008 19:03:22 +0000 Message-ID: <1202324603.5984.50.camel@wtprcwbti01002> References: <1202299652.5984.17.camel@wtprcwbti01002> <221b53ab0802061042x281d8287j61d620bf85e4c09e@mail.gmail.com> Reply-To: cloves.costa@m2sys.com.br Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <221b53ab0802061042x281d8287j61d620bf85e4c09e@mail.gmail.com> Sender: linux-net-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: sveina@gmail.com Cc: Linux Net ML , Linux-Admin ML Hi... My machine is a DELL PowerEdge 2500 with 2 CPU PIII 1 GHz, 2 GB RAM, 25= 0 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 =C3=A0s 19:42 +0100, Svein Ove Aas escreveu: > On Feb 6, 2008 1:07 PM, Cloves Pereira Costa Jr > wrote: > > Hi all... > > > > Anyone knows if there is some way to log the dropped packets in tcp= dump? > > I already search in google for it but didn't find anything... >=20 > 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 no= t > dropping packets would result in an infinitely growing buffer. >=20 > I don't know how you might configure the size of that buffer (a large= r > one /would/ quite possibly help), but if you dump to disk using the -= w > (and -s 0?) parameter, that might help. >=20 > Otherwise, get a faster machine. ;) >=20