Graphing packet loss

Dave dave at
Thu Dec 29 20:27:01 MST 2005

You might find out an IP address to the Access point  he connects to. 
Then you can ping the Access point, also ping someplace a few hops 
beyond his ISP.  If you can ping the AP and loose packets at the ISP 
level, the ISP is over provisioned. If you loose packets at to the AP it 
could be a signal issue.  If he in using 2.4 spectrum, the problem is 
almost for sure Digis noise pollution. Digis has ruined the 2.4 spectrum 
here in the Utah with all their illegal signal levels.

Josh Coates wrote:

>smokeping is easy and all it does is graph packet loss.  i use it. 
>plus it's kind of neat looking.
>>-----Original Message-----
>>From: plug-bounces at [mailto:plug-bounces at] On 
>>Behalf Of Hans Fugal
>>Sent: Thursday, December 29, 2005 5:11 PM
>>To: plug at
>>Subject: Graphing packet loss
>>My dad is having serious come-and-go packet loss issues with 
>>his ISP (a Vernal local wireless setup). I'd like to give him 
>>some leverage with some nice cacti graphs of packet loss, but 
>>I'm having a hard time pinning down precisely what to graph.
>>The following is an excerpt of /proc/net/snmp:
>>Tcp: RtoAlgorithm RtoMin RtoMax MaxConn ActiveOpens 
>>PassiveOpens AttemptFails EstabResets CurrEstab InSegs 
>>OutSegs RetransSegs InErrs OutRsts
>>Would any of those directly measure packet loss? If not, 
>>might some of the stats in /proc/net/tcp (or anywhere else) 
>>have the information (which I could then get into SNMP easy enough).
>>It'd be really nice if I could tell on the router what kind 
>>of packet loss is happening, but I'm not sure you can do 
>>that, and since the subnet is a whole two computers that's 
>>not a big issue.
>>Hans Fugal ;
>>There's nothing remarkable about it. All one has to do is hit 
>>the right keys at the right time and the instrument plays itself.
>>    -- Johann Sebastian Bach
>PLUG:, #utah on
>Don't fear the penguin.

More information about the PLUG mailing list