Official Vox DSL feedback thread

AntiGanda said:
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.
Click to expand...

Pretty sure I saw cvanwie saying something about the fault already logged with Telkom? They aren't ignoring it.

I'm fine here in Joburg. My issue was resolved by Telkom.

#justsaying
 
Method said:
Constantly...why would they switch it on and off? Makes no sense.



Can't blame cvanwie :whistle:
Click to expand...
It could be related to work in progress, live testing and so forth. On the 1st it was fine (everything the whole day) then boom, it's broken again. Either that or something else.
 
Method said:
Pretty sure I saw cvanwie saying something about the fault already logged with Telkom? They aren't ignoring it.

I'm fine here in Joburg. My issue was resolved by Telkom.

#justsaying
Click to expand...
Of course you are.

The problem was and remains in the Cape. Doesn't it always.
 
AntiGanda said:
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.
Click to expand...

Unsure what in my post could be considered "crowing". You ask for help and then spit in the face of those who offer it. I am also in CPT, was also affected by the latency issues which were resolved with Telkom, and am currently not seeing any of your symptoms, during any time of day. Good luck resolving your issues with that attitude.
 
This is interesting. When it does ping correctly, like now all of a sudden, I get the full address of the servers on each hop.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 9 ms 10 ms 10 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
121.9]
4 8 ms 9 ms 10 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
93.121.10]
5 9 ms 10 ms 9 ms vox-b2b-pts-barrack-ipc-int [209.203.1.41]
6 10 ms 10 ms 10 ms 41.193.120.113
7 176 ms 175 ms 175 ms 196.41.24.174
8 177 ms 176 ms 175 ms ldn-b3-link.telia.net [213.248.100.161]
9 176 ms 176 ms 176 ms twitter-ic-302263-ldn-b3.c.telia.net [62.115.34.
]
10 276 ms 276 ms 275 ms ae65.atl1-er2.twttr.com [192.133.76.19]
11 276 ms 276 ms 276 ms 199.16.156.102

Trace complete.

It's all clearly Vox-related equipment on those 1st hops. The new full address also suggests a change - maybe DNS or something.
 
AntiGanda said:
JusitinTek, MicR and Pat are all the same person and team. Low post troll. Easy kill.
Click to expand...

I don't understand to why you are being so aggressive about the statement?

And on a side note Justintek, Micr, Dankbanker, throwaway420 and Slvr are the same person. I don't know how I resemble that idiot.
 
There appear to be multiple routes in CPT:

Code: 
traceroute to 199.16.156.102 (199.16.156.102), 30 hops max, 60 byte packets
 1  router.asus.com (192.168.0.1)  0.340 ms  0.329 ms  0.381 ms
 2  dsl-197-xxx-xxx-1.voxdsl.co.za (197.xxx.xxx.1)  15.226 ms  16.028 ms  16.394 ms
 3  * * *
 4  vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za (41.193.121.38)  19.988 ms  20.364 ms  20.772 ms
 5  vox-b2b-pts-tygerberg-ipc-int (196.41.29.233)  21.566 ms  21.568 ms  21.946 ms
 6  41.193.120.121 (41.193.120.121)  21.959 ms  21.353 ms  22.145 ms
 7  196.41.24.174 (196.41.24.174)  189.383 ms  183.869 ms  183.934 ms
 8  ldn-b3-link.telia.net (213.248.100.161)  184.370 ms  183.542 ms  183.962 ms
 9  twitter-ic-302264-ldn-b3.c.telia.net (62.115.34.10)  183.938 ms  183.564 ms  183.989 ms
10  ae65.atl1-er2.twttr.com (192.133.76.19)  284.030 ms  284.362 ms  283.977 ms
11  199.16.156.102 (199.16.156.102)  283.182 ms  283.120 ms  283.104 ms
 
PostManPat said:
I don't understand to why you are being so aggressive about the statement?

And on a side note Justintek, Micr, Dankbanker, throwaway420 and Slvr are the same person. I don't know how I resemble that idiot.
Click to expand...
You were cute once with the Pat/Pot gimmick, but time to stop now methinks.
 
Seeyou said:
There appear to be multiple routes in CPT:

Code: 
traceroute to 199.16.156.102 (199.16.156.102), 30 hops max, 60 byte packets
 1  router.asus.com (192.168.0.1)  0.340 ms  0.329 ms  0.381 ms
 2  dsl-197-xxx-xxx-1.voxdsl.co.za (197.xxx.xxx.1)  15.226 ms  16.028 ms  16.394 ms
 3  * * *
 4  vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za (41.193.121.38)  19.988 ms  20.364 ms  20.772 ms
 5  vox-b2b-pts-tygerberg-ipc-int (196.41.29.233)  21.566 ms  21.568 ms  21.946 ms
 6  41.193.120.121 (41.193.120.121)  21.959 ms  21.353 ms  22.145 ms
 7  196.41.24.174 (196.41.24.174)  189.383 ms  183.869 ms  183.934 ms
 8  ldn-b3-link.telia.net (213.248.100.161)  184.370 ms  183.542 ms  183.962 ms
 9  twitter-ic-302264-ldn-b3.c.telia.net (62.115.34.10)  183.938 ms  183.564 ms  183.989 ms
