Neotel neotel neotel...

PROBLEM WITH INTERNET ON MY NEOTEL LIGHT UNLIMITED

HELLO

you are the only one that could help me.

I have had neotel since July of 2008, from the start I had problems with download speeds and disconnection's until neotel came and put a external aerial in for me. From then on my download speeds were great and I had almost no disconnection's. I was on tower P132 and my RSSI 72, I was downloading at about 17kbs.

Then at the start of this year around February march, my speeds dropped badly to around 1kbs to 2kbs a RSSI 97, I contacted neotel and they advised me to get on my roof and to adjust my external aerial because there could be a new tower in my area that my number had been assigned to. So I did as they advised and ended up turning my external aerial 180 degrees, I picked up a tower P356 and my RSSI 74 I was downloading at 17kbs to 19kbs, great my connection was fixed and I was happy.

Now this month November I was in hospital ICU for a week, when I was taken to hospital on the 31 of October my connection was great, my wife says that the connection was great the whole time I was in hospital as well, but the days before I came out of hospital the connection started giving problems, disconnecting the whole time, on the 5th of November when I got home from hospital the connection was stuffed. It had moved to P344 RSSI 96 downloading 1kbs to 3kbs. I contacted neotel the first of many times and was told that if I was not happy with the speed I could cancel my contract, I was not happy with the response I was getting from neotel so I kept on trying to phone to find out what was the problem. Another rep said that I must try adjusting my external aerial again because the other towers were over loaded with customers. So I tried that, I turned my aerial 360 degrees picking up many towers but none with an RSSI below 87, the towers I picked up were
P132 RSSI 94
P268 RSSI 87
P356 RSSI 97
P344 RSSI 98
So I ended up aiming at the best I could get tower P268 RSSI 87, and got off the roof. But as soon as I connect to the Internet it jumped to tower P344 but now with a RSSI 85, and I can only download at 1kbs to a very max of 4kbs, and it disconnects a lot or just goes flat to a download speed of 0.42kbs to 0.68kbs.

This is just not working. I cant understand this because through most of my time with neotel I have not had a problem and I have had good download speeds, a RSSI always in the 70's except for a few problems as I have explained which were easily fixed. Now I cant get a good RSSi I cant download at full speeds and I keep on disconnecting. I really need some help with this, because the call center is just not interested in helping me. I don't want to cancel my contract but if this continues and I cant get it fixed I will have no other choice but to cancel and look for another option.

So can you help? Please!!!!

Thank you neotel light unlimited
__________________
You only Live once, so live life to the fullest!!!
 
WTF is up with this oke and his duplicate threads!!!!!!!!!!!!!!!! He has posted this is all active Neotel threads... ARG!!!!!!!!!!! :mad:
 
