dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1028
time eater
join:2010-11-12

time eater

Member

I would like some help with a few line tests I ran.

»/pingt ··· /3175523
»/pingt ··· /3175807
»/pingt ··· /3175081
»/pingt ··· /3177332
»/pingt ··· /3177339
»/pingt ··· /3177888
»/pingt ··· /3178147
»/pingt ··· /3185517
»/pingt ··· /3186709

»/pingt ··· /3186710 This is the latest one.

they are fail at certain parts and I would like to know why and verify is this is something i should be concerned about.

I first brought these tests(though i had not ran as many at that point) to the attention of the suddenlink forum my ISP at the moment. They basicly said that all the tools on this site where crap and I should not use them.

I have been using this site for a while whenever i have had internet trouble. The ISP I had been using is a&tt. and I wanted to try something new.

The thing that concerns me is latency in games, I play a lot of video games and I know packet loss and high ping times are a death sentence.

They(suddenlink forum) had told me to download pingplotter and run a test to the google DNS to see if there were any problems. It looked fine to me.

But a test I ran to a Team fortress 2 server i used to play on shows a much higher ping time then what my A&tt internet would have, and I dont think this is a case of DSL vs cable latency, because it goes through one of the same hops as the above tests. And on similar(location wise) servers where the traffic goes through a slightly different route it doesn't have a big increase in ping.

Now what worries me is that something like this could happen when I am playing one of my console games. I play a lot of fighting games and a good connection is important. And since this is peer to peer I cant really run a test to a server to get empirical data.

All and all I am very confused as to what I need to be doing to properly judge the worth of my connection with suddenlink as far as what i mainly need it for.

I hope this wasn't an incoherent information dump


Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

1 recommendation

Irish Shark

MVM

You have a mixed bag of things going on as reported by the pingtests.

• The Suddenlink routers are not responding to pings and the packet loss is phantom packet loss.

• The Suddenlink routers are overloaded and cannot process the pings in a timely fashion and are causing the high ping times as seen at your hop.

• The Suddenlink routers have packet loss and is carrying the packet loss to your hop.

• The Suddenlink routers are processing the pings correctly, but it shows packet loss at your hop.

• The reason why the tests look uglier on the Central Tests is that the pings are being routed differently on both tests. Also the tests only report the routers going to the target and you cannot see what the return routers are doing. The return path may not be the same routers that are going to the target.

The tests indicate that Suddenlink has some issues with their routers; and you might have some packet loss at your hop.

Have you talked to Suddenlink and showed them the plots?

I am on a MAC and I cannot read your PingPlotter test results. Can you copy them as a jpeg and post them here so I can take a look at them?
time eater
join:2010-11-12

1 edit

time eater

Member

Click for full size
Click for full size
Click for full size
Click for full size
here are images of all the tests i was told to run by the suddenlink forum.

these are poorly organized and some were run with different hardware, so i dont know how useful any of this is.

This all started when I decided to try suddenlink out as an ISP. I have been a customer of AT&T for a long time now, and I have never really been happy with them. There have been occasions with AT&T where has had some esoteric issue that has negatively effected my ability to play games. And these problems never got resolved by calling their tech support, because as long as it was on and I could reach yahoo there obviously wasn't a problem.

Shit only ever got fixed when I dived down the deep rabit hole of the internet networking and infrastructure and found this site. I have got in the habit of checking things with this site and trying to stay on top on any issues. But its like a 1st grader trying to grapple with quantum physics for me. I am just slow with comprehending it all.

I ran that line test, just to see what i could see. To see if it was a healthy internet connection, because the issues that were plaguing me at one point with AT&T effected everyone in my area it was just the squeaky wheel that wondered what happened and if it could be fixed. Here is everything I have ran, if thats useful at all. »/testh ··· 26/91944

All I want is a stable internet with as low a latency as possible. And running that line test I saw packet loss and in my head I go "Hmm I know that's a bad thing, and I dont see that with ATT" so I posted it suddenlink forum.

And they said the line test doesn't mean anything, it was just a snapshot test and to run ping-plotter to the Google DNS and my public gateway IP. And I am still not really sure what that is, since if i Google that term it talks about gateway address i.e 198.168.x.x but that's just the ips the my hardware uses locally to identify itself and I was told that's not what I want.

