nl80211: explicit userspace MPM
Secure mesh had the implicit requirement that the Mesh Peering Management entity be in userspace. However userspace might want to implement an open MPM as well, so specify a mesh setup parameter to indicate this. Signed-off-by: Thomas Pedersen <thomas@cozybit.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
This commit is contained in:

committed by
Johannes Berg

parent
2ff2b690c5
commit
bb2798d45f
@@ -1151,6 +1151,7 @@ struct mesh_config {
|
||||
* @ie_len: length of vendor information elements
|
||||
* @is_authenticated: this mesh requires authentication
|
||||
* @is_secure: this mesh uses security
|
||||
* @user_mpm: userspace handles all MPM functions
|
||||
* @dtim_period: DTIM period to use
|
||||
* @beacon_interval: beacon interval to use
|
||||
* @mcast_rate: multicat rate for Mesh Node [6Mbps is the default for 802.11a]
|
||||
@@ -1168,6 +1169,7 @@ struct mesh_setup {
|
||||
u8 ie_len;
|
||||
bool is_authenticated;
|
||||
bool is_secure;
|
||||
bool user_mpm;
|
||||
u8 dtim_period;
|
||||
u16 beacon_interval;
|
||||
int mcast_rate[IEEE80211_NUM_BANDS];
|
||||
|
Reference in New Issue
Block a user