Official Vox DSL feedback thread

AfricanTech said:
Nimz, there is something weird going on with your local network (first hop)
Click to expand...
Okay if that is the case, how come I'm still getting full speed on the FNB account yet as soon as I switch to the vox account, its dead?

P.s I've had this setup for over 2 years now and had no issues. Could the modem or router be malfunctioning?
 
Nimz said:
Okay if that is the case, how come I'm still getting full speed on the FNB account yet as soon as I switch to the vox account, its dead?

P.s I've had this setup for over 2 years now and had no issues. Could the modem or router be malfunctioning?
Click to expand...

Keep the FNB account on your modem for a bit and see if it stays full speed. Something on your internal network is definitely wrong, the ethernet cable could be faulty or the router and modem setup need to be redone, I have no idea why your router would be 10.0.0.2 and your modem 192.168.1.1, I would have set the router to 192.168.1.1 and have the modem 192.168.1.2.
 
Nimz said:
1. Okay if that is the case, how come I'm still getting full speed on the FNB account yet as soon as I switch to the vox account, its dead?

2. P.s I've had this setup for over 2 years now and had no issues. Could the modem or router be malfunctioning?
Click to expand...

1. Not sure - when you switch back to vox from FNB does it go pear shaped immediately?

2. Yes it could be.

Are you sure that you don't have a routing rule between the router and the modem that is causing an issue on that first hop?

Edit: I just checked mine, and even though my modem (192.168.1.1) and router (192.168.88.1) have different IP ranges, I only see the router IP when I do a tracert - not sure why you see both ie router (10.0.0.1) and modem (192.168.1.1)

When you are connected via FNB, what does your trace route look like?

That first hop is really weird - it really shouldn't be that slow.

I have a router connected to a modem, and until I rebooted both of them, I had endless problems - don't know why - similarly to you, when I switched ISP (before the reboot) I would get better speed (but not for very long).

Good luck.
 
Last edited:
Soul Assassin said:
Keep the FNB account on your modem for a bit and see if it stays full speed. Something on your internal network is definitely wrong, the ethernet cable could be faulty or the router and modem setup need to be redone, I have no idea why your router would be 10.0.0.2 and your modem 192.168.1.1, I would have set the router to 192.168.1.1 and have the modem 192.168.1.2.
Click to expand...

Yeah, I noted that as well.

I have my router and modem on separate ranges (long story) but with the correct routing rules it works fine.

@Nimz, are you sure that DHCP is enabled on only one of the two devices?
 
what is going on, internet is totally dead.

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 3565 ms 3659 ms 3751 ms 41.193.164.85
4 * 3894 ms * 41.193.164.86
5 * 2537 ms 2635 ms 41.193.164.92
6 2746 ms 2993 ms 3114 ms 41.193.119.13
7 3026 ms 2965 ms 3000 ms 41.193.119.30
8 3127 ms 3182 ms 3267 ms mweb.jb1.napafrica.net [196.46.25.145]
9 3398 ms 3397 ms 3499 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
10 * 3652 ms 3724 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 * * 3852 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 1360 ms 1910 ms 2001 ms 196.28.178.66
13 2389 ms 2352 ms 2156 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

14 2352 ms 2367 ms 2351 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 2677 ms 2596 ms 2583 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 2872 ms 2821 ms 2716 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
 
Tracing route to 41-86-110-143.mweb.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 10 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 811 ms 797 ms 801 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
4 9 ms 8 ms 8 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
5 10 ms 10 ms 9 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
6 10 ms 10 ms 10 ms optinet.ct1.napafrica.net [196.10.140.145]
7 14 ms 14 ms 11 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
8 10 ms 10 ms 10 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
9 11 ms 10 ms 10 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
10 10 ms 9 ms 11 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

11 11 ms 10 ms 11 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
12 11 ms 11 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 10 ms 10 ms 11 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
 
rebooted router

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 12 ms 11 ms 11 ms 41.193.164.85
4 11 ms 12 ms 12 ms 41.193.164.86
5 12 ms 11 ms 12 ms 41.193.164.92
6 705 ms 1440 ms 2790 ms 41.193.119.13
7 2448 ms 909 ms 1294 ms 41.193.119.30
8 * 3068 ms 1894 ms mweb.jb1.napafrica.net [196.46.25.145]
9 1403 ms 2093 ms 3155 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
10 3362 ms * 2421 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 2684 ms 2718 ms 2792 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 3121 ms 3066 ms 1950 ms 196.28.178.66
13 1278 ms 1113 ms 1218 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.23

14 1396 ms 1241 ms 963 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 1313 ms


gonna switch to my telkom ISP and past results.
 
