Graphing packet loss

Josh Coates jcoates at
Fri Dec 30 09:10:55 MST 2005

> Digis has ruined the 2.4 spectrum here in 
> the Utah with all their illegal signal levels.

unless you can prove that, that sounds a lot like corporate defamation to

i don't personally have any legal or professional association with digis
(though my company is a customer of theirs) and i don't know jack squat
about wireless spectrums, but i don't think you should go shooting off about
a local company doing something illegal unless you know what you're talking

and if you can prove illegal activity, why don't you call up the
founder/president of digis (i've spoken with him several times, he's easy to
get on the phone) and ask him to stop?

and if you do, why don't you help educate the community and tell us how it

or maybe you don't really give a crap enough to care to really investigate
your claims, but you just like griping and exaggerating at the expense of a
local startup.  

or maybe you feel threatened by them on a professional level (i believe you
are affiliated with correct me if i'm mistaken) and you think
defamation is an acceptable competitive practice.

(btw - i'm back on plug for a while, so all you over-sensitive crybabies can
put me in your killfile again if you'd like.)


> -----Original Message-----
> From: plug-bounces at [mailto:plug-bounces at] On 
> Behalf Of Dave
> Sent: Thursday, December 29, 2005 8:27 PM
> To: Provo Linux Users Group Mailing List
> Subject: Re: Graphing packet loss
> 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.
> >
> >-josh
> >
> >  
> >
> >>-----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
> >Unsubscribe:
> >Don't fear the penguin.
> >*/
> >  
> >
> /*
> PLUG:, #utah on
> Unsubscribe:
> Don't fear the penguin.
> */

More information about the PLUG mailing list