On 18 December 2013 10:50, Gavin Henry <[email protected]> wrote: > On 16 December 2013 11:02, James Bensley <[email protected]> wrote: >> It performs a traceroute to a destination every 5 minutes and stores >> the results. The idea is to monitor for route changes in networks >> other than your own where you typically can't. This is hard to do >> accurately, so even though the initial alpha release of the code is >> 90% finished, I need to work on making it more accurate. It will >> support multiple kinds of traceroute (ICMP, UDP and TCP). You can be >> alerted when the route chages to a remote host and receive an email >> with the different hops in the path. If there is a router failure in a >> peer network close to our peering router with them, would can catch >> it, if we have Smokeping set up to a similar point in there network >> and start seeing loss, we could assume congestion and shut down the >> peering session, as an example. > > Open source?
Of course ;) James.
