Dropping packets at a particular device really isn't a good measure of performance.
Many providers limit the total number, the response rate or the overhead for ICMP packets at points along their network. On Sep 12, 2013, at 2:38 PM, Brad Bendily wrote: > Ok. > http://70.177.34.235:8497/smokeping/ > > I would be somewhat understanding of a few dropped packets to google and > other sites. But what irks me the the most is the dropped packets to internal > Cox > services. Those should never happen to me as a Cox customer. Check out the > cox.com and the three 68.x.x.x addresses. Those are Cox DNS servers. > If your DNS servers are dropping packets, what kind of end user experience is > the end user having? > bb > > > > On Thu, Sep 12, 2013 at 2:25 PM, Edmund Cramp <e...@motion-labs.com> wrote: > Why not post them here and let the folks on the list take a look at them? > > > > Interestingly enough I fired up pingplotter today and it seems that both AT&T > and COX appear to drop a lot of packets around Baton Rouge. What was most > interesting was that tracing to places like the google DNS servers resulted > in a lot more hops with AT&T than with COX. > > > > <image002.png> > > > > <image003.png> > > > > > > From: General [mailto:general-boun...@brlug.net] On Behalf Of Brad Bendily > Sent: Wednesday, September 11, 2013 12:51 PM > > > To: general@brlug.net > Subject: Re: [brlug-general] Cox internet service slow in evenings? > > > > I've been running smokeping and have some graphs too. > > but, i haven't been able to talk to someone who knows what to do with that > information. > > > > > > On Wed, Sep 11, 2013 at 10:39 AM, Edmund Cramp <e...@motion-labs.com> wrote: > > My general impression with the support folks is that you have to nail the > problem to their heads before they will look at it. This means that you have > to do the diagnostic and evidence collection and then present them with the > problem in a way that they can’t easily dismiss it - remember it’s “their” > network and they think that they know all about it even though they rarely > bother to look at it. > > > > Start with tracert and document the response times over a week or so for all > of the nodes - that will give you a good idea where they need to start > looking. > > > > <image001.png> > > > > In my case the firewall generates all the data I need - above you can see > that the link (COX) went down briefly last Thursday morning and that I had a > lot of traffic yesterday. Otherwise it’s been solid - now if you can > generate something similar and show it to the COX tech - and explain it to > them - then they may start to look at the problem. You have to remember that > close to 100% of the complaints that they have to deal with daily are luser > errors and that they will start by assuming that you can’t drive your > equipment . Don’t take it personally - most of the time they are right. > > > > Regards, > Edmund Cramp > -- > Debugging is twice as hard as writing the code in the first place. Therefore, > if you write the code as cleverly as possible, you are–by definition–not > smart enough to debug it. - Brian Kernighan > > > > > > > From: General [mailto:general-boun...@brlug.net] On Behalf Of Brad Bendily > Sent: Wednesday, September 11, 2013 9:47 AM > > > To: general@brlug.net > Subject: Re: [brlug-general] Cox internet service slow in evenings? > > > > The main problem I have isn't the high latency, i could deal with that, it's > the dropped packets/pings. > > To me, that shouldn't happen, often. > > > > > > On Wed, Sep 11, 2013 at 7:34 AM, Edmund Cramp <e...@motion-labs.com> wrote: > > For what it’s worth these are my ping times to 8.8.8.8 and 8.8.4.4 :- > > > > COX work 27ms, Cox home 25ms > > ATT work 70ms, ATT home 29ms > > > > These are measured via the routing monitor in the pfSense firewalls. > > > > Edmund Cramp > -- > > There are only two kinds of programming languages: those people always bitch > about and those nobody uses. - Bjarne Stroustrup > > > > > > From: General [mailto:general-boun...@brlug.net] On Behalf Of Brad Bendily > Sent: Tuesday, September 10, 2013 9:56 PM > > > To: general@brlug.net > Subject: Re: [brlug-general] Cox internet service slow in evenings? > > > > Actually, back in February, i replaced an old DOCSIS2.0 Linksys modem with a > CiscoDPC3010. And then in about april started noticing these issues. > > Had a tech come out around June. > > He checked the signals and they were all good, he replaced the modem any way, > with a Cisco DPC3825, but the issues remain. > > I've noticed a marginal improvement since I called a few weeks ago and > someone was supposed to check the neighborhood lines. > > I don't know if that actually happened or not. But i'll keep monitoring. > > > > bb > > > > > > On Tue, Sep 10, 2013 at 3:07 PM, Edmund Cramp <e...@motion-labs.com> wrote: > > I had a bitch at COX a while back over dropouts and signal latency and they > came out and replaced the Motorola Surfboard modem with a Cisco DPC3010 … > that just about halved the latency and virtually eliminated the service drops > that I was having at work. > > > > But the number one cause of large latencies is traffic - if you have a lot of > traffic in the pipe (in or out) then the packet latency is going to rise. > I’d measure the traffic in the pipe and see if there’s not some other source > of traffic on the connection. > > > > I’ve recently moved to using both COX and AT&T in an effort to improve > connection reliability and it’s working very nicely to date - I feed the two > WAN connections into the firewall and the LAN uses them both giving me almost > 12Mbs at home with a pair of 6Mb connections from COX and AT&T DSL. > > > > Edmund Cramp > -- > > The question of whether computers can think is like the question of whether > submarines can swim. - Edsger W. Dijkstra > > > > From: General [mailto:general-boun...@brlug.net] On Behalf Of Terry Stockdale > Sent: Friday, August 30, 2013 7:07 AM > To: general@brlug.net > > > Subject: Re: [brlug-general] Cox internet service slow in evenings? > > > > Also take a look at your router. When my old router went flaky (which I > eventually figured out), http was slow while email worked fine. Eventually, > web browsers could never get the full page. Pulling the plug on the router, > waiting 15 seconds, and then reinserting the plug solved it -- but two weeks > later, same problem. Then 2 days, then 2 hours... Fortunately, I had a new > one on order from Amazon by the time it got that bad. > > -- > Terry Stockdale -- Baton Rouge, LA > My computer tips site and newsletters: http://www.TerrysComputerTips.com > On 8/30/2013 12:06 AM, Karthik Poobalasubramanian wrote: > > Not really. My ping times to quakelive servers got higher than usual > but not by much. Cox techs, at least the ones who came out to my > place, were mostly incompetent. In all their tests, the "signals" were > good but my modem would disconnect every few hours or so. The modem > will be back online within minutes. Won't notice that while browsing > but when you on a video calls, you will. I changed my cable modem > twice but that did not resolve it. I went ahead and changed the coax > from the drop outside to my house to the attic distribution box and > change out cable from the distribution box to the cable modem. And > that fixed the issue. > > I don't want to move to another ISP, but if it comes down to it, i will. > haha... Like you have a real choice. Unless you wan to go commercial, > you only other choice is ATT and they suck too. > > Find out if your modem's S/N ratio is in the acceptable range and if > you have the latest firmware. If you call cox tech and if you are > lucky, you will get someone who will know the answer to this. I think > for Cisco Modems you can access the power and S/N at > http://192.168.100.1. > > Here's my Modem's Power and S/N ratio: http://db.tt/GBAjlze3 > > Here are some of my speed test results: > Cox plan speed: 50 Mbps down/ 10 Mbps up > > speedtest.net Results > To LUS: 64.27 Mbps Down/ 21.10 Mbps up Ping: 24ms > http://www.speedtest.net/result/2933064237.png > > To Cox NO: 65.41 Mbps Down/ 21.20 Mbps up Ping: 20ms > http://www.speedtest.net/result/2933065765.png > > To UT Houston: 54.45 Mbps Down/ 23.63 Mbps up Ping: 29ms > http://www.speedtest.net/result/2933067305.png > > nuttcp network test to my desktop at work. The desktop is on LONI with > 100 Mbps to commodity. > > > > poobal@daedalus:~$ sudo nuttcp -r -il -p 8760 -P 8759 bhope > 2.1875 MB / 1.00 sec = 18.3442 Mbps 0 retrans > 6.6250 MB / 1.00 sec = 55.5860 Mbps 0 retrans > 7.6875 MB / 1.00 sec = 64.4885 Mbps 0 retrans > 7.4375 MB / 1.00 sec = 62.3913 Mbps 0 retrans > 7.6875 MB / 1.00 sec = 64.4865 Mbps 0 retrans > 7.6250 MB / 1.00 sec = 63.9410 Mbps 0 retrans > 7.7500 MB / 1.00 sec = 65.0234 Mbps 0 retrans > 7.6875 MB / 1.00 sec = 64.4954 Mbps 0 retrans > 7.7500 MB / 1.00 sec = 65.0168 Mbps 0 retrans > 7.6875 MB / 1.00 sec = 64.4800 Mbps 0 retrans > > 71.7388 MB / 10.24 sec = 58.7872 Mbps 0 %TX 17 %RX 0 retrans 29.97 msRTT > > poobal@daedalus:~$ sudo nuttcp -t -il -p 8760 -P 8759 bhope > 1.5625 MB / 1.00 sec = 13.1070 Mbps 0 retrans > 3.6875 MB / 1.00 sec = 30.9329 Mbps 0 retrans > 1.3125 MB / 1.00 sec = 11.0101 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4857 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4858 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4858 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4854 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4859 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4857 Mbps 0 retrans > 1.2500 MB / 1.00 sec = 10.4860 Mbps 0 retrans > > 15.9375 MB / 10.52 sec = 12.7116 Mbps 0 %TX 4 %RX 0 retrans 30.67 msRTT > > > On Thu, Aug 29, 2013 at 10:00 PM, Brad Bendily <bend...@gmail.com> wrote: > Does anyone else have cox internet and notice much slower speed and > reliability in the evenings? > > I've been running smokeping for a few weeks and every evening, about 7-11 > speed and latency is very sporadic. I'm not 100% how long this has been a > problem but back in april/may I started a new project where I have been > working from home more and need to use a VPN to connect to another network. > Actually, two different VPNs on two different networks. One, is Dell > Sonicwall and the other is a Cisco. The Cisco, is surprisingly very stable > and even though the network is flakey the Cisco stays connected. But the > Sonicwall is very sensitive to the network outages. Any time the network > glitches the Sonicwall disconnects and all my SSH connections drop. Now I > RDP to a server on the network and run the SSH sessions from there. So I > don't lose everything. > > But, this brings me back to Cox's evening service. A tech came out about a > month ago and checked my signals which were all in the good range, he even > replaced the cable modem on good faith. Even though the one I had was only a > few months old.I replaced a much older linksys docsis2, with the Cisco > docsis3 modem. So, the tech replaced my modem with mostly the same model > modem, but still the signals are good. Normally, running a speed test on > speedtest.net, i get around 30Mbps down, 15Mbps up. Just now, i got .75Mbps > down, and 4Mbps up. > My smokeping is hitting 3 Cox DNS servers and one of their web servers and a > handful of other high profile servers. As well as two of my own personal, > which have no traffic and should be no lag what so ever. Yet smokeping shows > dropped packets and higher latency. > > I've called a few more times to try to explain the problem again. Monday i > called and the guy said they will send someone to check from the house out. > Last night I called and the person wanted to schedule a tech to come to the > house again. I asked for level 2 support and was put on hold for an hour. I > eventually hung up. > > If I were just web surfing, i would probably have never noticed and probably > wouldn't care, but now that i'm using the VPN a lot it would be nice to have > stable service in the evenings. > > has anyone else run into this and have any suggestions about how I can get > to the bottom of it with cox? > > I don't want to move to another ISP, but if it comes down to it, i will. > > thoughts? suggestions? bullshit remarks from jarred? > > > -- > Have Mercy & Say Yeah > > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > -- > Have Mercy & Say Yeah > > > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > -- > Have Mercy & Say Yeah > > > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > -- > Have Mercy & Say Yeah > > > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > -- > Have Mercy & Say Yeah > _______________________________________________ > General mailing list > General@brlug.net > http://brlug.net/mailman/listinfo/general_brlug.net --- Keith Stokes
_______________________________________________ General mailing list General@brlug.net http://brlug.net/mailman/listinfo/general_brlug.net
