My thought is a utility that initiates the trace, identifies the hops it can, queries the looking glasses, identifies the return per hop on the path and icmp expires the identified return path.... would be a cumbersome process manually. I have one of those "some sites work, some sites dont" issues im working on with a banks IT. I think its their firewall based on the pcaps, but when im looking at it from the middle its hard to rule out an assymetric path issue with one of those one off issues like some freaked out mtu along the way
On Fri, May 31, 2019, 8:04 PM Steve Jones <[email protected]> wrote: > Thats kind of the point of the question > > On Fri, May 31, 2019, 5:35 PM Adam Moffett <[email protected]> wrote: > >> Gotta have someone at the other end traceroute back to you. >> >> IMO Traceroute is kinda useless anyway these days. If you're lucky it'll >> tell you what L3 routers are in the path, but all manner of >> tunneling/switching/MPLS stuff is invisible to traceroute. The only other >> diagnostic info it gives you is the total of the time that router took to >> generate an ICMP error message and the time it took that error message to >> come back to you.... and you can't assume that ICMP message came back to >> you on the same path normal traffic to and from your destination would have >> taken. >> >> >> On 5/31/2019 6:20 PM, Steve Jones wrote: >> >> Is there a tool similar to traceroute to view both paths in an asymmetric >> path. Maybe something that queries looking glass then multipings >> >> >> -- >> AF mailing list >> [email protected] >> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >> >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
