The problem with this approach is that the points inbetween can change specially if a providers peering point is starting to fail and I want to follow those changes... That is what mtr does nicely.
-----Original Message----- From: Jon Bendtsen [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 5:52 AM To: Fred Skrotzki Cc: [email protected] Subject: Re: [smokeping-users] Has anybody wirtten a routine to determine whereon a route loss is occuring? Den mandag 6.aug kl. 21:42 skrev Fred Skrotzki: > We are currently noticing loss to three different points that we > monitor and know it has to be in one of the common points that is > causing the issue. The problem is the loss is low (5%) and it takes > many repeated traceroutes to each location to start to determine the > location. > > I was just wondering if anybody has some something like a > smoketraceroute? i often have problems with a particular partner. So i did a traceroute to the partners IP address and started doing regular smokeping monitoring of each node all the way to the partner. That will show where the problem is, but you have to monitor each node. JonB _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
