> There are two test scenarios: > 1) When creating the path to a ta where the direct hop is a bad path. > Relatively easy to setup and demonstrate poor performance pre-patch. > 2) Incorrect routing when the metric for an existing SN is changed without > also updating the SN. Hard to demonstrate. We've certainly seen similar bugs > with our own mesh protocols but that was with protocols explicitly designed > with testing support. Best approach is probably via something like > http://alloy.mit.edu/alloy/ If the direct hop is a bad path, could it be due the metric calculation. Also, you may also add your vendor specific mesh protocol to open source community. --- Chun-Yeow -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