when you are desperate to have your problem solved you try everyting that is possible.....i am totaly desperate and need help from neotel:(
 
gdiza said:
WTF is up with this oke and his duplicate threads!!!!!!!!!!!!!!!! He has posted this is all active Neotel threads... ARG!!!!!!!!!!! :mad:
Click to expand...

It's called desperation. Poor wireless subscribers. You should switch to ADSL if possible - throw Neotel out the window. It'll do wonders for your stress levels, blood pressure, and thinning hair :D

He did also just come out of ICU.. might just be the after-effects if a bad head injury. I once had a mate.... argh.. NM.
 
@Neotel btw that vmc app only works if the device is plugged into your pc via usb. I do not use USB. :(
 
And if you on flex, you going to have more than one device connected at once! so how do you track the usage of all of them at once?
 
Got up early for once to run a test to check something. Normally when I work on my system I get massive disconnects and ping loss. What I wanted to check was at a time when the network should be quiet and I got the result below. In 2 minutes not a single latency spike or ping loss. My speeds were not much better. 15K bps to 50K bps speed swings which is telling me that even at this early hour the tower is badly congested.

At any other time I get them every 20 seconds or so. This tells that me that neotel has a serious problem on their core router configurations as well as on their edge routers at the towers. They cannot handle traffic when it starts to pickup and compensate by dropping connections or shoving data so far back in the prioritisation containers that it never gets handled. ie they have ****ed up on their prioritisation settings. This is a problem that is highlighted in Advanced routing. If you mess up on this type of configuration you have an unstable network at load.

Now the next test I want to do is get in my car and go park 50m from the tower and see what I get......................... Will find time for that this weekend.

If I get the results I am expecting Neotel can expect a pretty harsh submission to ICASA.

This test was done at 5am this morning

PING 196.3.164.2 (196.3.164.2) 56(84) bytes of data.
64 bytes from 196.3.164.2: icmp_seq=1 ttl=55 time=55.8 ms
64 bytes from 196.3.164.2: icmp_seq=2 ttl=55 time=79.0 ms
64 bytes from 196.3.164.2: icmp_seq=3 ttl=55 time=76.2 ms
64 bytes from 196.3.164.2: icmp_seq=4 ttl=55 time=77.9 ms
64 bytes from 196.3.164.2: icmp_seq=5 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=6 ttl=55 time=78.3 ms
64 bytes from 196.3.164.2: icmp_seq=7 ttl=55 time=76.0 ms
64 bytes from 196.3.164.2: icmp_seq=8 ttl=55 time=67.2 ms
64 bytes from 196.3.164.2: icmp_seq=9 ttl=55 time=66.5 ms
64 bytes from 196.3.164.2: icmp_seq=10 ttl=55 time=64.3 ms
64 bytes from 196.3.164.2: icmp_seq=11 ttl=55 time=74.9 ms
64 bytes from 196.3.164.2: icmp_seq=12 ttl=55 time=63.3 ms
64 bytes from 196.3.164.2: icmp_seq=13 ttl=55 time=75.1 ms
64 bytes from 196.3.164.2: icmp_seq=14 ttl=55 time=64.0 ms
64 bytes from 196.3.164.2: icmp_seq=15 ttl=55 time=57.9 ms
64 bytes from 196.3.164.2: icmp_seq=16 ttl=55 time=62.9 ms
64 bytes from 196.3.164.2: icmp_seq=17 ttl=55 time=57.3 ms
64 bytes from 196.3.164.2: icmp_seq=18 ttl=55 time=73.6 ms
64 bytes from 196.3.164.2: icmp_seq=19 ttl=55 time=71.0 ms
64 bytes from 196.3.164.2: icmp_seq=20 ttl=55 time=71.8 ms
64 bytes from 196.3.164.2: icmp_seq=21 ttl=55 time=81.0 ms
64 bytes from 196.3.164.2: icmp_seq=22 ttl=55 time=66.9 ms
64 bytes from 196.3.164.2: icmp_seq=23 ttl=55 time=82.9 ms
64 bytes from 196.3.164.2: icmp_seq=24 ttl=55 time=62.1 ms
64 bytes from 196.3.164.2: icmp_seq=25 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=26 ttl=55 time=80.8 ms
64 bytes from 196.3.164.2: icmp_seq=27 ttl=55 time=66.9 ms
64 bytes from 196.3.164.2: icmp_seq=28 ttl=55 time=59.4 ms
64 bytes from 196.3.164.2: icmp_seq=29 ttl=55 time=55.8 ms
64 bytes from 196.3.164.2: icmp_seq=30 ttl=55 time=63.2 ms
64 bytes from 196.3.164.2: icmp_seq=31 ttl=55 time=83.9 ms
64 bytes from 196.3.164.2: icmp_seq=32 ttl=55 time=60.0 ms
64 bytes from 196.3.164.2: icmp_seq=33 ttl=55 time=54.2 ms
64 bytes from 196.3.164.2: icmp_seq=34 ttl=55 time=98.1 ms
64 bytes from 196.3.164.2: icmp_seq=35 ttl=55 time=82.9 ms
64 bytes from 196.3.164.2: icmp_seq=36 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=37 ttl=55 time=79.3 ms
64 bytes from 196.3.164.2: icmp_seq=38 ttl=55 time=83.0 ms
64 bytes from 196.3.164.2: icmp_seq=39 ttl=55 time=79.9 ms
64 bytes from 196.3.164.2: icmp_seq=40 ttl=55 time=77.5 ms
64 bytes from 196.3.164.2: icmp_seq=41 ttl=55 time=60.7 ms
64 bytes from 196.3.164.2: icmp_seq=42 ttl=55 time=94.9 ms
64 bytes from 196.3.164.2: icmp_seq=43 ttl=55 time=61.0 ms
64 bytes from 196.3.164.2: icmp_seq=44 ttl=55 time=70.0 ms
64 bytes from 196.3.164.2: icmp_seq=45 ttl=55 time=59.9 ms
64 bytes from 196.3.164.2: icmp_seq=46 ttl=55 time=61.1 ms
64 bytes from 196.3.164.2: icmp_seq=47 ttl=55 time=57.0 ms
64 bytes from 196.3.164.2: icmp_seq=48 ttl=55 time=87.2 ms
64 bytes from 196.3.164.2: icmp_seq=49 ttl=55 time=80.3 ms
64 bytes from 196.3.164.2: icmp_seq=50 ttl=55 time=59.8 ms
64 bytes from 196.3.164.2: icmp_seq=51 ttl=55 time=69.5 ms
64 bytes from 196.3.164.2: icmp_seq=52 ttl=55 time=48.8 ms
64 bytes from 196.3.164.2: icmp_seq=53 ttl=55 time=78.5 ms
64 bytes from 196.3.164.2: icmp_seq=54 ttl=55 time=59.1 ms
64 bytes from 196.3.164.2: icmp_seq=55 ttl=55 time=83.5 ms
64 bytes from 196.3.164.2: icmp_seq=56 ttl=55 time=70.9 ms
64 bytes from 196.3.164.2: icmp_seq=57 ttl=55 time=84.6 ms
64 bytes from 196.3.164.2: icmp_seq=58 ttl=55 time=83.2 ms
64 bytes from 196.3.164.2: icmp_seq=59 ttl=55 time=67.9 ms
64 bytes from 196.3.164.2: icmp_seq=60 ttl=55 time=80.5 ms
64 bytes from 196.3.164.2: icmp_seq=61 ttl=55 time=116 ms
64 bytes from 196.3.164.2: icmp_seq=62 ttl=55 time=104 ms
64 bytes from 196.3.164.2: icmp_seq=63 ttl=55 time=82.8 ms
64 bytes from 196.3.164.2: icmp_seq=64 ttl=55 time=61.3 ms
64 bytes from 196.3.164.2: icmp_seq=65 ttl=55 time=65.9 ms
64 bytes from 196.3.164.2: icmp_seq=66 ttl=55 time=59.9 ms
64 bytes from 196.3.164.2: icmp_seq=67 ttl=55 time=79.4 ms
64 bytes from 196.3.164.2: icmp_seq=68 ttl=55 time=50.2 ms
64 bytes from 196.3.164.2: icmp_seq=69 ttl=55 time=73.5 ms
64 bytes from 196.3.164.2: icmp_seq=70 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=71 ttl=55 time=80.2 ms
64 bytes from 196.3.164.2: icmp_seq=72 ttl=55 time=49.3 ms
64 bytes from 196.3.164.2: icmp_seq=73 ttl=55 time=114 ms
64 bytes from 196.3.164.2: icmp_seq=74 ttl=55 time=93.8 ms
64 bytes from 196.3.164.2: icmp_seq=75 ttl=55 time=77.0 ms
64 bytes from 196.3.164.2: icmp_seq=76 ttl=55 time=87.1 ms
64 bytes from 196.3.164.2: icmp_seq=77 ttl=55 time=67.7 ms
64 bytes from 196.3.164.2: icmp_seq=78 ttl=55 time=83.6 ms
64 bytes from 196.3.164.2: icmp_seq=79 ttl=55 time=55.1 ms
64 bytes from 196.3.164.2: icmp_seq=80 ttl=55 time=67.6 ms
64 bytes from 196.3.164.2: icmp_seq=81 ttl=55 time=64.6 ms
64 bytes from 196.3.164.2: icmp_seq=82 ttl=55 time=80.0 ms
64 bytes from 196.3.164.2: icmp_seq=83 ttl=55 time=78.9 ms
64 bytes from 196.3.164.2: icmp_seq=84 ttl=55 time=81.1 ms
64 bytes from 196.3.164.2: icmp_seq=85 ttl=55 time=63.2 ms
64 bytes from 196.3.164.2: icmp_seq=86 ttl=55 time=69.8 ms
64 bytes from 196.3.164.2: icmp_seq=87 ttl=55 time=67.7 ms
64 bytes from 196.3.164.2: icmp_seq=88 ttl=55 time=87.4 ms
64 bytes from 196.3.164.2: icmp_seq=89 ttl=55 time=78.1 ms
64 bytes from 196.3.164.2: icmp_seq=90 ttl=55 time=116 ms
64 bytes from 196.3.164.2: icmp_seq=91 ttl=55 time=62.9 ms
64 bytes from 196.3.164.2: icmp_seq=92 ttl=55 time=59.5 ms
64 bytes from 196.3.164.2: icmp_seq=93 ttl=55 time=87.1 ms
64 bytes from 196.3.164.2: icmp_seq=94 ttl=55 time=74.6 ms
64 bytes from 196.3.164.2: icmp_seq=95 ttl=55 time=66.2 ms
64 bytes from 196.3.164.2: icmp_seq=96 ttl=55 time=57.3 ms
64 bytes from 196.3.164.2: icmp_seq=97 ttl=55 time=76.4 ms
64 bytes from 196.3.164.2: icmp_seq=98 ttl=55 time=75.2 ms
64 bytes from 196.3.164.2: icmp_seq=99 ttl=55 time=66.9 ms
64 bytes from 196.3.164.2: icmp_seq=100 ttl=55 time=57.4 ms
64 bytes from 196.3.164.2: icmp_seq=101 ttl=55 time=117 ms
64 bytes from 196.3.164.2: icmp_seq=102 ttl=55 time=56.4 ms
64 bytes from 196.3.164.2: icmp_seq=103 ttl=55 time=73.6 ms
64 bytes from 196.3.164.2: icmp_seq=104 ttl=55 time=85.9 ms
64 bytes from 196.3.164.2: icmp_seq=105 ttl=55 time=81.5 ms
64 bytes from 196.3.164.2: icmp_seq=106 ttl=55 time=62.1 ms
64 bytes from 196.3.164.2: icmp_seq=107 ttl=55 time=53.0 ms
64 bytes from 196.3.164.2: icmp_seq=108 ttl=55 time=52.1 ms
64 bytes from 196.3.164.2: icmp_seq=109 ttl=55 time=54.2 ms
64 bytes from 196.3.164.2: icmp_seq=110 ttl=55 time=84.9 ms
64 bytes from 196.3.164.2: icmp_seq=111 ttl=55 time=64.9 ms
64 bytes from 196.3.164.2: icmp_seq=112 ttl=55 time=86.6 ms
64 bytes from 196.3.164.2: icmp_seq=113 ttl=55 time=65.2 ms
64 bytes from 196.3.164.2: icmp_seq=114 ttl=55 time=56.8 ms
64 bytes from 196.3.164.2: icmp_seq=115 ttl=55 time=73.2 ms
64 bytes from 196.3.164.2: icmp_seq=116 ttl=55 time=81.9 ms
64 bytes from 196.3.164.2: icmp_seq=117 ttl=55 time=72.9 ms
64 bytes from 196.3.164.2: icmp_seq=118 ttl=55 time=52.2 ms
64 bytes from 196.3.164.2: icmp_seq=119 ttl=55 time=63.9 ms
64 bytes from 196.3.164.2: icmp_seq=120 ttl=55 time=62.9 ms
64 bytes from 196.3.164.2: icmp_seq=121 ttl=55 time=73.0 ms
64 bytes from 196.3.164.2: icmp_seq=122 ttl=55 time=73.5 ms
64 bytes from 196.3.164.2: icmp_seq=123 ttl=55 time=72.8 ms
64 bytes from 196.3.164.2: icmp_seq=124 ttl=55 time=62.6 ms
64 bytes from 196.3.164.2: icmp_seq=125 ttl=55 time=94.1 ms
64 bytes from 196.3.164.2: icmp_seq=126 ttl=55 time=80.5 ms
64 bytes from 196.3.164.2: icmp_seq=127 ttl=55 time=85.6 ms
64 bytes from 196.3.164.2: icmp_seq=128 ttl=55 time=71.2 ms
 
Last edited:
Morning

Morning Guys.

Gary - noted the loop, and working on that FSE callout to you again, as well as Jean. will give you each you individual dates for it, or you'll know when they call to confirm a time.

Jean - I said SIMILAR to the VMC thing, but doesn't use the same principles as PNP devices... thats why i mentioned it. The network carriage tools should be able to support an online tool as well, but then the inaccuracy could well be way off. Henceforth if you want detailed accuracy, then depending on an indivual app might be the best solution.

Catruter - Have pasted your info as is to networks, and i want to see what their response is to it. Will keep you posted on here.

Team - I want to know would it be ok if we started weekly threads with subjects being Fri 20 Nov to Thu 26 Nov.
This will help us keep track of posted challenges and help resolution times to 1 week. So if you post in the week example above, by the Friday 27th Nov, all of the previous week challenges should have been solved. Tell me what you guys think?

Hugo
 
As far as the Bandwidth usage tools goes, it needs to work off data from your billing database. You cannot rely on data collected on a client machine. I for one have 4 machines, one of which has 4 virtual machines on it.


edit : Fixed my *** spelling before I have had my 2 cups of coffee :D
 
Last edited:
@neotel
agreed, thank you for the response, i will be waiting for the update and my connection to be fixed, it is truely not nice to have my internet connection like this over the past few weeks, i hope that you will be able to fix it soon
 
rofl .... Maybe he is trying to convince us he isnt a spy afterall :D
 
And now once the tower starts getting busy ....
I get crap like this continually
I had no traffic other than the ping running
Nice stable connection for doing something like gaming :/

Reply from 196.3.164.2: bytes=32 time=78ms TTL=55
Reply from 196.3.164.2: bytes=32 time=62ms TTL=55
Request timed out.
Reply from 196.3.164.2: bytes=32 time=857ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.3.164.2: bytes=32 time=61ms TTL=55
Reply from 196.3.164.2: bytes=32 time=80ms TTL=55
Reply from 196.3.164.2: bytes=32 time=61ms TTL=55
Reply from 196.3.164.2: bytes=32 time=402ms TTL=55
Reply from 196.3.164.2: bytes=32 time=1371ms TTL=55
Reply from 196.3.164.2: bytes=32 time=130ms TTL=55
Reply from 196.3.164.2: bytes=32 time=52ms TTL=55
Reply from 196.3.164.2: bytes=32 time=62ms TTL=55
Reply from 196.3.164.2: bytes=32 time=55ms TTL=55
Reply from 196.3.164.2: bytes=32 time=72ms TTL=55
Reply from 196.3.164.2: bytes=32 time=72ms TTL=55
Reply from 196.3.164.2: bytes=32 time=85ms TTL=55
Reply from 196.3.164.2: bytes=32 time=81ms TTL=55
Reply from 196.3.164.2: bytes=32 time=62ms TTL=55
Reply from 196.3.164.2: bytes=32 time=79ms TTL=55
Reply from 196.3.164.2: bytes=32 time=89ms TTL=55
Reply from 196.3.164.2: bytes=32 time=62ms TTL=55
Reply from 196.3.164.2: bytes=32 time=70ms TTL=55
Reply from 196.3.164.2: bytes=32 time=80ms TTL=55
Reply from 196.3.164.2: bytes=32 time=71ms TTL=55
Reply from 196.3.164.2: bytes=32 time=67ms TTL=55
Reply from 196.3.164.2: bytes=32 time=94ms TTL=55
Reply from 196.3.164.2: bytes=32 time=71ms TTL=55
Reply from 196.3.164.2: bytes=32 time=84ms TTL=55
Reply from 196.3.164.2: bytes=32 time=91ms TTL=55
Reply from 196.3.164.2: bytes=32 time=52ms TTL=55
Reply from 196.3.164.2: bytes=32 time=58ms TTL=55
Reply from 196.3.164.2: bytes=32 time=70ms TTL=55
Reply from 196.3.164.2: bytes=32 time=80ms TTL=55
Reply from 196.3.164.2: bytes=32 time=63ms TTL=55
Reply from 196.3.164.2: bytes=32 time=60ms TTL=55
Reply from 196.3.164.2: bytes=32 time=60ms TTL=55
Reply from 196.3.164.2: bytes=32 time=81ms TTL=55
Reply from 196.3.164.2: bytes=32 time=75ms TTL=55


Gary Waterworth said:
Got up early for once to run a test to check something. Normally when I work on my system I get massive disconnects and ping loss. What I wanted to check was at a time when the network should be quiet and I got the result below. In 2 minutes not a single latency spike or ping loss. My speeds were not much better. 15K bps to 50K bps speed swings which is telling me that even at this early hour the tower is badly congested.

At any other time I get them every 20 seconds or so. This tells that me that neotel has a serious problem on their core router configurations as well as on their edge routers at the towers. They cannot handle traffic when it starts to pickup and compensate by dropping connections or shoving data so far back in the prioritisation containers that it never gets handled. ie they have ****ed up on their prioritisation settings. This is a problem that is highlighted in Advanced routing. If you mess up on this type of configuration you have an unstable network at load.

Now the next test I want to do is get in my car and go park 50m from the tower and see what I get......................... Will find time for that this weekend.

If I get the results I am expecting Neotel can expect a pretty harsh submission to ICASA.

This test was done at 5am this morning

PING 196.3.164.2 (196.3.164.2) 56(84) bytes of data.
64 bytes from 196.3.164.2: icmp_seq=1 ttl=55 time=55.8 ms
64 bytes from 196.3.164.2: icmp_seq=2 ttl=55 time=79.0 ms
64 bytes from 196.3.164.2: icmp_seq=3 ttl=55 time=76.2 ms
64 bytes from 196.3.164.2: icmp_seq=4 ttl=55 time=77.9 ms
64 bytes from 196.3.164.2: icmp_seq=5 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=6 ttl=55 time=78.3 ms
64 bytes from 196.3.164.2: icmp_seq=7 ttl=55 time=76.0 ms
64 bytes from 196.3.164.2: icmp_seq=8 ttl=55 time=67.2 ms
64 bytes from 196.3.164.2: icmp_seq=9 ttl=55 time=66.5 ms
64 bytes from 196.3.164.2: icmp_seq=10 ttl=55 time=64.3 ms
64 bytes from 196.3.164.2: icmp_seq=11 ttl=55 time=74.9 ms
64 bytes from 196.3.164.2: icmp_seq=12 ttl=55 time=63.3 ms
64 bytes from 196.3.164.2: icmp_seq=13 ttl=55 time=75.1 ms
64 bytes from 196.3.164.2: icmp_seq=14 ttl=55 time=64.0 ms
64 bytes from 196.3.164.2: icmp_seq=15 ttl=55 time=57.9 ms
64 bytes from 196.3.164.2: icmp_seq=16 ttl=55 time=62.9 ms
64 bytes from 196.3.164.2: icmp_seq=17 ttl=55 time=57.3 ms
64 bytes from 196.3.164.2: icmp_seq=18 ttl=55 time=73.6 ms
64 bytes from 196.3.164.2: icmp_seq=19 ttl=55 time=71.0 ms
64 bytes from 196.3.164.2: icmp_seq=20 ttl=55 time=71.8 ms
64 bytes from 196.3.164.2: icmp_seq=21 ttl=55 time=81.0 ms
64 bytes from 196.3.164.2: icmp_seq=22 ttl=55 time=66.9 ms
64 bytes from 196.3.164.2: icmp_seq=23 ttl=55 time=82.9 ms
64 bytes from 196.3.164.2: icmp_seq=24 ttl=55 time=62.1 ms
64 bytes from 196.3.164.2: icmp_seq=25 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=26 ttl=55 time=80.8 ms
64 bytes from 196.3.164.2: icmp_seq=27 ttl=55 time=66.9 ms
64 bytes from 196.3.164.2: icmp_seq=28 ttl=55 time=59.4 ms
64 bytes from 196.3.164.2: icmp_seq=29 ttl=55 time=55.8 ms
64 bytes from 196.3.164.2: icmp_seq=30 ttl=55 time=63.2 ms
64 bytes from 196.3.164.2: icmp_seq=31 ttl=55 time=83.9 ms
64 bytes from 196.3.164.2: icmp_seq=32 ttl=55 time=60.0 ms
64 bytes from 196.3.164.2: icmp_seq=33 ttl=55 time=54.2 ms
64 bytes from 196.3.164.2: icmp_seq=34 ttl=55 time=98.1 ms
64 bytes from 196.3.164.2: icmp_seq=35 ttl=55 time=82.9 ms
64 bytes from 196.3.164.2: icmp_seq=36 ttl=55 time=59.0 ms
64 bytes from 196.3.164.2: icmp_seq=37 ttl=55 time=79.3 ms
64 bytes from 196.3.164.2: icmp_seq=38 ttl=55 time=83.0 ms
64 bytes from 196.3.164.2: icmp_seq=39 ttl=55 time=79.9 ms
... blah blah 2 mins of totally stable link
Click to expand...
 
Gary

Hey Gary.

I'll revert response to you monday morning on below!

Hugo
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X