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>