"Is it my Line" Report Tool

ichocolate said:
This seems like a false positive to me because i tested an iso download from the is ftp site and i get 40 to 60 kb/s :

Zertop's LineTool Results
Date/Time: Thu Sep 22 22:20:44 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 5ms.
Your maximum ping was 7ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 7ms, Average = 5ms


I dont know what to do anymore.

Something is slowing my speed down. I download the same file just moments ago and really could not believe it, it was downloading at 950 odd kb/s

Note before i did the java test about it was a bad speed test like 4.9 and then max the needle was , was at 7.6.
Ping test was good though showing amazingly no jitter and only ping - quality B was given.

I rebooted the modem to run this test but before i did i downloaded a iso out of interest:

View attachment 390998


Then all of a sudden it went back to the mystery speed i have been having since they changed me to a 10 meg line from 4:

View attachment 391000

Its been reported but i might be talking to the wrong technician.
Anoying part is that you report a fault and you are told there is a line noise and then then tell you they will contact you later to tell you what speed you are connected at and tghey ask you to check how fast a website loads.
i mean flip.
The call gets closed and no dam resolution.
I have escalated this so hope something happens because it is ridiculous.

These are my details of my tp-link device page:
I have tested different RJ11 cables and also unplugged the phone and im running nothing else electrical near by.
Not sure what to do and who to talk to .
You either have the right person that will go out of their way to help you or you just struggle.


View attachment 391002


I also run the Zertop test - 3 of them which all include 2x the tracert results:


Zertop Results:
Code: 
TEST01

Tracert skipped (post too long)
  
International Speedtest 
Downloaded 100.0 megabytes in 4:58 seconds. (343.37 KB/s)
  
Local Speedtest 
Downloaded 8000.0 kilobytes in 14 seconds. (564.17 KB/s)
  
Test End Timestamp 
Fri 09/23/2016  0:08:16.63 


TEST02

Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  dsldevice.lan [192.168.10.1] 
  2     *        *        *     Request timed out.
  3    47 ms   231 ms     7 ms  cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182] 
  4     7 ms     7 ms     7 ms  cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181] 
  5     7 ms     7 ms     6 ms  cdsl1-rba-vl150.ip.isnet.net [196.38.73.17] 
  6    10 ms     8 ms     7 ms  core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163] 
  7     7 ms    17 ms     7 ms  168.209.1.170 
  8     7 ms     7 ms     7 ms  mweb-1.jinx.net.za [196.223.14.25] 
  9    29 ms    29 ms    30 ms  te0-0-0-3.vic-p-2.optinet.net [197.80.7.34] 
 10    28 ms    27 ms    27 ms  te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34] 
 11    25 ms    26 ms    25 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
 12    27 ms    27 ms    26 ms  196.28.178.66 
 13    29 ms    27 ms    29 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 14    26 ms    26 ms    26 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 15    26 ms    27 ms    27 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 16    26 ms    26 ms    26 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  dsldevice.lan [192.168.10.1] 
  2     *        *        *     Request timed out.
  3     7 ms     8 ms     7 ms  cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182] 
  4     7 ms     7 ms     7 ms  cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181] 
  5     7 ms     7 ms     7 ms  cdsl1-rba-vl150.ip.isnet.net [196.38.73.17] 
  6     8 ms     7 ms     7 ms  core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163] 
  7     7 ms     7 ms     7 ms  168.209.1.170 
  8     7 ms     7 ms     7 ms  mweb-1.jinx.net.za [196.223.14.25] 
  9    30 ms    28 ms    31 ms  te0-0-0-3.vic-p-2.optinet.net [197.80.7.34] 
 10    30 ms    31 ms    31 ms  te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34] 
 11    26 ms    26 ms    26 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
 12    28 ms    32 ms    26 ms  196.28.178.66 
 13    27 ms    27 ms    27 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 14    26 ms    27 ms    30 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 15    27 ms    26 ms    29 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 16    26 ms    26 ms    26 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  dsldevice.lan [192.168.10.1] 
  2     *        *        *     Request timed out.
  3    76 ms   104 ms   103 ms  curp1-rba-gi1.isdsl.net [196.38.72.230] 
  4     7 ms     9 ms     7 ms  196.38.72.229 
  5     8 ms     7 ms     7 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 
  6    11 ms     7 ms    11 ms  core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163] 
  7   194 ms   194 ms   184 ms  core2b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.209.246.66] 
  8   184 ms   183 ms   184 ms  linx-gw2.thdo.ncuk.net [195.66.236.240] 
  9   180 ms   179 ms   179 ms  po4-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 10   183 ms   183 ms   184 ms  [url]www.thinkbroadband.com[/url] [80.249.99.130] 

