Official Vox DSL feedback thread

AntiGanda said:
And my Vox is kark again after a few days or sem-normality.

the 3rd hop problem is back again. Definitely a vox issue given the others having similar poor performance. Not a coincidence!

Tracing route to voxtelecom.co.za [196.41.6.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 1460 ms 1213 ms 1121 ms 41.193.121.9
4 9 ms 8 ms 9 ms 41.193.121.10
5 9 ms 10 ms 9 ms 209.203.1.41
6 10 ms 10 ms 10 ms 41.193.120.89
7 21 ms 21 ms 21 ms 41.193.106.105
8 21 ms 21 ms 20 ms 41.193.106.97
9 26 ms 25 ms 26 ms 41.193.106.101
10 25 ms 25 ms 25 ms 41.193.32.138
11 26 ms 24 ms 25 ms 196.41.6.140
12 * * * Request timed out.
13 * * * Request timed out.
14 * ^C
Click to expand...

Method said:
The third op is your exchange.

1st is your Internal IP
2nd your WAN IP
3rd is your exchange.

Really isn't hard to grasp that.
Click to expand...

Method said:
I had EXACTLY the same issues. I'm trying to help you, but it seems you're not interested at all. I've seen your comments here many many times and you just complain about the same thing over and over. If you don't want anyone's help, then why are you posting it here? Yell at their call centre staff then.

When I had the issue, I swapped to another ADSL account (WebAfrica) and the problem goes away for awhile and then comes back. Or when I reboot my router.

There is no ifs or buts about the 3rd hop. It's not any ISP. It's your exchange. I'm pretty sure MOST ADSL users have congestion on their exchanges as Telkom doesn't give a fig about ADSL (best effort).

I use a Vox account and I only have issues during peak times, which I know is the exchange. It seems to have gone away now for about 3 weeks since I spoke to Telkom (user on MyBB).
Click to expand...

Tinuva said:
Wrong information sadly.

1 = Router
2 = Telkom BRAS/Exchange/ect name. Although it has an ip that is mostly in the same ip range as your own ip, but sometimes not.
3 = 1st ISP IPC infrastructure device

Hop 2 nowadays gets blocked by Telkom on the newer exchanges.

ps. Antiganda's exchange looks 100% fine in that traceroute.
Click to expand...

FFS, not this again.

We know for a fact it's Telkom's equipment. Suck it up.

Read from here - http://mybroadband.co.za/vb/showthr...om-Fatpipe?p=16382625&viewfull=1#post16382625.
 
pop.gmail.com takes forever to come in and times out 50% of the time.
I switch back to Afrihost and everything comes in instantly ?

A trace if that helps:

Vox
Code: 
C:\>tracert pop.gmail.com

Tracing route to gmail-pop.l.google.com [64.233.184.109]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  dsl-197-245-40-1.voxdsl.co.za [197.245.40.1]
  3    26 ms    26 ms    28 ms  41.193.164.85
  4    32 ms    32 ms    31 ms  41.193.164.86
  5    67 ms    31 ms    32 ms  41.193.164.92
  6    32 ms    32 ms    33 ms  41.193.119.45
  7    98 ms    32 ms    32 ms  41.193.119.42
  8    25 ms    26 ms    25 ms  72.14.220.136
  9   194 ms   193 ms   194 ms  72.14.234.161
 10   201 ms   201 ms   201 ms  209.85.250.124
 11   201 ms   201 ms   201 ms  209.85.253.108
 12   206 ms   206 ms   214 ms  209.85.251.231
 13     *        *        *     Request timed out.
 14   207 ms   206 ms   207 ms  wa-in-f109.1e100.net [64.233.184.109]

Trace complete.
Afrihost
Code: 
C:\>tracert pop.gmail.com

Tracing route to gmail-pop.l.google.com [74.125.71.108]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  169-0-40-1.ip.afrihost.co.za [169.0.40.1]
  3     *        *        *     Request timed out.
  4    11 ms     9 ms    10 ms  dbn-up2.ip.adsl.co.za [169.1.5.162]
  5     9 ms     9 ms     9 ms  dbn-in1.ip.adsl.co.za [169.1.5.204]
  6     9 ms     9 ms    10 ms  41.162.84.192
  7    18 ms    18 ms    19 ms  172.18.1.162
  8    24 ms    24 ms    24 ms  72.14.194.206
  9   184 ms   184 ms   184 ms  72.14.234.161
 10   179 ms   179 ms   179 ms  209.85.250.124
 11   192 ms   192 ms   191 ms  209.85.253.208
 12   185 ms   186 ms   185 ms  209.85.249.14
 13     *        *        *     Request timed out.
 14   191 ms   191 ms   191 ms  wn-in-f108.1e100.net [74.125.71.108]

Trace complete.
 
I seem to be only getting half my line speed

Are there any issues currently?

Code: 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Home Server>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     1 ms     1 ms     1 ms  192.168.1.1
  3    12 ms    11 ms    11 ms  dsl-197-245-43-1.voxdsl.co.za [197.245.43.1]
  4     *        *        *     Request timed out.
  5    24 ms    23 ms    22 ms  41.193.164.86
  6    26 ms    25 ms    25 ms  41.193.164.92
  7    25 ms    26 ms    25 ms  41.193.119.13
  8    25 ms    55 ms    67 ms  41.193.119.38
  9    25 ms    27 ms    25 ms  72.14.220.136
 10    26 ms    26 ms    26 ms  72.14.237.239
 11    25 ms    25 ms    25 ms  jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users\Home Server>

4799771975.png

saix.jpg
 
Last edited:
PostmanPot said:
FFS, not this again.

We know for a fact it's Telkom's equipment. Suck it up.

Read from here - http://mybroadband.co.za/vb/showthr...om-Fatpipe?p=16382625&viewfull=1#post16382625.
Click to expand...

I don't see any facts there. So not sure what you want me to suck up on?

What I can tell you is this. Telkom's IPC setup makes use of half-duplex mpls vrfs.
So why that 1 ip has high latency, is probably because it still takes a longer router out over the ISPs network, hits their shaping devices and the line/pipe/vc they hit probably has some sort of limitation on, eg. low priority queue and then by the time it gets back in the traceroute it has high latency.

I will admit though, there is some interesting and strange traceroutes in these posts, and that may need some investigation as to what exactly is happening there.

Edit:
Ok I see cvanwie did say its on the upload vlan. What however is then odd, is how both ips on the upload /30 shows up in the traceroute, only the one on the ISP side should technically show up in a 1 direction traceroute.

That said, the IP is not the exchange, its in a MPLS VRF. So my initial post is semi correct.
If anything, that might mean latency on one of the backhaul paths from the Telkom exchange, towards the Telkom device that connects an ipc link to the ISP. Should be fairly interesting to troubleshoot, but will have to be done by a telkom tech.
 
Last edited:
Well though a Telkom tech needs to do the investigation, I highly suggest the ISP escalate to Telkom to investigate, not the ADSL escalations via uniweb, but instead via ipnet. Otherwise you won't get the correct people to look at it.
 
Tinuva said:
Well though a Telkom tech needs to do the investigation, I highly suggest the ISP escalate to Telkom to investigate, not the ADSL escalations via uniweb, but instead via ipnet. Otherwise you won't get the correct people to look at it.
Click to expand...
So the question remains. After reporting this for so long, why hasn't it been fixed? Is Vox just hoping it will go away?

(ignore Postman, he's a snake oil salesman of repute)
 
Nimz said:
I seem to be only getting half my line speed

Are there any issues currently?

Code: 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Home Server>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     1 ms     1 ms     1 ms  192.168.1.1
  3    12 ms    11 ms    11 ms  dsl-197-245-43-1.voxdsl.co.za [197.245.43.1]
  4     *        *        *     Request timed out.
  5    24 ms    23 ms    22 ms  41.193.164.86
  6    26 ms    25 ms    25 ms  41.193.164.92
  7    25 ms    26 ms    25 ms  41.193.119.13
  8    25 ms    55 ms    67 ms  41.193.119.38
  9    25 ms    27 ms    25 ms  72.14.220.136
 10    26 ms    26 ms    26 ms  72.14.237.239
 11    25 ms    25 ms    25 ms  jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users\Home Server>

View attachment 312235

View attachment 312241
Click to expand...

I checked the IPC and no congestion that would have slowed you down, also checked your user - no rate limits which would have slowed you down.

The trace route looks clean. The time out on hop 4, is to 41.193.164.85 since it's timing out, give it a straight ping and you should get a response back. Please respond with the value of the ping, thanks.
 
cvanwie said:
I checked the IPC and no congestion that would have slowed you down, also checked your user - no rate limits which would have slowed you down.

The trace route looks clean. The time out on hop 4, is to 41.193.164.85 since it's timing out, give it a straight ping and you should get a response back. Please respond with the value of the ping, thanks.
Click to expand...
Why are we seeing so many time-outs?

This used to be a rare event from my screen.
 
cvanwie said:
I checked the IPC and no congestion that would have slowed you down, also checked your user - no rate limits which would have slowed you down.

The trace route looks clean. The time out on hop 4, is to 41.193.164.85 since it's timing out, give it a straight ping and you should get a response back. Please respond with the value of the ping, thanks.
Click to expand...


Code: 
Pinging 41.193.164.85 with 32 bytes of data:
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59
Reply from 41.193.164.85: bytes=32 time=23ms TTL=59
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59

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

Seems to be back to normal now after a port reset
 
AntiGanda said:
So the question remains. After reporting this for so long, why hasn't it been fixed? Is Vox just hoping it will go away?

(ignore Postman, he's a snake oil salesman of repute)
Click to expand...

Seems it's only you being ignored... ;)

Props to cvanwie.
 
Nimz said:
Code: 
Pinging 41.193.164.85 with 32 bytes of data:
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59
Reply from 41.193.164.85: bytes=32 time=23ms TTL=59
Reply from 41.193.164.85: bytes=32 time=24ms TTL=59

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

Seems to be back to normal now after a port reset
Click to expand...
I had one too, but the problem returns. Port reset is temporary.
 
Seeyou said:
If a port reset resolves the problem (albeit temporarily), then how can the problem lie with the ISP?
Click to expand...
Your internet works and you now sit crowing, we get this behaviour. It's a type of pyschosis I imagine.

I don't know what's wrong with our ADSL or how properly to fix it. What I do know is that Telkom blames Vox and Vox get's shirty and shoves the blame back. Ultimately the customer loses.

What we need is teamwork. It appears as though the hardware is Vox's, so why can't they undertake to fix it together? This slopey shoulder and sniffy it's not our job attitude is not the right one.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X