| commit | 945aad99b1753742aacac733a089cf2ba29e016f | |
| author | David Kilroy <kilroyd@googlemail.com> | |
| Sat, 4 Dec 2010 15:32:10 +0000 (4 15:32 +0000) | ||
| committer | David Kilroy <kilroyd@googlemail.com> | |
| Sat, 11 Dec 2010 15:27:06 +0000 (11 15:27 +0000) | ||
| tree | d14d45725b494806c3729fd1a127d33b111ed84b | treesnapshot (tar.gz zip) |
| parent | 2c3c5834eacf61a099f8c3add3baec04771326ca | commitdiff |
orinoco: clear countermeasure setting on commit
... 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>
... 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>
| drivers/net/wireless/orinoco/main.c | diffblobblamehistory |