On Wed, 2008-02-13 at 08:51 +0100, Johannes Berg wrote: > > the same mesh configuration. This mesh configuration is composed by the > > mesh ID and path discovery protocol/metric/congestion control IDs. Once > > the link is open the mesh ID is not included in the frames. Let me know > > if you want more info. > > We don't have settings for the other control IDs yet, or did I miss > them? Those settings are in the struct ieee80211_if_sta. We are just hardcoding the values on route initialization, since we just support one path protocol and link metric. > Another, off-topic in this thread, question: How is beaconing defined > for a mesh point? Is it similar to how it works in an IBSS? According to the draft you can choose IBSS-like beaconing (wait a small random time before sending the beacon and don't send it if you hear it first) or AP-like beaconing. -- 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