I ran some tests and showed the suddenlink forum the results and they saw the packet loss on my end and focused on that. I have sice bought and returned around 800$ worth of hardware just trying to remove anything that could be wrong on my end.

The first series of tests was done with a with a motorola gateway an SBG6580, then i replaced that with a net gear n600 gateway and rantests with that.

the most recent tests were done with(at least i think) just a motorola modem

I am now in the possession of a motorola sb6141 modem, and netgear gear n300 router and a linksys ac1200 router, all of which are still returnable to the stores that i bought them at. I tried asking the suddenlink what good hardware would be, I didn't really get a concrete answer, just any modem from motorla, and that there are a whole lot of different routers, but no suggestions.

And So I have basically opened a can of worms of me trying to see whats wrong on my end, whats wrong on, if anything on suddenlinks end(and if there was it would be a crapshoot if anything could be done about it)

And the whole thing is very stressful

I have yet to run a "public gateway ip" ping test with the linksys router because i cant find any IP that looks right in the router page.

And the netgear one drops all the packets on the first hop of one of the tests if I run two tests at a time.

I dont know the best way to handle all of this, I have 8 days to return this latest round of stuff I have bought, if I cant figure something out by then I will just drop suddenlink and return all the hardware and wait for the fatigue from trying to sort this stuff out to go away.

Really hoping somebody here can help me figure out the best course of action


Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark to time eater

MVM

to time eater
• Those graphs have me rethinking the cause of your problem.

• Run 10 ping tests 15 minutes apart to 192.168.0.1 about 20 pings. Post what you get.

• Pull the router. Reboot the MODEM and your box. Do the same as above for IP 10.244.96.1
time eater
join:2010-11-12

time eater

Member

Click for full size
I am confused as to what exactly you want me to do.

Do you want me to run 10 tests to that IP(why is it showing all those addresses?) fifteen minutes about and have it collect 20 samples. what should i set the trace interval it.

I posted a screen of the program interface, what should i have it set at? And what is it we are looking for by doing this?

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark

MVM

I meant just a ping test.

In a command prompt, type ping 192.168.1.1 -n 20

Now in that PingPlotter test there is no target address, so it kind of gets lost and it just pings past 192.169.1.1 for a while.

It looks like 192.168.1.1 is your Linksys/Cisco router. Is that correct?

Is 192.168.0.1 your MODEM? If yes, just do the ping test to that IP. Just do it once for 20 pings. Ping 192.168.0.1 -n 20
time eater
join:2010-11-12

time eater

Member


In my modems address page it lists the ethernet IP address as 192.168.100.1 is that what i would use?

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark

MVM

192.168.100.1 is the MODEM.

What the heck is 192.168.0.1 ???????
time eater
join:2010-11-12

time eater

Member

I dont know, how do i find out?

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark

MVM

It is a router default gateway (192.168.0.1) principally various D-Link and Netgear models. You have a Linksys/Cisco router, right?

But that IP into your browser and see if anything comes up or if you get an unknown destination.
time eater
join:2010-11-12

2 edits

time eater

Member

it wont connect to anything. I ran a ping test to that IP and got this

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 173.219.227.47: TTL expired in transit.
Reply from 173.219.229.203: TTL expired in transit.
Reply from 173.219.227.47: TTL expired in transit.
Reply from 173.219.227.51: TTL expired in transit.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

here is the first test to the modem and also one for the router

Ping statistics for 192.168.1.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping statistics for 192.168.100.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Right now the hardware that is hooked up is the motorola modem and the linksys. I also have a netgear but its in the package right now.

Edit: Here is the next set of tests
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63
Reply from 192.168.100.1: bytes=32 time1ms TTL=63

Ping statistics for 192.168.100.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64
Reply from 192.168.1.1: bytes=32 time1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Edit#2: Here's the next set

Ping statistics for 192.168.100.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping statistics for 192.168.1.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

So far its looking to be the same each time

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark to time eater

MVM

to time eater
What is catching my eye is that the PingPlotter runs look good for min and ave; but the max is off the chart.

If you notice in most of the plots, the first hop is 192.168.0.1.

At first I thought it was your router. But when ran the last PingPlotter run, the first hop is 192.168.1.1; your router. Also the run has good pings for min, ave, and max. Just does not make any sense.