Trace complete.

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  dsldevice.lan [192.168.10.1] 
  2     *        *        *     Request timed out.
  3     8 ms     7 ms     8 ms  curp1-rba-gi1.isdsl.net [196.38.72.230] 
  4     7 ms     7 ms     7 ms  196.38.72.229 
  5     6 ms     7 ms     7 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 
  6    10 ms     7 ms     7 ms  core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163] 
  7   186 ms   188 ms   187 ms  core2b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.209.246.66] 
  8   183 ms   183 ms   183 ms  linx-gw2.thdo.ncuk.net [195.66.236.240] 
  9   181 ms   178 ms   193 ms  po4-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 10   183 ms   183 ms   184 ms  [url]www.thinkbroadband.com[/url] [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 10.0 megabytes in 30 seconds. (331.28 KB/s)
  
Local Speedtest 
Downloaded 4000.0 kilobytes in 5 seconds. (770.71 KB/s)
  
Test End Timestamp 
Fri 09/23/2016  0:11:21.12
Click to expand...

Looks like you've done everything except try a new ISP. Try a Crystal Web trial.
 
I received unshapped and throttle-free trial data from Webafrica so i have been doing a few tests.
Same junk.

Telkom worked on my line on Sunday PM after i had re logged it again.

SNR is better now by 7db or so. It was 7.5 odd but it has dropped to about 7.3-6.8 Still better than 6.1 down to 4 at times.

Attenuation was also improved to 37 compared to 43.

Download speeds almost there but single thread downloads are 100 kb/s odd.
Speed test says 6.5 to 7.5 sometimes 8 if i am lucky.

Any comments...
 
ichocolate said:
I received unshapped and throttle-free trial data from Webafrica so i have been doing a few tests.
Same junk.

Telkom worked on my line on Sunday PM after i had re logged it again.

SNR is better now by 7db or so. It was 7.5 odd but it has dropped to about 7.3-6.8 Still better than 6.1 down to 4 at times.

Attenuation was also improved to 37 compared to 43.

Download speeds almost there but single thread downloads are 100 kb/s odd.
Speed test says 6.5 to 7.5 sometimes 8 if i am lucky.

Any comments...
Click to expand...

I guess your only option is to downgrade your line, try an 8mb.
 
Long story short, 4mb Afrihost Business account seems shaped for long periods during the day. Have logged five Telkom faults in a row, had two technicians here, had support from local exchange, still happening. Like Clockwork, at 1, 2 or 5 PM, line will drop to quarter speed, sometimes slower, and remain that way until precisely 12 in the evening, when it magically starts working fine again.

Ran both tools available during nightly purge session, and no idea, problems, problems, problems.

Zertop's LineTool Results
Date/Time: Tue Nov 01 22:27:08 CAT 2016

Basic Report:

Your packet loss was 70%.
Your average ping was 1703ms.
Your maximum ping was 3388ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Pinging 169.0.35.1 with 32 bytes of data:
Reply from 169.0.35.1: bytes=32 time=2334ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.35.1: bytes=32 time=2644ms TTL=254
Reply from 169.0.35.1: bytes=32 time=3388ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.35.1: bytes=32 time=1005ms TTL=254
Reply from 169.0.35.1: bytes=32 time=738ms TTL=254
Reply from 169.0.35.1: bytes=32 time=698ms TTL=254
Reply from 169.0.35.1: bytes=32 time=734ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.35.1: bytes=32 time=3155ms TTL=254
Reply from 169.0.35.1: bytes=32 time=633ms TTL=254

Ping statistics for 169.0.35.1:
Packets: Sent = 30, Received = 9, Lost = 21 (70% loss),
Approximate round trip times in milli-seconds:
Minimum = 633ms, Maximum = 3388ms, Average = 1703ms
 
So glad I am rid of ADSL and Telkom this month

Zertop's LineTool Results
Date/Time: Tue Nov 15 20:39:16 GMT+02:00 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 34ms.
Your maximum ping was 113ms.

Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:
Code: 
PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=30.1 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=48.0 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=32.8 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=30.5 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=31.1 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=26.0 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=27.8 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=31.2 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=31.5 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=29.8 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=31.7 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=30.2 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=32.3 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=31.8 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=30.6 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=34.4 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=28.5 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=25.3 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=31.9 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=32.9 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=31.9 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=113 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=33.6 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=30.1 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=31.2 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=31.6 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=30.9 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=26.9 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=33.8 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=41.3 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29123ms
rtt min/avg/max/mdev = 25.336/34.497/113.815/15.301 ms
 
Zertop said:
Hi All,
This tool pings the last possible hardware on the telkom network - to help deduce whether a fault lies with Telkom or with the user's ISP :)

I am very strict with regards to malware, and will never distribute something that potentially has any form of harmful file attached to it.

Download JAR: https://zertop.com/releases/linetool/



Download Android App: https://github.com/Zertop/LineToolAndroid/releases

Changelog: https://github.com/Zertop/LineTool/releases

Click to expand...

Hi Zertop :D

The link marked in red above , he is broken ....

Best

Geoff
 
Thanks for this tool, it is very helpful.

ISP: MWEB 10 Mbps uncapped
ADSL line: 4Mbps Telkom

I have been having intermittent issues. I have been in contact with Telkom who just recreate my port. Last night I changed my POTS filter and thought everything was OK again, but I just got home and the internet was down. This was the result of the line tool (no internet access):

Zertop's LineTool Results
Date/Time: Wed Jan 25 17:14:56 CAT 2017

Basic Report:

Your packet loss was 3%.
Your average ping was 8ms.
Your maximum ping was 9ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Request timed out.
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 9ms, Average = 8ms

I then rebooted my modem and the internet went on again. I reran the line tool and get this:

Zertop's LineTool Results
Date/Time: Wed Jan 25 17:21:32 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 10ms.
Your maximum ping was 58ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=58ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=7ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=12ms TTL=62
Reply from 155.239.255.250: bytes=32 time=8ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 58ms, Average = 10ms

This is my speed test result:
Test Result

Last Result:
Download Speed: 3312 kbps (414 KB/sec transfer rate)
Upload Speed: 417 kbps (52.1 KB/sec transfer rate)
Latency: 9 ms
Jitter: 1 ms
25/01/2017, 17:30:50

Router stats:
Uptime: 0 days, 0:13:29

DSL Type: ITU-T G.992.5 Annex A (ADSL2+ over POTS)

Bandwidth (Up/Down) [kbps/kbps]: 511 / 4.096

Data Transferred (Sent/Received) [MB/MB]: 11,58 / 43,23

Output Power (Up/Down) [dBm]: -1,0 / 5,0

Line Attenuation (Up/Down) [dB]: 18,5 / 29,5

SN Margin (Up/Down) [dB]: 11,8 / 16,5

System Vendor ID (Local/Remote): TMMB / ----

I am using the crappy MWeb fon modem at the moment, could that be the issue?

Any advise will be appreciated.
 
Latest Results Testing a D-Link Router

Zertop's LineTool Results
Date/Time: Sat Mar 25 09:34:43 SAST 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 26ms.
Your maximum ping was 53ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:
Code: 
PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=24.246 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=24.106 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=25.876 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=24.891 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=24.086 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=24.913 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=24.212 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=24.374 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=24.021 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=24.280 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=24.812 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=24.895 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=25.120 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=24.805 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=53.413 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=34.935 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=23.560 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=24.363 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=25.470 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=23.930 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=33.122 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=26.197 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=24.750 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=24.277 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=23.867 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=25.140 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=23.891 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=24.959 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=24.084 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=26.497 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.560/26.236/53.413/5.607 ms
 
Awks,

Sorry peeps! Didn't check this thread at all, so didn't realise the links had expired. I've updated the main post :-)
 
Hi Zertop

Tried a few different versions, all give the same.

This is my work laptop, might be the JAVA that is an issue, as I have to run a specific version.

I will try later at home on my PC, that has the latest version of JAVA.
 
Pretty sure the JAVA version is the issue. Had a similar problem on a PC recently that is used in a BYOD environment but not with Zertops Line test tool.
 
Last edited:
happynoodleboy said:
Hi Zertop

Tried a few different versions, all give the same.

This is my work laptop, might be the JAVA that is an issue, as I have to run a specific version.

I will try later at home on my PC, that has the latest version of JAVA.
Click to expand...

Let me know how that goes! I've compiled using JDK7, so anything > Java 7 should work fine :-)
 
Geoff.D said:
Pretty sure the JAVA version is the issue. Had a similar problem on a PC recently that is used in a BOYD environment but not with Zertops Line test tool.
Click to expand...

Did you manage to sort it by updating java?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X