orinoco: clear countermeasure setting on commit
authorDavid Kilroy <kilroyd@googlemail.com>
Sun, 5 Dec 2010 15:45:58 +0000 (15:45 +0000)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 7 Jan 2011 21:58:32 +0000 (13:58 -0800)
commit107fd06cf44abb702cd8f97c1f78a3de1c770dfb
treeded5a14ed4c0397d61b4a7ae53d402ee48c14cff
parentd2decdda7421a5917da51d62165417c2900a6ad6
orinoco: clear countermeasure setting on commit

commit ba34fcee476d11e7c9df95932787a22a96ff6e68 upstream.

... and interface up.

In these situations, you are usually trying to connect to a new AP, so
keeping TKIP countermeasures active is confusing. This is already how
the driver behaves (inadvertently). However, querying SIOCGIWAUTH may
tell userspace that countermeasures are active when they aren't.

Clear the setting so that the reporting matches what the driver has
done..

Signed-off by: David Kilroy <kilroyd@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/net/wireless/orinoco/main.c