Vox Telecom Fatpipe

SirFooK'nG said:
edited my response above after rebooting ... This only in the last week .... never before.
Click to expand...

I'm telling you, something is up with your exchange, rebooting your router is a temporary fix, don't change anything and test in a hour or two, I bet your traceroute shows high latency again.
 
Soul Assassin said:
I'm telling you, something is up with your exchange, rebooting your router is a temporary fix, don't change anything and test in a hour or two, I bet your traceroute shows high latency again.
Click to expand...

Yip ... its fukt.

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

C:\Users\Graham>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 192.168.0.1
2 * * * Request timed out.
3 996 ms 962 ms 1068 ms 41.193.3.101
4 1004 ms 934 ms 919 ms 41.193.3.102
5 933 ms 1001 ms 1018 ms 196.41.12.0
6 822 ms 1054 ms 1122 ms 41.193.32.137
7 924 ms 953 ms 759 ms 41.193.32.198
8 1162 ms 1136 ms 969 ms 41.193.119.42
9 1031 ms 928 ms 1134 ms 72.14.220.136
10 275 ms 450 ms 487 ms 72.14.237.239
11 360 ms 416 ms 458 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users\Graham>

Direct Afrihost Dialup


C:\Users\Graham>TRACERT WWW.GOOGLE.CO.ZA

Tracing route to WWW.GOOGLE.CO.ZA [216.58.223.3]
over a maximum of 30 hops:

1 * * * Request timed out.
2 971 ms 884 ms 954 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
3 944 ms 838 ms 661 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
4 879 ms 752 ms 888 ms 41.162.84.192
5 485 ms 537 ms 468 ms 172.18.1.162
6 219 ms 159 ms 136 ms 72.14.194.206
7 770 ms 728 ms 865 ms 72.14.237.239
8 738 ms 857 ms 1034 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users\Graham>
 
Last edited:
I've ben having some Disconnects lately, some cases extreme, where it disconnects around 20-30 time an hour. I checked my line sync info, and the SNR's is constant, and i do not lose sync.

It sometimes tell me that my authentication failed.
 
SirFooK'nG said:
3 faults reported in 3 weeks ... what fun.
Click to expand...
Have you tried another router? From my experience, high latency to exchange usually indicates exchange congestion... but if rebooting the modem fixes your ping, then there's a good chance it could be the router, not the exchange!
 
fragtion said:
Have you tried another router? From my experience, high latency to exchange usually indicates exchange congestion... but if rebooting the modem fixes your ping, then there's a good chance it could be the router, not the exchange!
Click to expand...

I whole heartily disagree with that.
 
Soul Assassin said:
I whole heartily disagree with that.
Click to expand...
And you provide no justification/reason to support your confident, whole-hearted disagreement?
Exchange congestion literally means that the exchange's capacity (ATM/Metro-ethernet backhaul to the ESR/BNG respectively) to serve all clients connected to that exchange, is saturated. So it actually affects all clients on the exchange at the same time. This is why typically with exchange congestion, rebooting your router won't make a difference - you just sync back to the same port on the same exchange which is already overloaded at that time of the day. Obviously one client rebooting their router is not going to resolve the entire exchange's capacity congestion problem. The fact that his ping resolves after rebooting the modem therefore indicates that another problem is likely at play. So my question to you is as follows: What is your definition of exchange congestion then, and how exactly do you think that rebooting a modem should resolve ping issues, if the problem is caused by exchange congestion? I do look forward to a more informed response from you than a merely emotional one this time around? :)
 
Last edited:
fragtion said:
And you provide no justification/reason to support your confident, whole-hearted disagreement?
Exchange congestion literally means that the exchange's capacity (ATM/Metro-ethernet backhaul to the ESR/BNG respectively) to serve all clients connected to that exchange, is saturated. This is why typically with exchange congestion, rebooting your router won't make a difference - you just sync back to the same port on the same exchange which is already overloaded at that time of the day. Obviously one client rebooting their router is not going to resolve the entire exchange's capacity congestion problem. So my question to you is as follows: What is your definition of exchange congestion then, and why do you think that rebooting a modem should resolve ping issues if the problem is caused by exchange congestion? I look forward to an informed response which, hopefully this time, will be less of an emotional one supported with little meaningful substance otherwise? ;)
Click to expand...

