linux-toradex.git/net/wireless/mesh.c, branch v3.7

cfg80211: respect iface combinations when starting operation

2012-06-29T11:39:19+00:00

devlist_mtx locking is changed to accomodate changes.

Signed-off-by: Michal Kazior 
Signed-off-by: Johannes Berg

cfg80211: add channel tracking for AP and mesh

2012-06-29T11:39:15+00:00

We need to know which channel is used by a running
AP and mesh for channel context accounting and
finding matching/active interface combination.

STA/IBSS have current_bss already which allows us
to check which channel a vif is tuned to.
Non-fixed channel IBSS can be handled with
additional changes.

Monitor mode is going to be handled differently.

Signed-off-by: Michal Kazior 
Signed-off-by: Johannes Berg

{nl,cfg,mac}80211: implement dot11MeshHWMPconfirmationInterval

2012-06-18T11:55:15+00:00

As defined in section 13.10.9.3 Case D (802.11-2012), this
control variable is used to limit the mesh STA to send only
one PREQ to a root mesh STA within this interval of time
(in TUs). The default value for this variable is set to
2000 TUs. However, for current implementation, the maximum
configurable of dot11MeshHWMPconfirmationInterval is
restricted by dot11MeshHWMPactivePathTimeout.

Signed-off-by: Chun-Yeow Yeoh 
[line-break commit log]
Signed-off-by: Johannes Berg

{nl,cfg,mac}80211: implement dot11MeshHWMProotInterval and dot11MeshHWMPactivePathToRootTimeout

2012-06-14T07:08:22+00:00

Add the mesh configuration parameters dot11MeshHWMProotInterval
and dot11MeshHWMPactivePathToRootTimeout to be used by
proactive PREQ mechanism.

Signed-off-by: Chun-Yeow Yeoh 
[line-break commit log]
Signed-off-by: Johannes Berg

cfg80211: clarify set_channel APIs

2012-06-06T19:18:17+00:00

Now that we've removed all uses of the set_channel
API except for the monitor channel and in libertas,
clarify this. Split the libertas mesh use into a
new libertas_set_mesh_channel() operation, just to
keep backward compatibility, and rename the normal
set_channel() to set_monitor_channel().

Also describe the desired set_monitor_channel()
semantics more clearly.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

cfg80211: provide channel to join_mesh function

2012-06-05T19:32:18+00:00

Just like the AP mode patch, instead of setting
the channel and then joining the mesh network,
provide the channel to join the network on to
the join_mesh() function.

Like in AP mode, you can also give the channel
to the join-mesh nl80211 command now.

Unlike AP mode, it picks a default channel if
none was given.

As libertas uses mesh mode interfaces but has
no join_mesh callback and we can't simply break
it, keep some compatibility code for that case
and configure the channel directly for it.

In the non-libertas case, where we store the
channel until join, allow setting it while the
interface is down.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

{nl,cfg,mac}80211: Allow user to see/configure HT protection mode

2012-05-09T01:53:59+00:00

This patch introduces a new mesh configuration parameter "ht_opmode" and will
allow user to check the current HT protection mode selected. Users could
configure the protection mode by the command "iw mesh_iface set mesh_param
mesh_ht_protection_mode=2". The default protection mode of mesh is set to
non-HT mixed mode.

Signed-off-by: Ashok Nagarajan 
Reviewed-by: Thomas Pedersen 
Signed-off-by: John W. Linville

{nl,cfg}80211: Support for mesh synchronization

2012-04-10T19:20:33+00:00

Report Toffset to userspace.
Let userspace select the mesh synchronization method.

Signed-off-by: Marco Porsch 
Signed-off-by: Pavel Zubarev 
Signed-off-by: Javier Cardona 
Signed-off-by: John W. Linville

{nl,cfg,mac}80211: Implement RSSI threshold for mesh peering

2012-03-05T20:23:15+00:00

Mesh peer links are established only if average rssi of the peer
candidate satisfies the threshold. This is not in 802.11s specification
but was requested by David Fulgham, an open80211s user. This is a way to avoid
marginal peer links with stations that are barely within range.

This patch adds a new mesh configuration parameter, mesh_rssi_threshold. This
feature is supported only for hardwares that report signal in dBm.

Signed-off-by: Ashok Nagarajan 
Signed-off-by: Javier Cardona 
Signed-off-by: John W. Linville

{nl,cfg,mac}80211: Add support of setting non-forwarding entity in Mesh

2012-01-27T19:56:56+00:00

A mesh node that joins the mesh network is by default a forwarding entity. This patch allows
the mesh node to set as non-forwarding entity. Whenever dot11MeshForwarding is set to 0, the
mesh node can prevent itself from forwarding the traffic which is not destined to him.

Signed-off-by: Chun-Yeow Yeoh 
Signed-off-by: John W. Linville