> > Updating the path to the transmitter of a path message is optional > > according to section 13.10.8.4 of the standard. Doing so can lead to > > better performance since we can adjust the route to the transmitter > > based on the freshest possible information. However it can also cause > > routing loops with more than four or five nodes. > > Do you have the test scenario on how routing loops happen in this case? > > Thanks > > ---- > Chun-Yeow We did this over a year ago and I don't think we saw routing loops though iirc we saw better performance when we made the change. Most likely because of the other problem with the original code: it creates a path to the ta if none exists but does not go through discovery to do so. So if the direct hop is not the best path you're going to be stuck with a crappy path until the next refresh. In any case updating metrics without doing an SN feasibility check is highly suspect. I'm not 100% sure this instance will cause routing loops but I do know that every time I have tried to be clever and optimize routing without looking at both the SN and metric I have wound up with routing loops. -- Jesse -- 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