10  ae65.atl1-er2.twttr.com (192.133.76.19)  284.030 ms  284.362 ms  283.977 ms
11  199.16.156.102 (199.16.156.102)  283.182 ms  283.120 ms  283.104 ms
Click to expand...

Two main IPC routes, one in Barrack street and one in Tygerberg. Once the IPC is reached, traffic is then routed to NAPAfrica in Rondebosch which will do the rest of the peering.
 
Seeyou said:
There appear to be multiple routes in CPT:

Code: 
traceroute to 199.16.156.102 (199.16.156.102), 30 hops max, 60 byte packets
 1  router.asus.com (192.168.0.1)  0.340 ms  0.329 ms  0.381 ms
 2  dsl-197-xxx-xxx-1.voxdsl.co.za (197.xxx.xxx.1)  15.226 ms  16.028 ms  16.394 ms
 3  * * *
 4  vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za (41.193.121.38)  19.988 ms  20.364 ms  20.772 ms
 5  vox-b2b-pts-tygerberg-ipc-int (196.41.29.233)  21.566 ms  21.568 ms  21.946 ms
 6  41.193.120.121 (41.193.120.121)  21.959 ms  21.353 ms  22.145 ms
 7  196.41.24.174 (196.41.24.174)  189.383 ms  183.869 ms  183.934 ms
 8  ldn-b3-link.telia.net (213.248.100.161)  184.370 ms  183.542 ms  183.962 ms
 9  twitter-ic-302264-ldn-b3.c.telia.net (62.115.34.10)  183.938 ms  183.564 ms  183.989 ms
10  ae65.atl1-er2.twttr.com (192.133.76.19)  284.030 ms  284.362 ms  283.977 ms
11  199.16.156.102 (199.16.156.102)  283.182 ms  283.120 ms  283.104 ms
Click to expand...

Here's a clearer example:

BEFORE

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 9 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 13 ms 10 ms 10 ms 41.193.121.9
4 9 ms 8 ms 9 ms 41.193.121.10
5 10 ms 9 ms 9 ms 209.203.1.41

AFTER

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 10 ms 10 ms 9 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
121.9]
4 16 ms 9 ms 9 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
93.121.10]
5 9 ms 9 ms 9 ms vox-b2b-pts-barrack-ipc-int [209.203.1.41]
 
PostManPat said:
Two main IPC routes, one in Barrack street and one in Tygerberg. Once the IPC is reached, traffic is then routed to NAPAfrica in Rondebosch which will do the rest of the peering.
Click to expand...
.. and you would know that how?
 
Seeyou said:
Unsure what in my post could be considered "crowing". You ask for help and then spit in the face of those who offer it. I am also in CPT, was also affected by the latency issues which were resolved with Telkom, and am currently not seeing any of your symptoms, during any time of day. Good luck resolving your issues with that attitude.
Click to expand...

That's exactly what he does and that is why he keeps on moaning about the same shyte. In the end he's not going to get any help it it will be his own stupidity.
 
AntiGanda said:
This is interesting. When it does ping correctly, like now all of a sudden, I get the full address of the servers on each hop.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 9 ms 10 ms 10 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
121.9]
4 8 ms 9 ms 10 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
93.121.10]
5 9 ms 10 ms 9 ms vox-b2b-pts-barrack-ipc-int [209.203.1.41]
6 10 ms 10 ms 10 ms 41.193.120.113
7 176 ms 175 ms 175 ms 196.41.24.174
8 177 ms 176 ms 175 ms ldn-b3-link.telia.net [213.248.100.161]
9 176 ms 176 ms 176 ms twitter-ic-302263-ldn-b3.c.telia.net [62.115.34.
]
10 276 ms 276 ms 275 ms ae65.atl1-er2.twttr.com [192.133.76.19]
11 276 ms 276 ms 276 ms 199.16.156.102

Trace complete.

It's all clearly Vox-related equipment on those 1st hops. The new full address also suggests a change - maybe DNS or something.
Click to expand...

Common IT knowledge would tell me hop 3 is the Telkom side of the IPC and hop 4 is the Vox side of the IPC, which is EXACTLY what cvanwie said a few threads ago and also said it was logged with Telkom to get a permanent fix in place.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X