Status
Not open for further replies.
MFN Lonehill with CISP as ISP, internet access is sporadic.

Code:
$ ping www.google.com
PING www.google.com (216.58.223.36): 56 data bytes
64 bytes from 216.58.223.36: icmp_seq=0 ttl=58 time=6.299 ms
64 bytes from 216.58.223.36: icmp_seq=1 ttl=58 time=34.505 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 216.58.223.36: icmp_seq=4 ttl=58 time=6.492 ms
64 bytes from 216.58.223.36: icmp_seq=5 ttl=58 time=7.405 ms
64 bytes from 216.58.223.36: icmp_seq=6 ttl=58 time=6.873 ms
64 bytes from 216.58.223.36: icmp_seq=7 ttl=58 time=7.465 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 216.58.223.36: icmp_seq=10 ttl=58 time=6.448 ms
64 bytes from 216.58.223.36: icmp_seq=11 ttl=58 time=6.484 ms
64 bytes from 216.58.223.36: icmp_seq=12 ttl=58 time=8.190 ms
64 bytes from 216.58.223.36: icmp_seq=13 ttl=58 time=6.525 ms
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
64 bytes from 216.58.223.36: icmp_seq=16 ttl=58 time=7.487 ms
64 bytes from 216.58.223.36: icmp_seq=17 ttl=58 time=6.312 ms
64 bytes from 216.58.223.36: icmp_seq=18 ttl=58 time=49.577 ms
64 bytes from 216.58.223.36: icmp_seq=19 ttl=58 time=7.295 ms
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 216.58.223.36: icmp_seq=22 ttl=58 time=7.373 ms
64 bytes from 216.58.223.36: icmp_seq=23 ttl=58 time=6.881 ms
64 bytes from 216.58.223.36: icmp_seq=24 ttl=58 time=7.367 ms
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
64 bytes from 216.58.223.36: icmp_seq=28 ttl=58 time=7.070 ms
64 bytes from 216.58.223.36: icmp_seq=29 ttl=58 time=8.165 ms
64 bytes from 216.58.223.36: icmp_seq=30 ttl=58 time=7.314 ms
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
64 bytes from 216.58.223.36: icmp_seq=34 ttl=58 time=6.399 ms
64 bytes from 216.58.223.36: icmp_seq=35 ttl=58 time=6.509 ms
64 bytes from 216.58.223.36: icmp_seq=36 ttl=58 time=8.139 ms
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
64 bytes from 216.58.223.36: icmp_seq=40 ttl=58 time=7.240 ms
64 bytes from 216.58.223.36: icmp_seq=41 ttl=58 time=14.456 ms
64 bytes from 216.58.223.36: icmp_seq=42 ttl=58 time=8.503 ms
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
64 bytes from 216.58.223.36: icmp_seq=46 ttl=58 time=6.241 ms
64 bytes from 216.58.223.36: icmp_seq=47 ttl=58 time=8.747 ms
64 bytes from 216.58.223.36: icmp_seq=48 ttl=58 time=7.082 ms
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
64 bytes from 216.58.223.36: icmp_seq=52 ttl=58 time=6.542 ms
64 bytes from 216.58.223.36: icmp_seq=53 ttl=58 time=6.803 ms
64 bytes from 216.58.223.36: icmp_seq=54 ttl=58 time=32.515 ms
 
There is a switch related issue affecting Benoni, we've implemented a workaround and will be replacing it tomorrow.

Thanks PBCool.

As attached on a 50/50 line. Not dead, but not working so lekker as others put it. :p
 

Attachments

  • speedtest.jpg
    speedtest.jpg
    41.3 KB · Views: 37
Just signed up and wondering if there is an issue in the Durban area.... Can't seem to get much more than 40mbps on a 100mbps connection.
 
Vuma trenched in Farrarmere Benoni still up and down - pfSense box showing packet loss
 
Vuma trenched in Farrarmere Benoni still up and down - pfSense box showing packet loss

Same here in Northmead - up and down since this afternoon - again a few moments ago.... very frustrating
 
Vumatel trenched in Atlasville Boksburg also up and down. Very annoying
 
@PBCool

Still look like something up between JHB and CPT from CPT side.

For example this trace:
Code:
 Host                                                                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. router.lan                                                                                      0.0%    12    0.4   0.4   0.4   0.5   0.0
 2. 155.93.227.1                                                                                    0.0%    11    1.3  19.0   1.2  90.7  34.5
 3. c3h-backbone.coolideas.co.za                                                                    0.0%    11    1.1   1.1   1.0   1.2   0.0
 4. cd-backbone.coolideas.co.za                                                                     0.0%    11    1.3   1.3   1.3   1.4   0.0
 5. c6t-backbone.coolideas.co.za                                                                    0.0%    11  141.3  97.3  18.7 141.5  61.0
    c1p-backbone.coolideas.co.za
    uoa-cust.coolideas.co.za
 6. 154.0.4.53                                                                                     70.0%    11  161.1  67.9  21.3 161.1  80.7
    154.0.3.113
    uzh-cust.coolideas.co.za
 7. c35-backbone.coolideas.co.za                                                                   70.0%    11   21.5  22.1  21.3  23.6   1.3
    c39-backbone.coolideas.co.za
 8. u139-cust.coolideas.co.za                                                                      70.0%    11  161.3 115.4  21.4 163.5  81.4
 9. google.jinx.net.za                                                                             70.0%    11   20.0  22.1  20.0  24.4   2.2
10. 72.14.239.129                                                                                  70.0%    11   56.3  34.2  22.1  56.3  19.2

You can see this on my smokeping here:
https://netmon.heaven.za.net/smokeping/smokeping.cgi?target=Google.Google-JNB

Screenshot at 2018-10-15 21-11-47.png
 
Looks like equal cost load balancing from CPT to JHB through the direct path and through LON. No idea what you using for your IGP but that probably need some tweaking after something changed.
 
I continue to be perplexed at the poor upload performance on my account, specifically Dropbox. I barely exceed 12Mbps. What gives?

I got in excess of 20Mbps when connected to MTN LTE (basically 80% of max attainable upload speed on the MTN account).
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X