Vox Telecom Fatpipe

cvanwie said:
If your second hop doesn't display, simply ping telkom-bras.vox.co.za (will only work while on a DSL line).

That means that you are on Telkom's Alcatel equipment instead of the Huawei. Nothing major, just the equipment doesn't allow ICMP traffic.
Click to expand...
Pinging telkom-bras.vox.co.za [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
AntiGanda said:
Pinging telkom-bras.vox.co.za [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Click to expand...

That's expected. Your second hop reports just fine. The fact that hop 3 doesn't report is concerning. Either an exchange, port, or line fault. Or the packets are not being re-sent and the problem comes in earlier.

You need to run mtr tests to ascertain where the packets are dropping. From there Vox or Telkom can assist. Tracerts are entirely useless for your problem...
 
DJ... said:
That's expected. Your second hop reports just fine. The fact that hop 3 doesn't report is concerning. Either an exchange, port, or line fault. Or the packets are not being re-sent and the problem comes in earlier.

You need to run mtr tests to ascertain where the packets are dropping. From there Vox or Telkom can assist. Tracerts are entirely useless for your problem...
Click to expand...
Thanks for the input. I've sent multiple plots and traces.

Vox and Telkom blame each other. I do know that Telkom testing is minimal - they do a port reset and close the fault!


Tracing route to gunsite.co.za [207.7.86.125]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 742 ms 102 ms 9 ms 41.193.121.9
4 9 ms 9 ms 9 ms 41.193.121.10
5 10 ms 16 ms 20 ms 209.203.1.41
6 10 ms 10 ms 9 ms 41.193.120.113
7 176 ms 187 ms 176 ms 196.41.24.174
8 177 ms 176 ms 177 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 * * * Request timed out.
10 * * * Request timed out.
11 279 ms 279 ms 278 ms COLO4-DALLA.ear1.Dallas1.Level3.net [8.9.232.74]

12 280 ms 279 ms 280 ms Jcore4.0.dal.colo4.com [206.123.64.218]
13 278 ms 278 ms 278 ms 72.249.129.125
14 279 ms 278 ms 279 ms 67.222.0.131
15 278 ms 279 ms 278 ms host.gunsite.co.za [207.7.86.125]

Trace complete.
--
The huge difference is ping of the 3 tests per hop is something new.
I was getting timeouts all morning to any site, but Vox says this is not a problem. However I'm only doing the tests and traces because the experience is poor.
 
Last edited:
AntiGanda said:
Thanks for the input. I've sent multiple plots and traces.

Vox and Telkom blame each other. I do know that Telkom testing is minimal - they do a port reset and close the fault!
Click to expand...

You're dropping packets somewhere. Tracerts won't show that. You need to find out where they're dropping so the network operator in question can dig into the problem for you, or you can resolve it yourself on your local network...
 
If the problem was to do with ICMP equipment affecting it, then the traces should be consistent.
They are not.

{This trace was from this morning at around 10AM}

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 * * * Request timed out.
4 8 ms 9 ms 9 ms 41.193.121.10
5 10 ms 10 ms 9 ms 209.203.1.41
6 9 ms 10 ms 10 ms 41.193.120.113
7 177 ms 175 ms 176 ms 196.41.24.174
8 176 ms 176 ms 176 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 * * * Request timed out.
10 * * * Request timed out.
11 193 ms 229 ms 192 ms 195.16.162.254
12 190 ms 190 ms 191 ms core11.hetzner.de [213.239.203.137]
13 190 ms 190 ms 190 ms core13.hetzner.de [213.239.203.198]
14 193 ms 192 ms 192 ms ex9k2.rz1.hetzner.de [213.239.203.214]
15 190 ms 190 ms 189 ms dedi354.nur4.host-h.net [78.46.9.234]
===

{I repeated this trace at 1:35PM}
Tracing route to www.avcom.co.za [78.46.9.234]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 9 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 10 ms 10 ms 9 ms 41.193.121.9
4 9 ms 11 ms 9 ms 41.193.121.10
5 9 ms 10 ms 10 ms 209.203.1.41
6 10 ms 10 ms 10 ms 41.193.120.113
7 176 ms 176 ms 176 ms 196.41.24.174
8 176 ms 183 ms 176 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 186 ms 185 ms 255 ms ae-1-60.edge7.Frankfurt1.Level3.net [4.69.154.11
]
10 186 ms * 187 ms ae-1-60.edge7.Frankfurt1.Level3.net [4.69.154.11
]
11 191 ms 190 ms 190 ms 195.16.162.254
12 190 ms 190 ms 190 ms core12.hetzner.de [213.239.245.25]
13 193 ms 193 ms 192 ms core13.hetzner.de [213.239.203.202]
14 193 ms 192 ms 192 ms ex9k2.rz1.hetzner.de [213.239.203.214]
15 191 ms 191 ms 190 ms dedi354.nur4.host-h.net [78.46.9.234]

Trace complete.
 
DJ... said:
You're dropping packets somewhere. Tracerts won't show that. You need to find out where they're dropping so the network operator in question can dig into the problem for you, or you can resolve it yourself on your local network...
Click to expand...
cvanwie asked me to do Pingplots which also show route changes and packet loss. He sent me a link to pingplotter.com I spent a good hour or more on them and submitted them. He then said Pingplot had a known issue with packet loss and the tests weren't useable so I must use Windows tracert. Go figure!

It's very frustrating!
 
AntiGanda said:
cvanwie asked me to do Pingplots which also show route changes and packet loss. He sent me a link to pingplotter.com I spent a good hour or more on them and submitted them. He then said Pingplot had a known issue with packet loss and the tests weren't useable so I must use Windows tracert. Go figure!

It's very frustrating!
Click to expand...

Bottom line, you need to run mtr tests to see where the packet loss is happening and solve the fundamental problem with the dropped packets. It's a fairly simple process and is why we don't use tracerts much in our business as they only tell half the story. My suspicion is the packets are dropping on hop 1 or 2. If 3, it's Vox's issue. If it's 2, it's Telkom's issue. If it's on 1 (or your internal network) it's your problem, and your ISP can assist to trace the root cause...
 
There was a brief outage on a couple of local sites a few minutes ago. Here is a tracert:

Code: 
Tracing route to [url]www.mybroadband.co.za[/url] [197.242.89.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home [192.168.0.1]
  2     9 ms     9 ms     9 ms  dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
  3     *        *        *     Request timed out.
  4    11 ms    11 ms    10 ms  41.193.121.38
  5    11 ms    21 ms    18 ms  196.41.29.233
  6    11 ms    10 ms    10 ms  africainx.ct1.napafrica.net [196.10.140.7]
  7    28 ms    28 ms    28 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.13.66]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Don't think this was a Vox specific issue, but thought I would post it anyway as I am using a Vox account... This happened briefly earlier today as well. iol.co.za was also affected.

No feedback required, just posting it for info purposes...

Phaedrus
 
IdlePhaedrus said:
There was a brief outage on a couple of local sites a few minutes ago. Here is a tracert:

Code: 
Tracing route to [url]www.mybroadband.co.za[/url] [197.242.89.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home [192.168.0.1]
  2     9 ms     9 ms     9 ms  dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
  3     *        *        *     Request timed out.
  4    11 ms    11 ms    10 ms  41.193.121.38
  5    11 ms    21 ms    18 ms  196.41.29.233
  6    11 ms    10 ms    10 ms  africainx.ct1.napafrica.net [196.10.140.7]
  7    28 ms    28 ms    28 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.13.66]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Don't think this was a Vox specific issue, but thought I would post it anyway as I am using a Vox account... This happened briefly earlier today as well. iol.co.za was also affected.

No feedback required, just posting it for info purposes...

Phaedrus
Click to expand...
Yes, the forum was unreachable as well. I swapped accounts and here I am.
 
cvanwie said:
If your second hop doesn't display, simply ping telkom-bras.vox.co.za (will only work while on a DSL line).

That means that you are on Telkom's Alcatel equipment instead of the Huawei. Nothing major, just the equipment doesn't allow ICMP traffic.
Click to expand...

Tracing route to telkom-bras.vox.co.za [155.239.255.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 6 ms 6 ms 6 ms 155.239.255.250

Trace complete.
 
DJ... said:
It's an issue with Cloudfare. Not any specific ISP...
Click to expand...

Agreed, that appears to be the case, hence the London routing:

Code: 
Tracing route to [url]www.mybroadband.co.za[/url] [104.20.72.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home [192.168.0.1]
  2     9 ms     9 ms     9 ms  dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
  3    12 ms    11 ms   201 ms  41.193.121.37
  4    10 ms    10 ms    11 ms  41.193.121.38
  5    11 ms    11 ms    11 ms  196.41.29.233
  6    12 ms    12 ms    11 ms  41.193.120.121
  7   178 ms   178 ms   177 ms  196.41.24.174
  8   178 ms   177 ms   179 ms  ldn-b3-link.telia.net [213.248.100.161]
  9   178 ms   245 ms   178 ms  ldn-bb2-link.telia.net [62.115.134.138]
 10   181 ms   180 ms   178 ms  ldn-b5-link.telia.net [80.91.246.147]
 11   178 ms   178 ms   178 ms  cloudflare-ic-306325-ldn-b3.c.telia.net [62.115.42.242]
 12   178 ms   178 ms   178 ms  104.20.72.110

Trace complete.
 
Third hop does appear to be an issue though, and according to whois, that is certainly a Vox IP:

Code: 
Tracing route to www.mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home [192.168.0.1]
  2    10 ms     9 ms     9 ms  dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
  3  2530 ms  2514 ms  2516 ms  41.193.121.37
  4    10 ms    10 ms    11 ms  41.193.121.38
  5    12 ms    10 ms    10 ms  196.41.29.233
  6    11 ms    11 ms    11 ms  41.193.120.121
  7   179 ms   178 ms   178 ms  196.41.24.174
  8   179 ms   177 ms   177 ms  ldn-b3-link.telia.net [213.248.100.161]
  9   178 ms   239 ms   178 ms  ldn-bb2-link.telia.net [62.115.134.138]
 10   178 ms   180 ms   178 ms  ldn-b5-link.telia.net [213.155.132.197]
 11   178 ms   178 ms   178 ms  cloudflare-ic-306325-ldn-b3.c.telia.net [62.115.42.242]
 12   178 ms   178 ms   178 ms  104.20.72.110
 
Howzit guys, anyone buy one of those 100/300 gig VOX specials that would like to get rid of them?
 
On MWEB account at the moment.... and also having MyBB issues today. As for my VOX, been loving it. @juBa, I have 2 X 100gb accounts on the special price, but I'm not parting with them :D
 
IdlePhaedrus said:
Third hop does appear to be an issue though, and according to whois, that is certainly a Vox IP:

Code: 
Tracing route to www.mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home [192.168.0.1]
  2    10 ms     9 ms     9 ms  dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
  3  2530 ms  2514 ms  2516 ms  41.193.121.37
  4    10 ms    10 ms    11 ms  41.193.121.38
  5    12 ms    10 ms    10 ms  196.41.29.233
  6    11 ms    11 ms    11 ms  41.193.120.121
  7   179 ms   178 ms   178 ms  196.41.24.174
  8   179 ms   177 ms   177 ms  ldn-b3-link.telia.net [213.248.100.161]
  9   178 ms   239 ms   178 ms  ldn-bb2-link.telia.net [62.115.134.138]
 10   178 ms   180 ms   178 ms  ldn-b5-link.telia.net [213.155.132.197]
 11   178 ms   178 ms   178 ms  cloudflare-ic-306325-ldn-b3.c.telia.net [62.115.42.242]
 12   178 ms   178 ms   178 ms  104.20.72.110
Click to expand...
Thanks, that's very helpful to me. That IP range is the same as my problem one and 3rd hop is ISP.

Come on Vox, please acknowledge your problem and fix.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X