You misunderstood, I totally agree about exchange congestion, I disagree with the router being at fault, making it look like exchange congestion, which you also just stated without any facts, Mr. pot calling the kettle black.

You can just search the forums, it is known fact that rebooting your modem or switching ISP's acts as a sort of port reset which for a very brief period will alleviate the exchange congestion symptoms.
 
Soul Assassin said:
You misunderstood, I totally agree about exchange congestion, I disagree with the router being at fault, making it look like exchange congestion, which you also just stated without any facts, Mr. pot calling the kettle black.

You can just search the forums, it is known fact that rebooting your modem or switching ISP's acts as a sort of port reset which for a very brief period will alleviate the exchange congestion symptoms.
Click to expand...
I'm just trying to understand how rebooting your modem is supposed to help with exchange congestion in principle. I agree with you that router faults are usually not a common cause for high latency (apart from wireless or other problems on the user's own network), but with a basic understanding of how these things work, I suggested that as a logical conclusion based on the fact that rebooting one's own router should have no observable affect if the problem is caused by a congested exchange. Obviously this problem is caused by something else then, such as a faulty router OR faulty DSLAM, or the DSLAM's port/configuration, etc. It can't be congestion because if it was, then I think we can agree that rebooting the router would have no effect because you'll just sync back to the busy exchange, right ?
 
fragtion said:
I'm just trying to understand how rebooting your modem is supposed to help with exchange congestion in principle. I agree with you that router faults are usually not a common cause for high latency (apart from wireless or other problems on the user's own network), but with a basic understanding of how these things work, I suggested that as a logical conclusion based on the fact that rebooting one's own router should have no observable affect if the problem is caused by a congested exchange. Obviously this problem is caused by something else then, such as a faulty router OR faulty DSLAM, or the DSLAM's port/configuration, etc. It can't be congestion because if it was, then I think we can agree that rebooting the router would have no effect because you'll just sync back to the busy exchange, right ?
Click to expand...

That is why I stated for a very brief period it will alleviate the symptoms not fix them, that is why the user immediately reported back that the reboot did not fix the issue, we can also clearly see that it's not a Wi-Fi issue since his trace showed <1 ms, which would indicate his modem is working just fine and he is using Ethernet.

If he does have a backup modem he should definitely test it out, but I will eat my hat if that fixes the issue.
 
I recently discovered that my line filter seems to be a bit faulty. So removed it and my line is flying again. Maybe give that a try if you haven't already?
 
Type RSA said:
I recently discovered that my line filter seems to be a bit faulty. So removed it and my line is flying again. Maybe give that a try if you haven't already?
Click to expand...

I'm so glad to hear that you finally found the cause of the problem!
 
Thanks for the late nights, intriguing and fascinating issues, great banter, and product suggestions!

My last day @ Vox has been incredibly busy and before I left, I wanted to say "Cheers!" to you all as well.

All the best

-Chris
 
cvanwie said:
Thanks for the late nights, intriguing and fascinating issues, great banter, and product suggestions!

My last day @ Vox has been incredibly busy and before I left, I wanted to say "Cheers!" to you all as well.

All the best

-Chris
Click to expand...

Good luck and all the best with your future endeavours Chris!
 
cvanwie said:
Thanks for the late nights, intriguing and fascinating issues, great banter, and product suggestions!

My last day @ Vox has been incredibly busy and before I left, I wanted to say "Cheers!" to you all as well.

All the best

-Chris
Click to expand...

Thank you for all the help and wish you the best. Enjoy fast internet in the States.
 
@cvanwie

Yo Chris... all the best mate... and a heartfelt and sincere THANKS from me here for all your effort and time !!

So long and thanks for all the fish!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X