Just replied on list for the sake of helping others. Can you get a trace back the other way.
Thanks for straighening the table up :) Kindly, ROY ADAMS* | *P 07 3040 5010 | Web: http://www.racs.com.au/ | Wiki: https://ex.racs.com.au:444/ | eMail: mailto:[email protected] <[email protected]> A positive attitude causes a chain reaction of positive thoughts, events, and outcomes. If you think it's expensive to hire a professional to do the job, wait until you hire an amateur - Red Adair. Life is a journey through a series of adventures... Live them, love them, hate them, but never give up on your dreams, desires, and goals. Have you been good today? ಠ_ಠ On Tue, 25 Aug 2020 at 17:27, Giles Pollock <[email protected]> wrote: > Much the same deal it seems with WinMTR... ICMP can only get you so far. > Standout seems to be 203.8.177.110 where the latency spikes and the packet > loss begins. > Host % Sent Recv Best Avrg Wrst Last > 192.168.1.129 0 200 200 0 0 2 0 > 192.168.1.1 0 200 200 0 0 1 0 > 192.168.0.1 0 200 200 1 1 5 1 > 10.20.22.139 0 200 200 5 5 13 5 > 27-32-160-196.static.tpgi.com.au 0 200 200 5 5 13 6 > 203-219-107-206.static.tpgi.com.au 0 200 200 5 6 13 6 > 203.8.177.110 6 164 155 54 66 77 68 > Request timed out. 100 40 0 0 0 0 0 > Request timed out. 100 40 0 0 0 0 0 > 124.19.61.93 7 160 150 0 65 74 68 > 124.19.69.102 7 160 150 0 69 78 67 > static-62.200.255.49.in-addr.VOCUS.net.au 8 152 140 56 68 84 68 > ip-226.194.255.49.in-addr.VOCUS.net.au 7 160 150 57 68 96 70 > Not overly surprising results, although at least the packet loss seems to > be reducing a bit now. I did the right thing and contacted my service > provider as well to log a ticket on their end (hello to anyone who might > end up with the escalation! :-D ) > > On Tue, Aug 25, 2020 at 5:08 PM Roy Adams <[email protected]> wrote: > >> Ahh, awesome, just sent another with link to WinMTR. >> I try to draft emails so that others who don't know this stuff also get >> some learning/help. >> >> I hope my email came across ok. >> >> I am sure the list would be interested in your findings. >> >> Don't forget when pasting those text traces to change the font to "Fixewd >> Width", or they are hard to read in emails :) >> >> Kindly, >> >> ROY ADAMS* | *P 07 3040 5010 | Web: http://www.racs.com.au/ | Wiki: >> https://ex.racs.com.au:444/ | eMail: mailto:[email protected] >> <[email protected]> >> A positive attitude causes a chain reaction of positive thoughts, events, >> and outcomes. >> If you think it's expensive to hire a professional to do the job, wait >> until you hire an amateur - Red Adair. >> Life is a journey through a series of adventures... Live them, love them, >> hate them, but never give up on your dreams, desires, and goals. >> Have you been good today? ಠ_ಠ >> >> >> On Tue, 25 Aug 2020 at 17:06, Giles Pollock <[email protected]> wrote: >> >>> Agreed Roy, especially with how much ICMP traffic now gets messed with >>> compared to other protocols. At best all it really gives me is a comparison >>> between what I normally see and what I'm seeing at the moment. That and my >>> constantly dying RDP and SSH sessions to various other hosts in the same >>> network. >>> >>> Not that it can be relied on either, but running a traceroute from the >>> hosts on the Vocus link back to me shows asymmetric routing as well. >>> >>> On Tue, Aug 25, 2020 at 4:59 PM Roy Adams <[email protected]> wrote: >>> >>>> Hi Giles, >>>> >>>> Using ICMP tracesw to measure traffic loss is fraught with danger due >>>> to intermediate routers dropping unimportant traffic like ICMP. >>>> Drawing conclusions regarding packet loss also requires noting the same >>>> or higher degree of packet loss further down the trace, among many other >>>> factors (see further below) >>>> A double end trace (one initiated form each end) is required from >>>> 124.19.69.102 to 27.32.160.196, and also from 27.32.160.196 to >>>> 124.19.69.102. >>>> This could well show that the trace in each direction follows a >>>> different path - i.e. asymmetric routing. >>>> mtr / WinMTR is a more reliable tool to do the above - you will need >>>> mtr profiles from each end to start painting a better picture. >>>> >>>> Some light reading on understanding traceroutes in general, well worth >>>> the read: >>>> >>>> http://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf >>>> >>>> I hope the above is of use. >>>> Here in the Philippines, we have learned some hard lessons about making >>>> assumptions about traffic loss. >>>> >>>> Kindly, >>>> >>>> ROY ADAMS* | *P 07 3040 5010 | Web: http://www.racs.com.au/ | Wiki: >>>> https://ex.racs.com.au:444/ | eMail: mailto:[email protected] >>>> <[email protected]> >>>> A positive attitude causes a chain reaction of positive thoughts, >>>> events, and outcomes. >>>> If you think it's expensive to hire a professional to do the job, wait >>>> until you hire an amateur - Red Adair. >>>> Life is a journey through a series of adventures... Live them, love >>>> them, hate them, but never give up on your dreams, desires, and goals. >>>> Have you been good today? ಠ_ಠ >>>> >>>> >>>> On Tue, 25 Aug 2020 at 16:42, Giles Pollock <[email protected]> wrote: >>>> >>>>> Not sure if anyone else is enjoying this experience, but I've seen a >>>>> few occasions where there seems to be degradation between TPG and Vocus in >>>>> Victoria. Pings go up by between 50-100ms with about 15% packet loss along >>>>> the way. >>>>> >>>>> 4 5 ms 6 ms 5 ms 10.20.22.139 >>>>> 5 6 ms 6 ms 6 ms 27-32-160-196.static.tpgi.com.au >>>>> [27.32.160.196] >>>>> 6 6 ms 6 ms 6 ms 203-219-107-206.static.tpgi.com.au >>>>> [203.219.107.206] >>>>> 7 69 ms 67 ms 69 ms 203.8.177.110 >>>>> 8 * * * Request timed out. >>>>> 9 * * * Request timed out. >>>>> 10 68 ms 68 ms 68 ms 124.19.61.93 >>>>> 11 73 ms 72 ms 72 ms 124.19.69.102 >>>>> >>>>> >>>>> Seen it come and go a few times over the last few weeks too. Makes >>>>> working from home a bit of a pain when remote sessions keep getting punted >>>>> out due to the packet loss! >>>>> _______________________________________________ >>>>> AusNOG mailing list >>>>> [email protected] >>>>> http://lists.ausnog.net/mailman/listinfo/ausnog >>>>> >>>>
_______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
