Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Nov 2011 15:15:25 -0600
From:      Gary Gatten <>
To:        "''" <>, "''" <>
Subject:   Re: Diagnosing packet loss
Message-ID:  <>
In-Reply-To: <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Well, 1% is not good but I've seen worse for sure!  Sounds like you tried t=
he obvious.  I would recommend a different IP to rule out a dupe ip; else i=
t must be NIC related - either hardware or driver.  Also, perhaps swap cabl=
es and ports with a working machine and see if the problem follows or stays=

----- Original Message -----
From: Kees Jan Koster []
Sent: Tuesday, November 22, 2011 02:33 PM
To: <>
Subject: Diagnosing packet loss

Dear All,

I am stuck with a machine that shows serious packet loss (about 1% of all t=
raffic is dropped). I tried the obvious (new network cable, different switc=
h port, different ethernet interface on the machine), but the problems rema=

Another machine that sits in the same rack and is hooked up to the same swi=
tch shows no such packet loss issues. The problematic machine is a dual Opt=
eron with FreeBSD 8.2-STABLE from Thu Aug 11 14:05:47 CEST 2011.

The machine is lightly loaded. A MySQL slave is running, but the machine is=
 not serving queries. Plus a Munin server process.

I am at a loss where to start diagnosing this. Can you advise me where to l=
ook? Are there network buffers that may be overflowing?
Kees Jan

Change is good. Granted, it is good in retrospect, but change is good.

_______________________________________________ mailing list
To unsubscribe, send any mail to ""

<font size=3D"1">
<div style=3D'border:none;border-bottom:double windowtext 2.25pt;padding:0i=
n 0in 1.0pt 0in'>
"This email is intended to be reviewed by only the intended recipient
 and may contain information that is privileged and/or confidential.
 If you are not the intended recipient, you are hereby notified that
 any review, use, dissemination, disclosure or copying of this email
 and its attachments, if any, is strictly prohibited.  If you have
 received this email in error, please immediately notify the sender by
 return email and delete this email from your system."

Want to link to this message? Use this URL: <>