On Mon, 2008-07-28 at 08:45 -0400, Steve Brown wrote: > Although mesh path timeout seems to default to 5000ms, in my testing it > takes about 50 min. Is this really the timeout that removes a node when > it's beacon is off for this period? When a mesh path timeouts it is marked accordingly and it is no longer valid for routing. In a continuous traffic scenario this means that every five seconds, the route are refreshed. Actually we start refreshing one second before the route expires, so that we have a fresh path before the current one times out. Mesh path timeout does not _remove_ the path from the mesh path table, so you will see it for a while, the table cleanup function which removes from the table paths that have expired long ago has a separate timing. -- Luis Carlos Cobo Rus GnuPG ID: 44019B60 cozybit Inc. -- 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
