It appears there's no ordering to the list of known mesh gates. I'm assuming this is because noone uses mesh gates except to fallback for unresolved paths?
I'm adding an anycast mechanism for finding the "best mesh gate" (a la what OLPC did/does). It seems mesh gates are installed in the mesh_paths hash table so all I need is to map my fixed anycast address to a known mesh gate and everything else will just work. The only decision I see is whether to register a hash-table entry for the anycast address that points to the current "best mesh gate" or to intercept the address and select the best mesh gate on every use. The former seems better since it also lets me see what the current choice is with iw. OTOH after writing the above it seems like I can even avoid doing this if all my mesh gates publish a path to the anycast address. Then the normal path discovery mechanism would find it because only mesh gates would answer for the anycast address. Comments? -Sam
_______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
