iAmMoDBoX Posted May 26, 2015 Share Posted May 26, 2015 About a week ago I noticed I was getting high ping spikes in my connection as well as slow upload speeds. It was reaching ~5,000ms at times. I talked to comcast and did all of their trouble shooting, they determined I needed a tech to come out here. I went ahead and changed the splitters on the lines inside my house and it did not fix my issue. I measured the ping and packet loss over the next few days while waiting for my appointment. During this time, comcast called me and said the upload speeds should be fixed and they were. But when the speed test gets to upload my connection starts dropping packets. I had the TM722G and it worked great besides this issue I was having. Today the tech came and didn't even look at anything besides swapping out my TM722G for the DPC3941T which I specifically said I do not want when I first called comcast and on the confirmation call for my appointment. Disgusted by the lack of care I just let the tech install the modem thinking it couldn't hurt my problem any more than it already is hurting.... Now hours later, I try to play my game and my pings are double what they were with my old modem, jitter is even higher, and my speeds are all over the place for my download. The modem I was supposed to get, which was noted plenty of times, was the TM822G. I wanted to use my own Asus router and not comcast's provided "all in one" piece of junk. What can I do to fix my ping spikes? http://i.imgur.com/KdIbD48.jpg http://i.imgur.com/wmXIMUy.jpg http://i.imgur.com/XHhWcpM.jpg http://i.imgur.com/qNeDT7y.jpg http://i.imgur.com/b3jWBhL.jpg http://i.imgur.com/dXTEO4N.jpg http://i.imgur.com/8vMagH8.jpg http://i.imgur.com/F1L2Zg6.jpg http://i.imgur.com/FnKnCOK.jpg http://i.imgur.com/UzsPSi9.jpg Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 26, 2015 Share Posted May 26, 2015 Originally I had the Tg852g. It worked ok I guess but I could never get my internet diagnosis to be that great with the R1. This particular router was a combo router/modem router. It had a wireless router side that I did not need. So I had Comcast bridge it with my Asus router. But like I said before, everything was ok I guess. I could never get my jitter improverd. So one that router needs to be replaced and comcasts gives me the tm722g because I told them I had my own wireless router. Now let me say I had three services with Comcast-phone,cable TV,and Internet. So with the tm722g it was basically a telephone and modem only. It was worst than the first. So basically what I ended up doing to remedy the situation was I did not need the home phone service anymore so I purchased my own modem. Arris Sb6183. I returned thectm722g to them and haven't looked back since. Oh yeah I was on the 100/20 service but now I'm on the 50/10 service and my internet diagnosis has no issues. Everything is exceptional and no packet loss. So you may just have to purchase the router that you prefer because Comcast will only give you what they think you need. I haven't had any expirence with the tm822 I can say this though when I got rid of the phone service through Comcast my quality of internet connection got a lot better. Hope this helps. Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Crossy Posted May 26, 2015 Netduma Staff Share Posted May 26, 2015 A couple of things that you could check. First of all the devices you are doing the ping test on are wired. Also make sure the ethernet cables are pushed in all the way and aren't lose. Having the ethernet cable not plugged in property can cause insanely high pings. I think Buck's solution sounds like a good one though as you seam to have had similar issues Also, although the packet loss was there, it was only a tiny amount compared to how many were sent. Were those packets losses when you started doing the upload speed test? If they were then I wouldn't worry about it because if you had congestion control enabled that would've dealt with it Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 26, 2015 Administrators Share Posted May 26, 2015 Wow Maz that is horrible mate, obivously that is almost certainly a problem with the line. So I don't think you can do anything its up to the ISP to fix that. Link to comment Share on other sites More sharing options...
lukasz Posted May 26, 2015 Share Posted May 26, 2015 Hello buddy. I don't wont to scare you off but i have delt with ISP when i first got my R1. It was here in UK. It took me about 2 moths of constant recording of different results of ping and Jitter. I took 2 technician 1 supervisor, numerous phone calls, Tweeting ISP official tweeter page etc. Just like you i was getting no where. Finally the tweeter campaign brought some results yet they never fixed it to the level i wanted it to be done. Out come of it is that my connection is a lot better yet it is far from being perfect. The reason i stopped this is that it is on a level of playable and i have a alternative witch is swapping to different ISP( my cousin that lives on this same street have that different ISP internet and he is having very nice steady connection) so when the times comes and all the stuff i am dealing with at the moment in my life witch are far more important then my internet will sorts out i will defiantly make that change. If you need more detail of how it was with me just let me know we can hook up on dumas chat and talk abut it. Wish you luck buddy. Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 27, 2015 Author Share Posted May 27, 2015 Originally I had the Tg852g. It worked ok I guess but I could never get my internet diagnosis to be that great with the R1. This particular router was a combo router/modem router. It had a wireless router side that I did not need. So I had Comcast bridge it with my Asus router. But like I said before, everything was ok I guess. I could never get my jitter improverd. So one that router needs to be replaced and comcasts gives me the tm722g because I told them I had my own wireless router. Now let me say I had three services with Comcast-phone,cable TV,and Internet. So with the tm722g it was basically a telephone and modem only. It was worst than the first. So basically what I ended up doing to remedy the situation was I did not need the home phone service anymore so I purchased my own modem. Arris Sb6183. I returned thectm722g to them and haven't looked back since. Oh yeah I was on the 100/20 service but now I'm on the 50/10 service and my internet diagnosis has no issues. Everything is exceptional and no packet loss. So you may just have to purchase the router that you prefer because Comcast will only give you what they think you need. I haven't had any expirence with the tm822 I can say this though when I got rid of the phone service through Comcast my quality of internet connection got a lot better. Hope this helps. After 5 phone calls the last time I updated from docsis 2 to docsis 3 I got the right Arris TM722G sent to me and I loved it. I had no problems up until now and since my pings are even higher and spiking I'm thinking there was no need to get rid of it anyway. I can't get rid of the phone service because they use it in my house. If it was up to me I would just buy my own modem but they won't provision my phone service on a purchased modem. A couple of things that you could check. First of all the devices you are doing the ping test on are wired. Also make sure the ethernet cables are pushed in all the way and aren't lose. Having the ethernet cable not plugged in property can cause insanely high pings. I think Buck's solution sounds like a good one though as you seam to have had similar issues Also, although the packet loss was there, it was only a tiny amount compared to how many were sent. Were those packets losses when you started doing the upload speed test? If they were then I wouldn't worry about it because if you had congestion control enabled that would've dealt with it Yes I'm wired. Modem>Asus Router>PC and that's the same setup I've always had... The packet loss was done over night when nobody was using the net so no there was 0 load on the router at the times of those packet losses. Wow Maz that is horrible mate, obivously that is almost certainly a problem with the line. So I don't think you can do anything its up to the ISP to fix that. It wasn't an issue up until about a week ago. I noticed while I was playing cod I would lag back a few seconds here and there. After seeing the R1 ping graph do that I knew something was wrong. Hello buddy. I don't wont to scare you off but i have delt with ISP when i first got my R1. It was here in UK. It took me about 2 moths of constant recording of different results of ping and Jitter. I took 2 technician 1 supervisor, numerous phone calls, Tweeting ISP official tweeter page etc. Just like you i was getting no where. Finally the tweeter campaign brought some results yet they never fixed it to the level i wanted it to be done. Out come of it is that my connection is a lot better yet it is far from being perfect. The reason i stopped this is that it is on a level of playable and i have a alternative witch is swapping to different ISP( my cousin that lives on this same street have that different ISP internet and he is having very nice steady connection) so when the times comes and all the stuff i am dealing with at the moment in my life witch are far more important then my internet will sorts out i will defiantly make that change. If you need more detail of how it was with me just let me know we can hook up on dumas chat and talk abut it. Wish you luck buddy. Most people I've talked to so far have no idea what ping even is. Like the tech that came to my house, he said himself "I have no idea what you're looking at or testing for so go ahead and check if it's working or not for you" and at the time my pings were level and when doing a speed test the modem stayed online. The only thing I haven't yet tried is changing the splitter outside my house, which is a 5 way comcast splitter so they have to come do that for me. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 27, 2015 Administrators Share Posted May 27, 2015 Wish I could help mate, just make sure it isn't that modem bug that the Cox cable guy has identified. Look up the member odog on this forum and see his posts. That's only thing I can think of. Link to comment Share on other sites More sharing options...
fuzzy clam Posted May 27, 2015 Share Posted May 27, 2015 I went thru that whole thing with jitter and node overload with my ISP and ended up having the cops called on me as I was very persistent.I had a Tier 3 guy come to my house when I asked for a Tier 1 supervisor,the tech knew nothing about what I had documented from pingtest or what all the overload on the nodes were.He knew pole to house and if I was getting the speeds I paid for and that's it.So to make a long story short I went and sat at the ISP's main office and asked to talk to a supervisor and was asked to leave,which I said no I'll just wait,so they called the cops.Everyone on here thought it was pretty funny,so all I can say is good luck getting it sorted out.As most ISP's are only concerned if it works and if your getting the speeds you pay for they could care less about line quality over overload. Link to comment Share on other sites More sharing options...
lukasz Posted May 27, 2015 Share Posted May 27, 2015 I went thru that whole thing with jitter and node overload with my ISP and ended up having the cops called on me as I was very persistent.I had a Tier 3 guy come to my house when I asked for a Tier 1 supervisor,the tech knew nothing about what I had documented from pingtest or what all the overload on the nodes were.He knew pole to house and if I was getting the speeds I paid for and that's it.So to make a long story short I went and sat at the ISP's main office and asked to talk to a supervisor and was asked to leave,which I said no I'll just wait,so they called the cops.Everyone on here thought it was pretty funny,so all I can say is good luck getting it sorted out.As most ISP's are only concerned if it works and if your getting the speeds you pay for they could care less about line quality over overload.i remember that one buddy. Just like it happened yesterday Link to comment Share on other sites More sharing options...
Alex49H Posted May 27, 2015 Share Posted May 27, 2015 Yep. That bug is whack. I have an Arris Motorola Sb6183 and Odog helped us out. Using a diff modem now from Netgear that is compatible with my Cox service. Not sure if there is an update because haven't heard from him I awhile. Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 28, 2015 Author Share Posted May 28, 2015 I talked to someone today about channel bonding since I am having upload issues and only bonding 3 out of the 4 channels available... They thought I was asking questions about my tv channel. This is very promising! Link to comment Share on other sites More sharing options...
Zennon Posted May 28, 2015 Share Posted May 28, 2015 I think if you bond with the existing problem you will still have these issue it will just cost more. Use Ping Plotter to plot the problem you can use the pro version for free for 30 days. It will chart the issues and you can save the data to show your i.s.p. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 28, 2015 Administrators Share Posted May 28, 2015 Alex I haven't heard from him in a while either. I guess big companies naturally have slower turn arounds, I'm referring to the modem company btw Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 29, 2015 Author Share Posted May 29, 2015 Speaking to level 3 tech support now... They said my area or street has a critically degraded signal and they have to send a line tech out to fix it. The guy laughed when he said he's surprised I'm the only one complaining in the area because of how bad the signal is. I explained I have a Netduma Link to comment Share on other sites More sharing options...
Zennon Posted May 29, 2015 Share Posted May 29, 2015 Hope he can sort it out for you Maz, good luck Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 29, 2015 Administrators Share Posted May 29, 2015 Wait a min, Maz you're Mike F on twitter? Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 29, 2015 Author Share Posted May 29, 2015 Wait a min, Maz you're Mike F on twitter? Depends.. is that good or bad? Lol Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 30, 2015 Author Share Posted May 30, 2015 Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 30, 2015 Administrators Share Posted May 30, 2015 Its good thing. I'm guessing those red parts aren't though. Link to comment Share on other sites More sharing options...
Zennon Posted May 30, 2015 Share Posted May 30, 2015 You can set ping plotter to plot events for long periods , keep and log of these bad events to give to your isp a max of 1112ms is massively unacceptable. It is showing on the round trip thats what counts so this is bad They might only accept readings from comand prompt so i would do some from there as wel lif you are a windows user. windows 8.1 right click on the windows start button and select command prompt type cmd/type ping 8.8.8.8 -t Other windows start/run/type cmd/type ping 8.8.8.8 -t That will run indefinitely. Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 30, 2015 Author Share Posted May 30, 2015 You can set ping plotter to plot events for long periods , keep and log of these bad events to give to your isp a max of 1112ms is massively unacceptable. It is showing on the round trip thats what counts so this is bad They might only accept readings from comand prompt so i would do some from there as wel lif you are a windows user. windows 8.1 right click on the windows start button and select command prompt type cmd/type ping 8.8.8.8 -t Other windows start/run/type cmd/type ping 8.8.8.8 -t That will run indefinitely. I've been running it for a day, I saved the whole log to a text file. I have tons of screenshots from command prompt ping tests that are showing huge spikes. The first tech I showed them to had no idea what ping even was, he said he doesn't know what kind of test I'm running lol Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted May 31, 2015 Author Share Posted May 31, 2015 Its good thing. I'm guessing those red parts aren't though. The red is packet loss or really high pings. The tech showed up today, did a signal to noise test and said everything is fine. He left, checked the splitter on the side of my house and said the ground was bad. Went to his truck to get his tools to replace it, came back and said he forgot what he needed at his last job so he would go get them and come back to finish here. He left and as far as I know he never returned because the splitter looks like it wasn't touched. I have no idea if he ever escalated the case to get a line tech sent out here or not. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 31, 2015 Administrators Share Posted May 31, 2015 man that sucks Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted June 1, 2015 Author Share Posted June 1, 2015 Comcast can tell if this is good or bad just by looking at it... Can you? Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted June 1, 2015 Author Share Posted June 1, 2015 man that sucks Any idea why pinging my router could cause such inconsistent results? Not the R1, I mean my comcast modem/router. Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=18ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=11ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=7ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=19ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=7ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=27ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=7ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=7ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=14ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=18ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=9ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=6ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=7ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=2ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=4ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=3ms TTL=64 Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Ping statistics for 192.168.1.1: Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 30ms, Average = 3ms Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.