Searching...
Reply
Highlighted
Accepted Solution

Timeouts in traceroute & dropped connections

inaroundroom

Over the last couple of weeks I'm been making an increased number of Skype based calls and have had issues with connection drops/audio drop outs.

 

Doing speedtests throughput seems okay but when doing traceroutes I note quite a few of the hops are timing out on the way to the destination:

 

google.com

Tracing route to www.google.com [198.142.187.29]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 12 ms 9 ms 10 ms 10.57.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 14 ms 11 ms 12 ms 210.49.109.18
9 14 ms 11 ms 12 ms 198.142.187.29

Trace complete.

 

Optus.com.au

Tracing route to e6356.a.akamaiedge.net [104.84.12.197]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 10 ms 9 ms 10 ms 10.57.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 11 ms 13 ms 12 ms 210.49.112.122
8 29 ms 29 ms 27 ms 198.142.144.182
9 13 ms 11 ms 12 ms a104-84-12-197.deploy.static.akamaitechnologies.com [104.84.12.197]

Trace complete.

 

Does anyone else get simliar results from Optus Cable?

Re: Timeouts in traceroute & dropped connections

beetroot

When performing traceroutes from a Windows PC the network packets are sent using ICMP. As the packets hop from one node/host to the next, the node may or may not respond, if a node responds then the time taken to establish the connection between your computer and that node is used to determine the delay or latency. However, if a node does not respond then this generally indicates that the node has been configured to not respond to ICMP traffic. Lots of public hosts are configured this way by network administrators who feel that ICMP is a security risk. Some legacy worms and DDOS attack methods leveraged off of the ICMP protocol. So a timeout at one or more hops does not mean that there is a network issue affecting traffic between your computer and that node.

 

If you have access to a Linux PC, then try performing a traceroute from it and you may find that you'll get different results because by default Linux uses UDP instead of ICMP to perform traceroutes and as such you just might end up getting a response from each hop.

 

Judging by your results,14ms/11ms/12ms seem like reasonable latency values for google.com and likewise 13ms/11ms/12ms for optus.com.au.

 

Have you tried the troubleshooting tips from Skype?

Click here: Troubleshooting problems with Skype calls

 

Hope this helps.

 

 

 

Beetroot

Re: Timeouts in traceroute & dropped connections

[ Edited ]
inaroundroom

Thanks for your response.

 

It happens from a MacOS machine as well as my router, when I look at it the problem does appear on face value to be in the Optus network past what I believe is the optus gateway 10.57.0.1?

 

I do not have the same issues when connecting via a Telstra tethered connection so my belief is that the problem is with the Optus Network.

 

If you do a simliar trace do you get drops?

 

Optus Trace from router:

traceroute to optus.com.au (104.98.26.26), 30 hops max, 38 byte packets
1 10.57.0.1 (10.57.0.1) 8.699 ms 6.527 ms 7.623 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 59.154.142.42 (59.154.142.42) 11.033 ms 13.904 ms 10.665 ms
7 220.101.73.82 (220.101.73.82) 12.622 ms 10.135 ms 21.611 ms
8 bundle-108.cor03.syd03.nsw.vocus.net.au (114.31.192.84) 11.692 ms 11.445 ms bundle-108.cor01.syd04.nsw.vocus.net.au (114.31.192.86) 9.809 ms
9 bundle-101.bdr05.syd03.nsw.vocus.net.au (114.31.192.59) 11.873 ms bundle-100.bdr05.syd03.nsw.vocus.net.au (114.31.192.57) 14.020 ms bundle-101.bdr05.syd03.nsw.vocus.net.au (114.31.192.59) 12.232 ms
10 asn20940.cust.bdr04.syd03.nsw.vocus.net.au (175.45.124.226) 33.606 ms 26.431 ms 27.921 ms
11 a104-98-26-26.deploy.static.akamaitechnologies.com (104.98.26.26) 10.672 ms 21.948 ms 11.165 ms

 

Re: Timeouts in traceroute & dropped connections

beetroot

No worries,

 

Before we go on, let's take a step back, the issue you mentioned is that your experiencing dropped calls/connections while on Skype. Have you tried following Skype's troubleshooting steps I posted earlier (even if they are lame and obvious - sometimes it's the obvious things that seem to stump the best of us)?

 

Perhaps I am missing the point but, I don't understand why you think performing a traceroute to www.google.com.au or www.optus.com.au is going to shed some light on why your Skype calls drop out. In saying that, the fact that you are receiving timeouts on 4 hops does not suggest that there is a network connectivity issue between your computer and those nodes at each hop. It just means, that those nodes are not responding to your traceroute (they don't have to respond).

 

For the sake of the exercise I get a timeout on hop 3. But the route or path my traceroute packets take are different to yours and you may find that depending on network load, distance and other factors, the same traceroute command you executed will differ from time. This is because networks have infrastructure in place to manage the direction and flow of traffic between your computer and the destination which means that the same traceroute on the same computer can be subject to change.

 

Either way, I'm not saying that it's not an Optus issue, but I am saying that Traceroute won't help determine the cause of the issue, particularly if its to a host that has nothing to do with Skype. At the very least, try the troubleshooting steps on the other link. That way you can say that you've tried the bleeding obvious. If to no avail then the next step I would try is skyping on another network (if possible, hopefully from a friend or family member or other trusted network). If it still drops off, it might be a software issue or configuration issue with your macOS configuration, otherwise if it doesn't then we know it's a network issue and we can look at other aspects of your home network set up before looking outwards into the Optus HFC network.

 

Beetroot

Re: Timeouts in traceroute & dropped connections

peekay

yes i agree. Internediate gateways may be blocking ICMPso n eral cause for concern

 

Also the actual RTT times look good anyway.  

Re: Timeouts in traceroute & dropped connections

Sam_D

Hey there @inaroundroom Smiley Happy As @beetroot suggested, you might find Skype's troubleshooting tips to be a little more helpful than performing trace routes to Optus and/or Google. Is Skype the only service that you've noticed connection issues with? If you're still having troubles after running through their targeted testing, let us know and we can check out your service. 

Re: Timeouts in traceroute & dropped connections

inaroundroom

@Sam_D it's definitely not just Skype this was the more annoying service drops, it also happens regularly with my work VPN around 4/5 times a day I will be kicked out sometimes this will auto reconnet other times will not and I have to reauthenticate.

 

I've implemented on my router a simple script running via a cronjob to check access past the Optus Cable Modem so I can get a better handle on how aften the connection drops and will report back in a bit.

Re: Timeouts in traceroute & dropped connections

Sam_D

When you experience these drops (Eg. from your work VPN) - have you noticed that everything disconnects completely at the same time? Or is it just certain programs like Skype which temporarily lose connection? 

Re: Timeouts in traceroute & dropped connections

inaroundroom

@Sam_D yes can pull down all devices internet access, sometimes I cannot even connect to the cable modem via the admin interface and this then requires a power off for 2min.

Solution

Re: Timeouts in traceroute & dropped connections

Sam_D

Thanks for confirming - are you able to send me a PM with your full name, DOB and Optus username so I can take a look at your service? 

Post a Reply
Top Contributors
81 Kudos
76 Kudos
71 Kudos
40 Kudos
30 Kudos