Telkom ISP, same results. port reset?

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 2592 ms 2692 ms 2834 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 3142 ms 2911 ms 3083 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 3226 ms 2465 ms 1600 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 1711 ms 1798 ms 1648 ms 105.187.249.74
7 2073 ms 2166 ms 2219 ms 105.187.249.74
8 2179 ms 2412 ms 2698 ms optinet.db1.napafrica.net [196.10.141.75]
9 2147 ms 2119 ms 2148 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
10 2288 ms 2350 ms 2392 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
11 2597 ms 2602 ms 2611 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
12 2779 ms 3016 ms 2942 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 1478 ms 1521 ms 1577 ms 196.28.178.66
14 1999 ms 2222 ms 2344 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234

15 2235 ms 2180 ms 2091 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
16 * 2030 ms 2017 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
17 1912 ms 1249 ms 1180 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
 
Telkom ISP, same results. port reset?

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 2592 ms 2692 ms 2834 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 3142 ms 2911 ms 3083 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 3226 ms 2465 ms 1600 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 1711 ms 1798 ms 1648 ms 105.187.249.74
7 2073 ms 2166 ms 2219 ms 105.187.249.74
8 2179 ms 2412 ms 2698 ms optinet.db1.napafrica.net [196.10.141.75]
9 2147 ms 2119 ms 2148 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
10 2288 ms 2350 ms 2392 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
11 2597 ms 2602 ms 2611 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
12 2779 ms 3016 ms 2942 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 1478 ms 1521 ms 1577 ms 196.28.178.66
14 1999 ms 2222 ms 2344 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234

15 2235 ms 2180 ms 2091 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
16 * 2030 ms 2017 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
17 1912 ms 1249 ms 1180 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
 
Deanoblado said:
Telkom ISP, same results. port reset?

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 2592 ms 2692 ms 2834 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 3142 ms 2911 ms 3083 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 3226 ms 2465 ms 1600 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 1711 ms 1798 ms 1648 ms 105.187.249.74
7 2073 ms 2166 ms 2219 ms 105.187.249.74
8 2179 ms 2412 ms 2698 ms optinet.db1.napafrica.net [196.10.141.75]
9 2147 ms 2119 ms 2148 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
10 2288 ms 2350 ms 2392 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
11 2597 ms 2602 ms 2611 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
12 2779 ms 3016 ms 2942 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 1478 ms 1521 ms 1577 ms 196.28.178.66
14 1999 ms 2222 ms 2344 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234

15 2235 ms 2180 ms 2091 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
16 * 2030 ms 2017 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
17 1912 ms 1249 ms 1180 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
Click to expand...

LOL! I'd be so pissed with that.

That's your exchange though. Long and hard battle lying ahead of you. Telkom doesn't give a damn :(
 
Method said:
LOL! I'd be so pissed with that.

That's your exchange though. Long and hard battle lying ahead of you. Telkom doesn't give a damn :(
Click to expand...

I hope not, my exchange has been pretty decent for a very long time. I hope the the tide hasn't changed. to make things worse they stopped laying fibre a few blocks from me.
 
Deanoblado said:
I hope not, my exchange has been pretty decent for a very long time. I hope the the tide hasn't changed. to make things worse they stopped laying fibre a few blocks from me.
Click to expand...

I think a port reset will resolve your issue... Call Telkom.
 
Deanoblado said:
I hope not, my exchange has been pretty decent for a very long time. I hope the the tide hasn't changed. to make things worse they stopped laying fibre a few blocks from me.
Click to expand...

Yep, I also have exchange issues (better now), but it was never as bad as yours.

And I fell 300m short from VDSL :(
 
I was testing the Glasnost online shaper tester. (http://broadband.mpi-sws.org/transparency/glasnost.php)

It confirmed they aren't limiting YouTube, which is great.

I got a surprising result when I went on to do the BitTorrent test.

Can anyone explain what this means?

Glasnost: Test if your ISP is shaping your traffic
Results for your host (dsl-197-245-124-232.voxdsl.co.za - 197.245.124.232):
Are certain ports blocked for all traffic?

3 out of 3 control flow transfers on port 6881 failed to upload any data. It seems like your ISP hinders you from uploading control flow traffic on port 6881 to our test server.

3 out of 3 control flow transfers on port 36306 failed to upload any data. It seems like your ISP hinders you from uploading control flow traffic on port 36306 to our test server.
 
Nimz, your router probably has open ports to the world. What happens is, on other ISP accounts these dont get attacked, but on VOX they probably get attacked.

For example, dns might be open, and some bots are using it for dns amplification ddos attacks.

To fix that, check firewall settings ect. Just using another router that doesn't have the ports open, might also fix your latency issues on VOX.
I have seen this happen with other people on VOX accounts, as well as my own when I had RDP port open to the world. As soon as I firewall it off, the issues stopped.

The attack is not the issue, its the cause. The issue is, the attack causes your router to flood your upload on the DSL line, causing massive latency, and slow download speeds.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X