Look at the ping test that you did. 3 different Suddenlink routers responded; TTL expired in transit. If it were a "dead" IP, would have shown the pings as 100% packet loss.

What ever 192.168.0.1 (I'll bet) is the culprit. Ask Suddenlink what is that IP.
time eater
join:2010-11-12

time eater

Member

well here is the things a lot of those ping plotter tests were run with different hardware, so I am sure at one point and time that first hop was what what it should be and not some phantom thing.

and I honestly dont know how to ask them anything so far I have been running around in circles chasing their suggestions.

And I am confused as all hell at this point

If I wanted to start all over looking into my line how do you think i should go about doing it?

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark

MVM

That is why things were not making any sense to me. i.e. IP 192.168.0.1

Let's stay with the hardware that you used to run the last PingPlotter test that you posted. If I follow you, that should be the Moto SB6141 Modem and the Linksys AC1200 router. Is that correct?

Run the Line Quality / Ping Test (the test that you posted in your first post). Run three of them about 15 minutes apart and post the links to the test results.

Now, run a PingPltter plot for 8 or so hours. Use the Google as the target with IP 8.8.8.8. Your first hop should be 192.168.1.1 if not, let me know what the first hop is.

Now let's see what that gives us.

Is there anything that you do not understand?
time eater
join:2010-11-12

time eater

Member

»/pingt ··· /3188554
»/pingt ··· /3188545
»/pingt ··· /3188530

here are those tests. I will post the results of the google ping plotter test as soon as i can.
time eater

time eater

Member

Click for full size
Well I have ran ping plotter all day, here are the results.

I have been talking to a tech from suddenlink who said that the nodes in my area were over saturated. And that there was physical maintenance to rebalanced them this morning.

So far my speeds have been consistent throughout the day, and my line tests look like they come up fine now.

»/pingt ··· /3189041

The only thing left that seems odd to me is there was a massive lag spike that happened early on in the test.

And a pattern of ping in the first hop, not sure what that is.

Any idea what that means and whats causing it?

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

3 edits

Irish Shark

MVM

It seems like things are getting better. That massive RTT on hop #1 is gone. (Look back an that used to be the 192.168.0.1. That was your other router.

Now we have high RTT starting at hop #2 and continues down to the target IP.

With routers saturated on Suddenlink's network is a sure sign that is one of the likely causes of your issues.

IP 10.25.32.1 is a private IP on the Suddenlink system. This hop is the Suddenlink side of your connection and shows latency between your network and Suddenlinks. When this hop shows high latency it usually means that the node is out of bandwidth or you are using all the bandwidth that your modem is configured for.

A high load as early as the second hop points to an overload of the private internet connection, which can be caused for example by sending large amounts of data via email, clogging up the upstream connection. File-sharing tools that suck up bandwidth in the background and have long since been forgotten could also be a problem. Since the ave and min look very good, you are not that bad. The max TTL could only be one ping. A clear picture of the problem can be found by performing a trace in the opposite direction.

When you run your plots are you doing anything in the background? Anyone else using the connection?

Try running a reverse trace from 8.8.8.8 to 10.25.32.1. Just let it run for about 20 minutes or so. The return routers will most likely not match the exact IPs as your plot to 8.8.8.8.

Have you run any smokeping plots?
time eater
join:2010-11-12

time eater

Member

i pretty sure I know what caused all the little spikes, i ran a speed test at 10am and then more every few hours, and the haze around 5pm coincides with me downloading something on my ps3.

I ran my first speed test at 8 before i turned ping plotter on, and hte massive spike happened after that, but before the 2nd test. I know i didn't do anything with my internet in that time.

Irish Shark
Play Like A Champion Today
MVM
join:2000-07-29
Las Vegas, NV

Irish Shark to time eater

MVM

to time eater
Those things will cause skewed data, but not much. Also, your node may be maxed out or just a few folks saturating the upstream will cause it.

Did you try a reverse PlingPlotter as I suggested above? The MODEM and Router are new, correct? How about all the Cat5 - 6?

Did I ask you if you are hardwired to the router or wireless when running all tests. You should be hardwired.

My best guess at the moment is a node issue or the line card at the CMTS is overloaded.