Regarding the new route changes detection: is there any way to detect a hop that is multi-homed or using load balancing? For example, our provider is using load-balancing on 4 T-1's between their POP (which we're connected to) and their backbone. Nearly every packet sent travels over a different T-1 on it's way out, making the "Route Changes" unusable. That one hop keeps changing because the addresses of the interfaces on each T-1 at their backbone is different.<br><br>My experience tells me that it would not be possible to detect such a thing without wrecking some real routing changes. So...would it be possible to have an "exception list", where the user could enter an IP address somewhere that tells PingPlotter to ignore changes at the hop after that address (but continue to monitor changes beyond there)?<br><br>Thanks for your time and brain-power. :-)<br><br>

Here's an idea for this. How about allowing you to enter a subnet mask that would be used for this purpose.<br><br>One possible way would be to do a "slider" bar with 4 settings. Each one would be one byte from the mask, so having it on full sensitivity would use a mask of 255.255.255.255 (all route changes would be tracked). Sliding the bar would progressively change these to 0s. This mask would then be anded with the old and new IPs at a hop, and if they were different *after* the anding, then a route change would be "detected".<br><br>This could possibly be augmented by allowing you to manually enter your own mask as well (for the advanced user). An advanced mask might be 255.255.255.252 (for example, if you're load balancing toggles between x.y.z.1 and x.y.z.2).<br><br>Another way to attack this would be to allow you to enter a list of masks that would be ignored. In the example above, you could enter x.y.x.3 (where the x.y.z were actually the numbers that matched the ip address used for load balancing). If both addresses had matching bits with one of your exception masks, then those route changes would be ignored.<br><br>Ideas/feedback?<br><br><br>

This feature is implemented for beta 2 - you can now enter route change exclusions - and Ping Plotter won't show route changes between the hops that fall within the filter. It updates the IP address on the host (as the IP changes), but as long as the IP falls within the mask you've entered, it doesn't generate a route change.<br><br><br>