Get online support
Hi Team
Thanks for your reply, however I'm not concerned with the firewall, I'm concerned about what appears to be regular packet loss and high latency within your network.
I can post a link to our smokeping graphs that appear to show regular packetloss occuring within your network either here or to you as a private message for your NOC to investigate.
Regards
Shamhat
Hi @shamhat_the_2nd, please perform a traceroute test from and to the destination you are running smokeping and the ADSL WAN IP address.
Please send the screenshots to helpdesk@tpg.com.au so we can check further.
Hi @Riezl
The trouble with performing a traceroute test from and to the destination I am running smokeping to is that the problem is intermittent.
So, I propose sending two lots of traceroutes to you. The first when there is no extreme latency/packet loss and the second when there is packet loss/latency. I'd also like to send my smoke ping graphs as they actually show the amount of packet loss and latency over time. I'm sure the TPG NOC would find them interesting, they look a lot like cacti graphs as they are based on the same RRDTool files.
Would that be ok with you? ADSL WAN IP address won't be a problem.
Regards
Shamhat
Hi @shamhat_the_2nd, we'd like to check if you have provided us the screenshots of the traceroute tests.
Hi @shamhat_the_2nd,
Thanks for updating us.
I've also now chased this with our engineering team. They'll be in contact once updates becomes available.
Cheers,
Update:
We are back online after a technician visited and performed work.
I've tested two scripts (hightracer.sh and lowtracer.sh) that traceroutes all of the destinations that my smokeping server targets and will use them over the next few days. FYI, the lowtracer.sh script looks like this (below) and the hightracer.sh is exactly the same but it saves the output to a different set of files in a different directory. Every trace is timestamped.
#!/bin/sh
#Have you marked it executable? chmod u+x filename
#tracing during periods of low latency:
cd /root/traceroutes/lowlatency
rm *.txt
cd .. /
#dns
date >> /root/traceroutes/lowlatency/lowlatency_2031216035.txt &
traceroute 203.12.160.35 >> /root/traceroutes/lowlatency/lowlatency_2031216035.txt &
date >> /root/traceroutes/lowlatency/lowlatency_2031216036.txt &
traceroute 203.12.160.36 >> /root/traceroutes/lowlatency/lowlatency_2031216036.txt &
date >> /root/traceroutes/lowlatency/lowlatency_8888.txt &
traceroute 8.8.8.8 >> /root/traceroutes/lowlatency/lowlatency_8888.txt &
date >> /root/traceroutes/lowlatency/lowlatency_8844.txt &
traceroute 8.8.4.4 >> /root/traceroutes/lowlatency/lowlatency_8844.txt &
#http
date >> /root/traceroutes/lowlatency/lowlatency_google.txt &
traceroute google.com >> /root/traceroutes/lowlatency/lowlatency_google.txt &
date >> /root/traceroutes/lowlatency/lowlatency_facebook.txt &
traceroute facebook.com >> /root/traceroutes/lowlatency/lowlatency_facebook.txt &
date >> /root/traceroutes/lowlatency/lowlatency_codeacademy.txt &
traceroute codeacademy.com >> /root/traceroutes/lowlatency/lowlatency_codeacademy.txt &
date >> /root/traceroutes/lowlatency/lowlatency_youtube.txt &
traceroute youtube.com >> /root/traceroutes/lowlatency/lowlatency_youtube.txt &
date >> /root/traceroutes/lowlatency/lowlatency_youporn.txt &
traceroute youporn.com >> /root/traceroutes/lowlatency/lowlatency_youporn.txt &
date >> /root/traceroutes/lowlatency/lowlatency_wikipedia.txt &
traceroute wikipedia.org >> /root/traceroutes/lowlatency/lowlatency_wikipedia.txt &
date >> /root/traceroutes/lowlatency/lowlatency_gumtree.txt &
traceroute gumtree.com.au >> /root/traceroutes/lowlatency/lowlatency_gumtree.txt &
date >> /root/traceroutes/lowlatency/towel.blinkenlights.nl.txt &
traceroute towel.blinkenlights.nl >> /root/traceroutes/lowlatency/towel.blinkenlights.nl.txt &
date >> /root/traceroutes/lowlatency/lowlatency_amazon.txt &
traceroute amazon.com >> /root/traceroutes/lowlatency/lowlatency_amazon.txt &
#speedtest
date >> /root/traceroutes/lowlatency/lowlatency_mel1speedtesttelstranet.txt &
traceroute mel1.speedtest.telstra.net >> /root/traceroutes/lowlatency/lowlatency_mel1speedtesttelstranet.txt &
date >> /root/traceroutes/lowlatency/lowlatency_syd1speedtesttelstranet.txt &
traceroute syd1.speedtest.telstra.net >> /root/traceroutes/lowlatency/lowlatency_syd1speedtesttelstranet.txt &
date >> /root/traceroutes/lowlatency/lowlatency_per1speedtesttelstranet.txt &
traceroute per1.speedtest.telstra.net >> /root/traceroutes/lowlatency/lowlatency_per1speedtesttelstranet.txt &
date >> /root/traceroutes/lowlatency/lowlatency_ade1speedtesttelstranet.txt &
traceroute ade1.speedtest.telstra.net >> /root/traceroutes/lowlatency/lowlatency_ade1speedtesttelstranet.txt &
date >> /root/traceroutes/lowlatency/lowlatency_brs1speedtesttelstranet.txt &
traceroute brs1.speedtest.telstra.net >> /root/traceroutes/lowlatency/lowlatency_brs1speedtesttelstranet.txt
Regards
Shamhat
Thanks for informing us, @shamhat_the_2nd.
We'll see how it goes and if the issue persists, please let us know so we can further check.