Any patch available for this?
On 14 February 2013 00:46, Javier Cardona <[email protected]> wrote: > Hi Ajay, > > On Tue, Feb 12, 2013 at 10:33 PM, Ajay Parida <[email protected]> > wrote: > > I am working with linux kernel 3.6.0. > > On a secured mesh network of 4 nodes, I want to block the direct path > from > > MAP to MPP. > > For this I am using command > > "iw dev mesh0 station set <mac address of MPP> plink_action block" at > MAP. > > > > But I am not getting expected result, I am still finding the direct path > > from MAP to MPP in my dumps. > > > > The same thing is perfectly working with a mesh network in open mode. > > > > What could be the issue? > > In an open mesh, the kernel handles the sta's state transitions, and > you may use iw to send "actions" to the in-kernel state machine that > trigger state changes. > > In a secure mesh, the in-kernel state machine is disabled and authsae > is directly setting the sta states and all action requests from user > space are ignored. > > So, a way to block a station would be to extend authsae to allow you > to set a sta in PLINK_BLOCKED state. See the function > set_plink_state() in linux/meshd-nl80211.c > Alternatively, one could modify iw to detect that the mesh is secure > and in that case send a NL80211_ATTR_STA_PLINK_STATE instead of a > NL80211_ATTR_STA_PLINK_ACTION message. > > Cheers, > > Javier > > > > -- > Javier Cardona > cozybit Inc. > http://www.cozybit.com > _______________________________________________ > Devel mailing list > [email protected] > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel >
_______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
