Vox Telecoms ADSL international issues

fixx

Well-Known Member
Joined
Feb 13, 2006
Messages
288
Reaction score
7
Location
South Africa
Hi everyone

I seem to have intermittent loss of connectivity to international hosts using any protocol. I am using a VOX Telecoms account with the bolton uncapped option.

During any time of the day most international sites are down. Calling their support does not yield any results either as they don't really have the know how to troubleshoot the issue and I am constantly told to ask Telkom te reset the port etc. (Not sure how that will help me get my international connectivity back).

I have noticed strange behaviour when I traceroute to a few hosts. For example, I can connect to my one server hosted at the campus is Bryanston without a problem:

# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 100% 6 timeout
2 196.41.25.5 0% 5 7.7ms 7.8 7.5 8.1 0.2 <MPLS:L=4833,E=0>
3 196.41.25.6 0% 5 7ms 6.9 6.5 7.1 0.2
4 196.41.25.12 0% 5 7.3ms 13.2 6.6 38.4 12.6
5 41.193.119.9 0% 5 7.3ms 7.3 7 7.4 0.1 <MPLS:L=300016,E=0>
6 41.193.32.197 0% 5 7.7ms 7.7 7.5 8 0.2 <MPLS:L=581430,E=0>
7 41.193.118.98 0% 5 20.4ms 20.5 20.1 21.3 0.4
8 196.14.217.129 0% 5 20.2ms 20.1 19.7 20.3 0.2
9 196.35.227.188 0% 5 20.1ms 20.1 19.6 20.5 0.3
10 196.38.43.168 0% 5 21.5ms 21.2 20.8 21.6 0.3

But when I traceroute to IS' main name server, the packets route via a route with a 10.x.x.x IP :cry:
See traceroute below:

# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 100% 2 timeout
2 196.41.25.5 0% 2 7.8ms 9 7.8 10.1 1.2 <MPLS:L=4833,E=0>
3 196.41.25.6 0% 2 7ms 12.5 7 18 5.5
4 196.41.25.12 0% 2 6.8ms 6.9 6.8 6.9 0.1
5 41.193.119.9 0% 2 7ms 7.2 7 7.4 0.2 <MPLS:L=299904,E=0 L=37,E=0,T=1>
6 41.193.32.197 0% 2 8ms 7.9 7.7 8 0.2 <MPLS:L=556116,E=0 L=37,E=0,T=2>
7 10.221.0.3 0% 2 7.8ms 8.1 7.8 8.3 0.3
8 100% 2 timeout
9 100% 2 timeout
10 100% 1 timeout
11 100% 1 timeout
12 100% 1 timeout

Isn't 10.0.0.0/8 reserved for private use?

Here is a traceroute to www.cnn.com:

# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 100% 2 timeout
2 196.41.25.5 0% 2 7.5ms 8.1 7.5 8.6 0.6 <MPLS:L=4833,E=0>
3 196.41.25.6 0% 2 6.8ms 6.7 6.5 6.8 0.2
4 196.41.25.12 0% 2 6.8ms 7.2 6.8 7.5 0.4
5 41.193.119.9 0% 2 7.3ms 7.5 7.3 7.7 0.2 <MPLS:L=337056,E=0>
6 41.193.32.197 0% 2 7.6ms 7.8 7.6 8 0.2 <MPLS:L=618536,E=0>
7 196.41.9.10 0% 2 181.9ms 182.3 181.9 182.7 0.4 <MPLS:L=798642,E=0>
8 196.41.27.114 0% 2 191.3ms 190.8 190.3 191.3 0.5
9 195.50.120.13 0% 2 190.5ms 190.6 190.5 190.7 0.1
10 4.69.150.197 0% 2 284.7ms 277.7 270.6 284.7 7.1
11 100% 2 timeout
12 100% 2 timeout
13 100% 2 timeout
14 100% 2 timeout
15 100% 1 timeout

Is anyone else also experiencing the same issues on one of these 'wonderful' unshaped VOX accounts?
 
There is nothing wrong with the 10.0.0.0/8 ips showing up in traceroutes, it just mean it was set up as the primary ip on that interface, while it also carry public traffic.

What IP are you tracing to, or what do you see as "IS's main name server" which could really be anything.
 
Top
Sign up to the MyBroadband newsletter
X